Configure integrations
DNS Posture Management supports 2 categories of integrations:
DNS integrations: AWS Route 53, NS1, DigiCert UltraDNS, and Cloudflare. Connecting a DNS provider integration gives Posture Management zone-level access to DNS data, enabling policy checks that external scanning can’t perform. See Scan coverage for a full breakdown of what each integration unlocks.
Other integrations: Atlassian Jira and ServiceNow. Connecting a ticketing integration enables ticket creation directly from findings in Posture Management.
Select Integrations from the left navigation menu to view connected integrations and connect new ones.
Connecting AWS Route 53 enables enhanced policy checks that require zone-level DNS data. Notice: You need an AWS API key and secret key with permissions to access Route 53.
Select Integrations from the left navigation menu.
Under DNS Integrations, select AWS Route 53.
In the Add integration panel:
In API Key, enter your AWS API key.
In Secret Key, enter your AWS secret key.
Select Connect.
Connecting NS1 enables enhanced policy checks that require zone-level DNS data. Notice: You need an NS1 API key.
Select Integrations from the left navigation menu.
Under DNS Integrations, select NS1.
In the Add integration panel:
In API Key, enter your NS1 API key.
Select Connect.
Connecting DigiCert UltraDNS enables enhanced policy checks that require zone-level DNS data. Notice: You need your DigiCert UltraDNS username and password.
Select Integrations from the left navigation menu.
Under DNS Integrations, select DigiCert UltraDNS.
In the Add integration panel:
In Username, enter your UltraDNS username.
In Password, enter your UltraDNS password.
Select Connect.
Connecting Cloudflare enables enhanced policy checks that require zone-level DNS data. Notice: You need a Cloudflare API token with DNS read permissions.
Select Integrations from the left navigation menu.
Under DNS Integrations, select Cloudflare.
In the Add integration panel:
In API Token, enter your Cloudflare API token.
Select Connect.
Connecting Atlassian Jira enables ticket creation directly from findings in Posture Management.
Select Integrations from the left navigation menu.
Under Other Integrations, select Atlassian Jira.
In the Add integration panel:
(Optional) In Integration Name, enter a name for this connection. Use this field to distinguish between multiple Jira instances.
In Base URL, enter the base URL of your Jira instance.
In Project Key, enter the project key where tickets will be created.
In Issue Type, enter the issue type to use for created tickets.
In Email, enter the email address associated with your Jira account.
In API Token, enter your Jira API token.
Select Connect.
Connecting ServiceNow enables ticket creation directly from findings in Posture Management.
Notice: You need the following before you begin:
The base URL of your ServiceNow instance (for example, https://yourcompany.service-now.com)
A ServiceNow API key
Select Integrations from the left navigation menu.
Under Other Integrations, select ServiceNow.
In the Add integration panel:
(Optional) In Integration Name, enter a name for this connection. Use this field to distinguish between multiple ServiceNow instances.
In Base URL, enter the base URL of your ServiceNow instance.
(Optional) In Category, enter the default category to apply to raised tickets.
(Optional) In Urgency, enter the default urgency to apply to raised tickets.
In API Key, enter your ServiceNow API key.
Select Connect.
Use Update to replace the credentials for a connected integration. For example, to rotate an API key or update a password. The Update integration panel shows the existing saved credentials. The Update button stays unavailable until you select Change credential and enter new values.
In the Connected integrations section, select the ⋮ icon on the integration card.
Select Update.
In the Update integration panel, select Change credential.
Enter the new credentials.
Select Update.
Disabling an integration removes the connection but retains the saved credentials. DNS provider integrations that are disabled revert to external scan coverage for any policies that previously used zone-level data.
In the Connected integrations section, select the ⋮ icon on the integration card.
Select Disable.
Re-enabling an integration restores the connection using the previously saved credentials. No credential re-entry is required.
In the Connected integrations section, locate the disabled integration card.
Select Connect.