Define policy reason mappings

  • Release version: Xanadu
  • Updated August 1, 2024
  • 1 minute to read
  • You can define the reason choices to be available to any user who requests an exception.

    Before you begin

    Role required: sn_vul.compliance.manager and sn_vulc.admin

    Procedure

    1. Navigate to All > Policy and Compliance > Policy Exceptions > Integration Registry.
      Note:
      You can either select a reason from the reason choices available in the Reason Choices table or add a new reason.
    2. Click the Container Vulnerability Response - CVIT integration registry.
    3. To add an existing reason choice, perform the following steps:
      1. In the Reason Choices list, click New.
      2. Click the magnifying glass icon to select a reason.
    4. To add new reason choices to the Reason Choices table, perform the following steps:
      1. In Reason Choices list, click New.
      2. Click the magnifying glass icon.
      3. Click New.
      4. On the form, fill in the fields.
        Table 1. Reason Choice List form
        Field Description
        Label Unique label for this choice.
        Value

        Unique value for this choice.

        This value is mapped in the Policy Exception Reason Mappings table for the respective applications. To navigate to this table, enter sn_sec_cmn_policy_reason_mapping.LIST in the filter navigator.

        Order Order for this choice. Reasons are ordered based on this number.
        Default Option to indicate that this reason choice will be available whenever an on demand policy exception is requested. If the integration registry doesn’t contain any application-specific choices, then all reason choices that have the Default field selected will be available.
        Active Option to display the choice in the list of reason choices.
    5. Click Submit.