Trigger conditions in a configuration item
Summarize
Summary of Trigger Conditions in a Configuration Item
This guide outlines how to configure trigger conditions for profiles within Microsoft Defender for Endpoint integration in ServiceNow. Trigger conditions ensure that profiles run automatically when specific security incidents are created, enhancing incident response efficiency.
Show less
Key Features
- Automatic Execution: Profiles can run automatically upon the creation of a matching security incident.
- Manual Execution: If no trigger condition is set, profiles can still be manually executed via the Run EDR profile(s) form.
- Integration with CMDB: The Configuration Item (CI) field on the security incident is used to retrieve asset information from the ServiceNow AI Platform Configuration Management Database (CMDB).
- Alternate CI Fields: You can select alternate fields on the security incident for endpoint identification, ensuring profiles run even if the CI field is not populated.
Key Outcomes
By effectively configuring trigger conditions, you can ensure that your profiles are executed in response to relevant security incidents, improving your incident management process. The use of alternate CI fields provides flexibility and reliability in identifying endpoints, thereby streamlining data retrieval from Microsoft Defender for Endpoint.
After you create a profile and select the Microsoft Defender for Endpoint capabilities that you want the profile to run, configure the profile settings so that the profile runs only when a set of specific conditions is met.
How to trigger conditions in a configuration item
You can set trigger conditions so the profile runs automatically whenever a security incident is created that matches the trigger condition. If the trigger condition is not set, these profiles can be manually run by clicking the Run EDR profile(s) form on the security incident, and selecting the profile.
By default, the integration uses the Configuration Item (CI) field on the Security incident. This value is used to match the IDs of your assets with the information stored in the ServiceNow AI Platform Configuration Management Database (CMDB). When a security incident is created, and a profile is run either automatically or manually, the CMDB is searched to retrieve the host name or IP address based on the value of the CI field. The host name or IP is used to resolve the Agent ID on Microsoft Defender for Endpoint to identify the endpoint.
In an ideal scenario, a matching value is found in the database, and data is gathered from the Microsoft Defender for Endpoint console for the matching asset. The data for various capabilities are pulled into your ServiceNow AI Platform Configuration Management Database (CMDB) instance and displayed in the related lists of a security incident. When the Configuration item (CI) field is not populated on the security incident with a host name with or an IP address that matches the database, you can select an alternate field on the security incident that contains either the host name or the IP to perform the Agent ID resolution.
During the configuration step of the profile setup, you can select an alternate CI field for endpoint identification to ensure that you are able to identify the endpoint on Microsoft Defender for Endpoint. You can select any field on the security incident as an alternate CI trigger field, including custom fields that you create. By selecting this alternate CI field as a backup, you ensure that your profiles run even if the CI field is not populated on the associated security incident on incident creation.