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.

​
Overview

GitHub is the world’s most widely used code hosting and collaboration platform. DSALTA integrates with GitHub to monitor repository security, code review compliance, vulnerability alerts, secret scanning, and change management via GitHub Issues.
Read-only access. DSALTA never modifies, creates, or deletes resources in your GitHub environment. All API access is strictly read-only.

​
Integration Details

PropertyValue
CategoryCode Repository & Security
Data Library ModulesAccess, Code Changes, Vulnerabilities, Changes
AuthenticationGitHub App installation with read-only repository access
Sync FrequencyEvery 24 hours (manual sync available)
PermissionsRead-only

​
What Data DSALTA Collects

When you connect GitHub, DSALTA automatically collects the following data on every sync cycle:
  • Repository configurations and visibility
  • Branch protection rules and enforcement
  • Pull request reviews and CI/CD check results
  • Dependabot vulnerability alerts
  • Code scanning and secret scanning alerts
  • GitHub Issues for change management tracking
  • User access and team permissions
Every record includes the integration name as its source, a sync timestamp, and is treated identically to manually entered records by auditors.

​
Key Use Cases

  • Enforce branch protection rules on all repositories
  • Monitor Dependabot alert resolution within SLA
  • Detect exposed secrets via secret scanning
  • Track code review compliance (author ≠ reviewer)
  • Manage change requests via GitHub Issues

​
How to Connect

1

Navigate to Integrations

Go to Settings → Integrations in your DSALTA dashboard and find GitHub in the catalog.
2

Review Permissions

Review the permissions DSALTA requires. All access is read-only. Click Connect.
3

Authenticate

Follow the on-screen instructions to authenticate with your GitHub account. Admin-level access is required for the initial setup.
4

Configure Scope

Select which accounts, projects, or resources DSALTA should monitor. You can adjust this later from the integration settings.
5

Initial Sync

DSALTA performs an initial data pull (typically 5–15 minutes). Automated compliance tests are generated immediately after sync completes.
After connecting, allow 15–20 minutes for the initial data sync. DSALTA may take up to 24 hours to fully evaluate all synced data and activate all relevant compliance tests.

​
Automated Compliance Tests

When you connect GitHub, DSALTA automatically generates the following compliance tests. Each test runs every 24 hours and produces pass/fail evidence for your auditor.
TestDescription
Branch protection should be enabled on repositoriesChecks that branch protection rules are enabled on GitHub repositories.
Dependabot alerts should be resolvedChecks that Dependabot vulnerability alerts are resolved.
User access to critical systems should be validChecks that users with access to critical systems are authorized in GitHub.
Code scanning alerts should be resolvedChecks that code scanning alerts are identified and resolved.
Secret scanning alerts should be resolvedChecks that secret scanning alerts are identified and resolved.
Dependabot alerts should be resolved within SLAChecks that Dependabot vulnerability alerts are resolved within the defined SLA.
Branch protection should be enabledChecks that branch protection is enabled on all GitHub repositories.
Change request tickets should be resolved within 30 daysChecks that change request tickets are resolved within 30 days.
All change tickets should have an assigneeChecks that all change management tickets have an assignee.
Ticketing system for change management should be configuredChecks that a ticketing system for change management is set up.
At least one change management system should be connectedChecks that at least one change management system is connected.
Tests run automatically every 24 hours. Failed tests generate alerts and appear in your compliance dashboard with remediation guidance. All test results are stored as audit evidence with timestamps.

​
Compliance Frameworks

This integration provides evidence for the following compliance frameworks:

SOC 2

Access controls, monitoring, and change management evidence.

ISO 27001

Asset management, access control, and operations security evidence.

GDPR

Access records and data processing evidence.

​
Troubleshooting

Re-authenticate by going to Settings → Integrations → GitHub and clicking Reconnect. This usually happens when API tokens expire or permissions change.
Verify that the connected account still has the required admin permissions. Try a manual sync from the integration settings page. If the issue persists, check your GitHub API rate limits.
Tests generate after the first successful data sync. If sync completed but tests are missing, ensure the relevant features are configured in GitHub (e.g., GuardDuty must be enabled in AWS for GuardDuty tests to appear).
DSALTA syncs all users visible to the connected admin account. If users are missing, verify they are within the scope you configured during setup. Suspended or deleted accounts may not appear.