Skip to content

Security: certforge/GH_500_Cert_Prep

.github/SECURITY.md

Security Policy

About This Repository

This is an educational repository for GH-500: GitHub Advanced Security exam preparation. It contains intentionally vulnerable code in demos/05-code-scanning/vulnerable-app/ for learning purposes.

Supported Versions

This repository is a study resource, not a deployed application. There are no versioned releases to support. Content is kept current with the official exam objectives.

Reporting a Security Issue

Important

If you discover a security vulnerability in this repository's actual code (e.g., a script that could be exploited, a workflow with a security flaw), please report it responsibly.

Do NOT open a public GitHub issue for security vulnerabilities.

Reporting Process

  1. Use GitHub's private vulnerability reporting feature (available in the Security tab of this repo)
  2. Or email: security@example.com (replace with your contact)

What to Include in Your Report

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • (Optional) Suggested fix

Response Timeline

Stage Timeline
Acknowledgment Within 48 hours
Initial assessment Within 7 days
Fix or mitigation Within 30 days
Public disclosure Coordinated with reporter

What Is NOT a Vulnerability

The following are intentional and should not be reported:

File Intentional Issue
demos/05-code-scanning/vulnerable-app/app.py SQL injection, XSS, command injection (CodeQL demo)
demos/05-code-scanning/vulnerable-app/app.js Prototype pollution, SQL injection (CodeQL demo)
demos/03-dependabot/package.json Outdated/vulnerable npm dependencies (Dependabot demo)
demos/03-dependabot/requirements.txt Outdated/vulnerable Python dependencies (Dependabot demo)
demos/02-secret-scanning/sample-secrets.md Non-functional credential patterns (secret scanning demo)

These files exist explicitly to demonstrate GHAS detection capabilities.

Security Best Practices for Contributors

When contributing to this repository:

  1. Do not commit real credentials or API keys
  2. Do not add real working exploits (demo code should be functional but clearly non-production)
  3. Keep workflow files secure — avoid injection vulnerabilities in GitHub Actions YAML
  4. Sign your commits when possible (git config commit.gpgsign true)

There aren’t any published security advisories