Contents Security Operations Previous Topic Next Topic ServiceNow Security Operations integration development guidelines Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics Share ServiceNow Security Operations integration development guidelines The ServiceNow platform provides several mechanisms for developing integrations with external systems. The ServiceNow Security Operations product suite adds integration capabilities intended to streamline the process of integrating with security-focused external systems. Most of the concepts in this guide assume some familiarity with standard ServiceNow functionality. To integrate with the Security Operations suite, at a minimum, knowledge of the following ServiceNow concepts is required: Script includes Inbound/outbound web services Data sources Import sets Transform maps Technology Partner Program Any requirements for application certification or guidelines given in the Technology Partner Program literature supersede any information in this guide. This guide is not a replacement for the Technology Partner Program literature and serves only as a supplement to existing documentation. For more information, see Technology Partner Program training course blog post. Types of ServiceNow integrations providedThe Security Operations applications (Security Incident Response, Threat Intelligence, and Vulnerability Response) can be seamlessly integrated with other ServiceNow applications to enhance their functionality. Security Operations Integration ConfigurationsMany of the integrations included in the base system require little or no setup, and operate in the same way. Certain integrations, such as the Qualys Cloud Platform, however, require separate steps for setting up the integration. Others support different sets of scan and lookup types and different rate limits.Rules for identifying configuration items from third-party integrationsWhen data is imported from a third-party integration, the host information is searched automatically for matches in the CMDB. When a host ID match is found, it is used as the Configuration item field in the vulnerable item record. If a match is not found, or the host ID field is empty, the rules use the other host information to correctly identify the CI.Tips for writing integrationsAvoid some of the pitfalls you can encounter when writing your own integrations by following these guidelines.Integration troubleshootingThese troubleshooting suggestions can help you resolve common issues you can encounter when setting up or running integrations. On this page Send Feedback Previous Topic Next Topic
ServiceNow Security Operations integration development guidelines The ServiceNow platform provides several mechanisms for developing integrations with external systems. The ServiceNow Security Operations product suite adds integration capabilities intended to streamline the process of integrating with security-focused external systems. Most of the concepts in this guide assume some familiarity with standard ServiceNow functionality. To integrate with the Security Operations suite, at a minimum, knowledge of the following ServiceNow concepts is required: Script includes Inbound/outbound web services Data sources Import sets Transform maps Technology Partner Program Any requirements for application certification or guidelines given in the Technology Partner Program literature supersede any information in this guide. This guide is not a replacement for the Technology Partner Program literature and serves only as a supplement to existing documentation. For more information, see Technology Partner Program training course blog post. Types of ServiceNow integrations providedThe Security Operations applications (Security Incident Response, Threat Intelligence, and Vulnerability Response) can be seamlessly integrated with other ServiceNow applications to enhance their functionality. Security Operations Integration ConfigurationsMany of the integrations included in the base system require little or no setup, and operate in the same way. Certain integrations, such as the Qualys Cloud Platform, however, require separate steps for setting up the integration. Others support different sets of scan and lookup types and different rate limits.Rules for identifying configuration items from third-party integrationsWhen data is imported from a third-party integration, the host information is searched automatically for matches in the CMDB. When a host ID match is found, it is used as the Configuration item field in the vulnerable item record. If a match is not found, or the host ID field is empty, the rules use the other host information to correctly identify the CI.Tips for writing integrationsAvoid some of the pitfalls you can encounter when writing your own integrations by following these guidelines.Integration troubleshootingThese troubleshooting suggestions can help you resolve common issues you can encounter when setting up or running integrations.
ServiceNow Security Operations integration development guidelines The ServiceNow platform provides several mechanisms for developing integrations with external systems. The ServiceNow Security Operations product suite adds integration capabilities intended to streamline the process of integrating with security-focused external systems. Most of the concepts in this guide assume some familiarity with standard ServiceNow functionality. To integrate with the Security Operations suite, at a minimum, knowledge of the following ServiceNow concepts is required: Script includes Inbound/outbound web services Data sources Import sets Transform maps Technology Partner Program Any requirements for application certification or guidelines given in the Technology Partner Program literature supersede any information in this guide. This guide is not a replacement for the Technology Partner Program literature and serves only as a supplement to existing documentation. For more information, see Technology Partner Program training course blog post. Types of ServiceNow integrations providedThe Security Operations applications (Security Incident Response, Threat Intelligence, and Vulnerability Response) can be seamlessly integrated with other ServiceNow applications to enhance their functionality. Security Operations Integration ConfigurationsMany of the integrations included in the base system require little or no setup, and operate in the same way. Certain integrations, such as the Qualys Cloud Platform, however, require separate steps for setting up the integration. Others support different sets of scan and lookup types and different rate limits.Rules for identifying configuration items from third-party integrationsWhen data is imported from a third-party integration, the host information is searched automatically for matches in the CMDB. When a host ID match is found, it is used as the Configuration item field in the vulnerable item record. If a match is not found, or the host ID field is empty, the rules use the other host information to correctly identify the CI.Tips for writing integrationsAvoid some of the pitfalls you can encounter when writing your own integrations by following these guidelines.Integration troubleshootingThese troubleshooting suggestions can help you resolve common issues you can encounter when setting up or running integrations.
