Security policies
Security policies let administrators define and monitor configuration expectations across every application in the organization. Rather than asking each team to configure its own applications and hoping nothing is missed, you create a policy — for example, that every application is scanned daily — and see at a glance which applications fall out of compliance.
A policy is built from components. Each component defines one expectation, configuration, or constraint that applies to an application: how often applications must be scanned (Scan Schedule), how new vulnerabilities are handled (Response Actions), how fast vulnerabilities must be fixed (Risk Mitigation), and which test categories must run (Test Scope). More component types are added regularly.
Until you designate one, the built-in APIsec Base Policy acts as the default. The default policy checks the compliance of every application that has no explicitly assigned policy. In the console, a policy is only offered as the default once all of its components are defined. Other policies can inherit components from the default policy: any component you leave unselected is inherited, and if the default policy's components change, the inherited components change with them.
Open the Security Policy page
-
In your browser, go to https://<your-tenant>.apisecapps.com.
-
Click Security Policy.

-
Verify the APIsec Base Policy.

Create components
Create components before you create your first policy — they are the building blocks of every policy.
-
Click the Policy Components tab.

-
Create components of each type, as described in the following sections.

Scan Schedule
Specify how frequently applications need to be scanned — every few hours, daily, weekly, or monthly — to ensure continuous security coverage and timely detection of new risks.
-
Click Add Frequency.

-
Enter the details for the Scan Schedule component:
- Component Name: Enter a unique name for the component.
- Frequency: Select a frequency (every few hours, daily, weekly, or monthly).
- Description: Enter a description for the component.

-
Click Create Component.

-
APIsec confirms the component has been added to Scan Schedule.

Response Actions
Define how newly discovered vulnerabilities are handled. For example, automatically creating a ticket when a vulnerability meets a defined severity level ensures issues are tracked and routed to engineering teams for resolution.
-
Click Add Response Action Set.

-
Enter the details for the Response Actions component:
- Component Name: Enter a unique name for the component.
- Response Actions: Select a response action (creating a ticket).
- Severity Selection: Select the severity levels (Critical, High, Medium, and Low).
- Description: Enter a description for the component.

-
Click Create Component.

-
APIsec confirms the component has been added to Response Actions.

Risk Mitigation
Ensure vulnerabilities are remediated within the SLA defined in the policy. To stay compliant, active vulnerabilities must be resolved within the established timelines, reinforcing accountability and reducing long-term exposure.
-
Click Add SLA Profile.

-
Enter the details for the SLA component:
- Component Name: Enter a unique name for the component.
- Time to fix new vulnerabilities: Select a time frame for each vulnerability severity (days or hours).
- Description: Enter a description for the component.

-
Click Create Component.

-
APIsec confirms the component has been added to Risk Mitigation.

Test Scope
Execute the required test categories for each application. Applications must run the selected category types to remain compliant with their assigned policy.
To be compliant with this component, applications must have the required configurations for the selected categories:
- Broken authentication: The application must have at least one authentication configured.
- RBAC: The application must have an RBAC permissions mapping enabled for testing.
- BOLA: The application must have a valid BOLA attack scenario configured.
To create a Test Scope component:
-
Click Add Profile.

-
Enter the details for the Test Scope component:
- Component Name: Enter a unique name for the component.
- Test Scope: Select the test scope.
- Description: Enter a description for the component.

-
Click Create Component.

-
APIsec confirms the component has been added to Test Scope.

Create a policy
-
Click the Security Policies tab.

-
Click Add New Policy.

-
In Step 1: Policy Information, enter the following details:
- Policy Name: Enter a unique policy name.
- Description: Enter a description for the policy.

-
In Step 2: Select Policy Components, choose an existing component, exclude the component, or create and add a new one for each type:
- Scan Schedule: Select a Scan Schedule component, exclude it, or create and add a new one.
- Response Actions: Select a Response Actions component, exclude it, or create and add a new one.
- Risk Mitigation: Select a Risk Mitigation component, exclude it, or create and add a new one.
- Test Scope: Select a Test Scope component, exclude it, or create and add a new one.

Creating a policy does not make it the default. Select Set as default to designate one; until you do, the built-in APIsec Base Policy applies to every application with no explicitly assigned policy.

-
In Step 3: Review Policy Configuration, review the configuration and click Create Policy.

-
Verify the newly created policy.

The default policy checks the compliance of all applications without an assigned policy. The console only offers a policy as the default once all of its components are defined, and the built-in APIsec Base Policy cannot be re-designated.
Assign a policy
A single policy applies to all of your applications by default. To assign a different policy to an application:
-
Click the Applications tab.

-
Click Configure for the selected application.

-
Select the new policy and click Update.

-
Verify the new policy name in the Policy tag. If the application violates its assigned security policy, the Compliance column shows Non-Compliant. The Policy Component column shows all the components and their status.

Create an inherited policy
Any component you leave unselected is inherited from the default policy.
-
Click Add New Policy.

-
Enter the policy information.

-
In Select Policy Components, select any one component.

-
Review the policy configuration and click Create Policy.

-
Verify the policy. Components you did not select are marked as inherited components.

Edit a policy
-
Click Edit for the selected policy.

-
Update the policy information or change the policy components.

-
Review the changes and click Update Policy.

Delete a policy
-
Click Delete for the selected policy.

-
Click Confirm to delete.

-
APIsec confirms the policy has been deleted.

The default policy cannot be deleted.
Delete a component
-
Click the Policy Components tab.

-
Click Delete for the selected component.

-
Click Confirm to delete.

-
APIsec confirms the component has been deleted.

Components that are currently used by a policy cannot be deleted.