Source: https://atomic-works-test.docs-staging.pageloop.ai/data-library/vulnerabilities/dashboard-actions/set-up-vulnerability-monitoring-source # Set Up Vulnerability Monitoring Source --- description: >- Learn how to connect your infrastructure or codebase scanners to Sprinto to automatically detect and track vulnerabilities. --- # Set Up Vulnerability Monitoring Source You can integrate Sprinto with widely used vulnerability monitoring tools to automate detection and tracking of security flaws across your infrastructure and application code. Once connected, Sprinto retrieves vulnerability logs from the configured source and automatically triggers system-status checks mapped to compliance frameworks. *** ### Before You Begin Ensure the following: * You have administrator access to the Sprinto dashboard. * You have administrator or integration-level permissions on the monitoring source (e.g. AWS, GitLab, Snyk). * Your desired source is supported by Sprinto (see list below). *** ### Supported Monitoring Sources Sprinto supports integrations across:
CategoryExamples
InfrastructureAWS Inspector, Google Security Center
CodebaseGitLab, Dependabot, SLSCan, Snyk, SonarCloud
EndpointsCrowdStrike Spotlight, Microsoft Defender for Endpoints
TicketingJira
If your service is not supported, you can instead configure manual workflow checks. See: [Create and Manage Workflow Checks](https://chatgpt.com/g/g-p-682c1aeced3481919aef33cebb2d490f-sprinto-documentation-overhaul/c/686e0f92-5a1c-8006-b421-407af2e29ff7). *** ### Procedure To connect a new vulnerability monitoring source: 1. Log in to the Sprinto Dashboard. 2. Go to **Data Library > Vulnerabilities**. 3. Click **+ Add monitoring source**.
4. In the pop-up, browse or search the available services (For example, GitLab, AWS Inspector and so on). 5. Click **Choose** next to the service you want to add.
6. Follow the onscreen instructions to authenticate and configure the integration. * For example, when configuring Jira, Sprinto will: 1. Run checks across all tracked projects. 2. Continuously track vulnerabilities. 3. Monitor SLA compliance for issue closures. 7. Once successfully connected, you’ll see the service listed on the **Overview** tab with open vulnerabilities (if any) and associated compliance controls. *** ### Manage AWS Inspector Resources Sprinto allows you to control which AWS Inspector resources are actively monitored for vulnerabilities. This helps you limit monitoring to specific assets within a connected AWS account, ensuring that only relevant resources are included in vulnerability tracking and compliance checks. Use this option to add or remove monitored Inspector resources without disconnecting the AWS Inspector integration. #### Procedure 1. Go to **Data Library > Vulnerabilities**. 2. Select **AWS Inspector** from the left navigation panel. 3. Click **Manage AWS Inspector**.
4. In the side panel, locate the AWS account you want to update. 5. Click **Manage assets** next to the account.
6. In the **Choose Inspector resources to monitor** window: 1. Review the available Inspector resources. 2. Select the resources you want Sprinto to monitor. 3. Clear the selection for resources you no longer want monitored. 7. Click **Choose** to save the changes.
Sprinto updates the monitored asset list for the selected AWS account and displays the revised asset count under the account details. *** ### Troubleshooting If you see an _Issues detected in Integrations_ banner, this means Sprinto has detected sync or credential errors in one or more sources. * Click **View and Fix** to go to the Integrations page. * Follow the prompts to reauthenticate or reconfigure the affected integration. *** ### Result Your monitoring source is now active. Sprinto will begin fetching vulnerability logs and activating system-status checks as per your compliance setup. You can now: * View vulnerabilities under each service tab (e.g. _Google Security Center_). * Track severity, assigned owner, and due dates. * Trigger remediation workflows based on the source findings.