Run detection key configuration

task australia Updated Nov 6, 2026 1 min read run-detection-key-configuration.md

Use the revised detection key to update the existing detections and vulnerable item records.

Before you begin

Role required: sn_vul.vulnerability_admin can modify detection key configurations and apply changes to existing detection records.

Procedure

Navigate to All > Vulnerability Response > Configure Detection Granularity.
Open a detection key configuration record.

The Configuration Item (CI) field is available. The Asset ID and Configuration Item fields are editable, while all other fields can't be edited.
Select Configuration Item, de-select Asset ID to switch to CI-based detection.
If both Asset ID and CI are selected, the system displays an error message.
- The record moves to a Pending state.
- An info message appears, notifying that changes are made but not yet applied to existing detections.
Select Apply Changes.

For the following cases, the detection key can't be modified:
- If the integration for the respective scanner or the CI lookup rules job is running, then detection key can’t be modified.
- If the detection key has been updated and the scheduled job is run to update the detections with the new key, configurations can't be modified until the job is completed.
- If the detection key update job is running, then the integration for that particular scanner will not run.
The scanner for which the detection keys are changed:
- Fixing the detections for updated key for Qualys
- Fixing the detections for updated key for Rapid7
- Fixing the detections for updated key for Tenable All existing detection and vulnerable item records are updated using the revised detection key. New detections generated by integrations use the new detection key fields.

Parent Topic:Detection key configurations for Vulnerability Response

54 lines · 2.8 KB Wrap lines

---
title: Run detection key configuration
description: Use the revised detection key to update the existing detections and vulnerable item records.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/run-detection-key-configuration.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-11-06"
reading_time_minutes: 1
breadcrumb: [Detection key configurations for Vulnerability Response, Advanced Vulnerability Response configuration tasks, Vulnerability Response implementation, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Run detection key configuration

Use the revised detection key to update the existing detections and vulnerable item records.

## Before you begin

Role required: sn\_vul.vulnerability\_admin can modify detection key configurations and apply changes to existing detection records.

## Procedure

1. Navigate to **All** &gt; **Vulnerability Response** &gt; **Configure Detection Granularity**.

2. Open a detection key configuration record.

The Configuration Item \(CI\) field is available. The Asset ID and Configuration Item fields are editable, while all other fields can't be edited.

3. Select **Configuration Item**, de-select **Asset ID** to switch to CI-based detection.

4. If both Asset ID and CI are selected, the system displays an error message.

- The record moves to a **Pending state**.
- An info message appears, notifying that changes are made but not yet applied to existing detections.
5. Select **Apply Changes**.

For the following cases, the detection key can't be modified:

- If the integration for the respective scanner or the CI lookup rules job is running, then detection key can’t be modified.
- If the detection key has been updated and the scheduled job is run to update the detections with the new key, configurations can't be modified until the job is completed.
- If the detection key update job is running, then the integration for that particular scanner will not run.
6. The scanner for which the detection keys are changed:

- Fixing the detections for updated key for Qualys
- Fixing the detections for updated key for Rapid7
- Fixing the detections for updated key for Tenable
All existing detection and vulnerable item records are updated using the revised detection key. New detections generated by integrations use the new detection key fields.

**Parent Topic:**[Detection key configurations for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/detection-key-configurations-for-vr.md)