Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that code scanning alerts are identified and resolved.

​
Why This Matters

Unresolved vulnerability alerts represent known security weaknesses in your codebase or dependencies. Attackers actively scan for known CVEs and can exploit them within hours of public disclosure. Timely remediation within defined SLAs is required by SOC 2 (CC7.1) and ISO 27001 (A.12.6.1).

​
What DSALTA Checks

DSALTA connects to your GitHub environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → GitHub.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Navigate to your GitHub security dashboard.
  2. Review all open vulnerability alerts sorted by severity (Critical → High → Medium → Low).
  3. For each alert, apply the recommended fix (update dependency, patch code, rotate secret).
  4. Merge the fix and verify the alert is resolved.
  5. Set up automatic security updates where possible (e.g., Dependabot auto-merge for patch versions).
  6. Define an SLA for vulnerability remediation: Critical within 24 hours, High within 7 days, Medium within 30 days.
  7. Once all alerts are resolved, DSALTA will update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the GitHub integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in GitHub.