Easily manage and configure integrations with supported third-party services.
Navigation
Integrations are configured from the Integrations page, accessible from your user account in the top right corner. [1]
Note: Only users with the Client Manager role can configure integrations.
Cloud Scanning Integrations
Connect cloud infrastructure to automatically add assets to your external attack surface.
Amazon Web Services
Automatically add cloud assets from AWS to your external attack surface. Navigate to Integrations and select Configure under Amazon Web Services. Setup instructions are available in the platform.
Multiple AWS connections are supported once the initial account is configured.
Microsoft Azure
Automatically add cloud assets from Microsoft Azure to your external attack surface. Navigate to Integrations and select Configure under Microsoft Azure. Setup instructions are available in the platform.
Multiple Azure connections are supported once the initial account is configured.
Ticketing Integrations
Sync findings and remediation activity with your issue tracking tools.
JiraCloud by Atlassian
The Jira integration syncs Sprocket findings to your Jira site as issues. Comments made on either platform are synced to the other automatically.
Setting up the Integration
To connect Jira, navigate to Integrations from your user account menu and select the Jira by Atlassian option, then click Configure.
Note: Ensure you have a Jira administrator present before proceeding.
- Click the Atlassian Marketplace link to navigate to the Jira Marketplace.
- Install the Sprocket Security app from the Atlassian Marketplace.
- If you have multiple Jira sites, select the site you want to install the integration to.
- Navigate to the application management page in Jira as an administrator and select the Sprocket application.
- Select Get Started from the dropdown menu.
-
You will be directed to a setup screen.
Note: The person completing this step must have a Sprocket platform account with the ability to configure integrations. If your Jira administrator does not have a Sprocket account, share the setup link with a Client Manager who does.
- You will be redirected to the Sprocket platform to activate the integration.
- Click Activate. Once activated, you can proceed to configure the integration.
Configuring the Integration
After activating, you can configure the integration at the global level or per Sprocket project.
Configure the following settings:
Jira Project
The Jira project where findings will be created when synced from the Sprocket platform.
Issue Type
The issue type Sprocket findings will be created as in Jira, such as Bug, Task, or Story.
Retest Ready Column
The Jira column or status that, when a finding is moved to it, will automatically update the finding's state to Retest Ready in the Sprocket platform. This triggers your Sprocket team to begin retesting.
Note: These settings can be configured independently for each project type in your Sprocket account.
Once your settings are saved, you can begin syncing findings to Jira.
Syncing Findings
New findings created by Sprocket will sync to your Jira site automatically once the integration is active.
To sync an existing finding manually:
- Open the finding you want to sync.
- Click the dropdown menu in the upper right corner of the finding.
- Select Sync to Jira.
- The finding will appear in your Jira board.
Once your team has resolved the issue in Jira, move it to the Retest Ready column you configured. This will automatically update the finding's state to Retest Ready in the Sprocket platform and notify your Sprocket team to begin retesting.
Two-Way Comment Sync
Comments are synced between the Sprocket platform and Jira in both directions.
- Comments made by your Sprocket team in the platform will appear on the linked Jira issue.
- Comments added to the Jira issue will sync back to the finding in the Sprocket platform.
This allows your team to ask questions or share context in Jira without needing to log in to the Sprocket platform directly.
Disabling the Automatic Sync
By default, all new findings are synced to Jira automatically. You can disable automatic sync per project type if needed.
You may want to disable automatic sync if:
- Your Sprocket testing generates a high volume of findings and you want to avoid overwhelming your development or IT teams
- You want to review findings before sending them to your internal teams
To disable automatic sync for a project type, change the toggle to Disable to turn off automatic sync. [1]
ServiceNow
The ServiceNow integration syncs Sprocket findings to your ServiceNow instance as Service Desk Incidents. Comments made on either platform are synced to the other automatically.
Setting up the Integration
To connect ServiceNow, navigate to Integrations from your user account menu and select Configure under ServiceNow.
You will need to provide the following:
- Instance URL: The web address of your ServiceNow instance
- User credentials: A dedicated ServiceNow user account for the integration
The ServiceNow user account requires the following permission roles to function correctly:
- sn_incident_write
- sn_incident_read
- itil_admin
- u_ticket_user
- sn_si.manager
- admin
For guidance on setting up a ServiceNow user with these roles, refer to the ServiceNow configuration guide at https://docs.synqly.com/guides/provider-configuration/servicenow-ticketing-setup
Custom Table (optional)
If your ServiceNow instance uses a custom table for incidents rather than the default Incidents table, you can enter that table name here. Your instance must already have this table configured, and it must be based on the default Incidents table. If your instance has been heavily customized, reach out to your Sprocket team before proceeding to confirm compatibility.
Once you have entered your details, activate the integration.
Configuring the Integration
After activating, locate the ServiceNow integration, on the Integrations page and select Edit to configure your settings.
Here you will map Sprocket findings to a category in your ServiceNow instance. This controls how findings are classified when they appear as incidents.
You can configure different category mappings per Sprocket project. For example, findings from your Web Application Testing project can be mapped to a "Web App" category to distinguish them from External Pentest findings. This is optional but recommended for organizations with multiple active projects.
Syncing Findings
New findings and their comments will sync to ServiceNow automatically once the integration is active.
To sync an existing finding manually:
- Open the finding you want to sync.
- Select the sync option from the finding.
- Choose one of the following:
- Create a new incident: Creates a new incident in your ServiceNow instance for this finding
- Link to an existing incident: Links the finding to an incident that already exists in your instance.
- Once the sync is complete, a confirmation comment will appear on the finding
and on the linked incident in ServiceNow.
Stopping a Sync
You have two options for stopping the sync:
- Deactivate the integration entirely to stop all findings from syncing to ServiceNow.
- Stop syncing a single finding by selecting the stop sync option on the individual finding.
Comment Syncing
Comments made in ServiceNow are synced back to Sprocket via a callback rule installed automatically during setup. This rule lives under System Definition > Business Rules in your ServiceNow instance. If you need to locate it, look for rules with the Sprocket naming convention shown below:
Note: Disabling this business rule will prevent comments made in ServiceNow from appearing in the Sprocket portal. Do not disable it unless you intentionally want to stop comment syncing.
Notification Integrations
Get real-time notifications from findings to enable swift action, reduce response times, and strengthen overall threat management.
Slack
Get real-time notifications from findings directly in Slack. Navigate to Integrations and select Configure under Slack. Setup instructions are available in the platform.
Important: Public Slack channels work by default. If you want to use a private channel, invite the bot to that channel in Slack before setting up the integration.
Microsoft Teams
Get real-time notifications from findings directly in Microsoft Teams. Setup instructions are available in the platform. Navigate to Integrations and select Configure under Microsoft Teams to get started.
Troubleshooting
If you receive an error when setting up the Teams integration, check the following:
- Ensure Power Automate is not blocked in your organization.
- Go to Teams Admin Center admin.teams.microsoft.com
- Navigate to Manage apps
- Search for Power Automate and confirm it is allowed
-
Check Team Owner Permissions, the channel you are integrating with must have at least one member with the Owner role
- Go to Teams Admin Center
- Navigate to Teams > Manage Teams
- Select your team > Members
- Confirm at least one member (the one building the integration) has the Owner role
If neither of these settings can be accessed, contact your Microsoft 365 administrator.