Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossaryContacting Support and Reporting Bugs
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidanceDetermining Control Applicability
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: AzureAuto Checks: GCPAuto Checks: GitHubEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
GitHub Auto Checks Detailed Explanations
Ensure secret scanning is enabled to detect sensitive dataEnsure code owner approval is required for owned code changesEnsure at least two approvals are required before merging codeEnsure branches are deleted automatically after mergingEnsure unresolved conversations block mergesEnsure force push is disabled for all branchesEnsure admins are subject to branch protection rulesEnsure a CODEOWNERS file exists in the repositoryEnsure inactive repositories are archivedEnsure all required status checks pass before mergingEnsure linear history is enforced on the default branchEnsure branch protection is enforced on the default branchEnsure the default branch cannot be deletedEnsure vulnerability scanning is enabled for repository dependenciesEnsure public repositories include a SECURITY.md fileEnsure all organization members have MFA enabledEnsure only signed commits are accepted

Ensure vulnerability scanning is enabled for repository dependencies

Framework Reference: A.8.8 (Management of technical vulnerabilities) Integration: GitHub – Dependabot & Dependency Graph

Why this matters

Modern software development relies heavily on open-source dependencies, which may include known vulnerabilities.
Without automated vulnerability scanning, these risks can remain undetected, exposing your codebase to potential exploitation, data breaches, or supply-chain attacks.

Enabling dependency scanning ensures that:

  • GitHub continuously monitors your project’s dependency graph
  • Known vulnerabilities are detected and reported through Dependabot alerts
  • Developers receive proactive notifications to update or patch vulnerable packages

Without this control, outdated or insecure dependencies can persist unnoticed in production systems.

What this check does

This check verifies that dependency vulnerability scanning is enabled for the repository. Specifically, it confirms that:

  • Dependency graph is activated
  • Dependabot alerts are turned on to detect and notify about vulnerable dependencies

GitHub’s Dependabot feature automatically cross-references your repository’s dependencies against public vulnerability databases.

How to fix it

From the GitHub Web Console

  1. Go to your repository on GitHub.
  2. Navigate to Settings → Security & analysis.
  3. Under Dependency graph, ensure that Enable is selected.
  4. Under Dependabot alerts, click Enable Dependabot alerts.
  5. (Optional) Also enable Dependabot security updates to automatically create pull requests for vulnerable dependency upgrades.

GitHub will begin scanning your project’s dependency manifests and alert you if any vulnerabilities are detected.

Exceptions

  • Private repositories require GitHub Advanced Security or GitHub Enterprise to use Dependabot alerts.
  • Dependabot supports most common package ecosystems (npm, Maven, pip, RubyGems, Composer, etc.); unsupported dependency types won’t generate alerts.
  • The dependency graph and alerts must be enabled per repository—they are not inherited automatically from the organization level.

Further Resources

Was this article helpful?

Powered by Product Fruits