Skip to main content

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​

  1. In your browser, go to https://<your-tenant>.apisecapps.com.

  2. Click Security Policy.

    Security Policy in the navigation menu

  3. Verify the APIsec Base Policy.

    APIsec Base Policy on the Security Policy page

Create components​

Create components before you create your first policy — they are the building blocks of every policy.

  1. Click the Policy Components tab.

    Policy Components tab

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

    Policy Components page listing component types

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.

  1. Click Add Frequency.

    Add Frequency button

  2. 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.

    Scan Schedule component details form

  3. Click Create Component.

    Create Component button for Scan Schedule

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

    Scan Schedule component success message

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.

  1. Click Add Response Action Set.

    Add Response Action Set button

  2. 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.

    Response Actions component details form

  3. Click Create Component.

    Create Component button for Response Actions

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

    Response Actions component success message

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.

  1. Click Add SLA Profile.

    Add SLA Profile button

  2. 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.

    SLA component details form

  3. Click Create Component.

    Create Component button for the SLA component

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

    Risk Mitigation component success message

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:

  1. Click Add Profile.

    Add Profile button

  2. 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.

    Test Scope component details form

  3. Click Create Component.

    Create Component button for Test Scope

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

    Test Scope component success message

Create a policy​

  1. Click the Security Policies tab.

    Security Policies tab

  2. Click Add New Policy.

    Add New Policy button

  3. In Step 1: Policy Information, enter the following details:

    • Policy Name: Enter a unique policy name.
    • Description: Enter a description for the policy.

    Policy Information step

  4. 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.

    Select Policy Components step

    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.

    First policy marked as the default policy

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

    Review Policy Configuration step

  6. Verify the newly created policy.

    Newly created policy in the policy list

note

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:

  1. Click the Applications tab.

    Applications tab

  2. Click Configure for the selected application.

    Configure button for the selected application

  3. Select the new policy and click Update.

    Policy selection and Update button

  4. 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.

    Application list showing policy, compliance, and component status

Create an inherited policy​

Any component you leave unselected is inherited from the default policy.

  1. Click Add New Policy.

    Add New Policy button

  2. Enter the policy information.

    Policy Information step

  3. In Select Policy Components, select any one component.

    Selecting a single policy component

  4. Review the policy configuration and click Create Policy.

    Review Policy Configuration step with Create Policy button

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

    Policy showing components marked as inherited

Edit a policy​

  1. Click Edit for the selected policy.

    Edit button for the selected policy

  2. Update the policy information or change the policy components.

    Updating policy components

  3. Review the changes and click Update Policy.

    Update Policy button

Delete a policy​

  1. Click Delete for the selected policy.

    Delete button for the selected policy

  2. Click Confirm to delete.

    Confirm dialog for policy deletion

  3. APIsec confirms the policy has been deleted.

    Policy deletion success message

note

The default policy cannot be deleted.

Delete a component​

  1. Click the Policy Components tab.

    Policy Components tab

  2. Click Delete for the selected component.

    Delete button for the selected component

  3. Click Confirm to delete.

    Confirm dialog for component deletion

  4. APIsec confirms the component has been deleted.

    Component deletion success message

note

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