This document outlines security best practices and procedures to prevent sensitive information from being committed to the repository.

• .env files (environment variables with secrets)
• SSL certificates (.pem, .crt, .key, .pfx, .p12)
• Kubernetes secrets (secrets.yaml)
• API keys and tokens
• Database credentials
• Private keys and certificates

• .env.template (template without real values)
• k8s/secrets.template.yaml (template without real secrets)
• Configuration examples with placeholder values

• Comprehensive patterns for sensitive file types
• Multiple layers of protection
• Regular expressions for secret detection

• Automatically blocks commits with sensitive files
• Scans file names and content for secrets
• Requires manual override for suspicious content

• .env.template - Safe environment template
• k8s/secrets.template.yaml - Safe Kubernetes secrets template

git clone <repository-url>
cd game-app-laptop-demo

cp .env.template .env
# Edit .env with your actual values

cp k8s/secrets.template.yaml k8s/secrets.yaml
# Edit with base64 encoded values

git status
# Should NOT show .env or secrets.yaml files

• No .env files in staging
• No SSL certificates (.pem, .crt, .key)
• No secrets.yaml files
• No hardcoded passwords or API keys
• Template files are properly named (.template)
• Run git status to verify

1. IMMEDIATELY revoke exposed credentials
2. Remove files from git history:

   git filter-branch --force --index-filter \
     'git rm --cached --ignore-unmatch <file>' \
     --prune-empty --tag-name-filter cat -- --all

3. Force push to remote:

   git push origin --force --all

4. Notify team members to reset their local repos

1. Review the detected sensitive files
2. Remove them from staging: git restore --staged <file>
3. Add to .gitignore if needed
4. Retry the commit

• GitHub Security Best Practices
• Kubernetes Secrets Management
• Environment Variables Best Practices

If you discover a security issue:

1. DO NOT commit the fix to the repository
2. Contact the security team immediately
3. Follow the emergency procedures above

Remember: Security is everyone's responsibility. When in doubt, ask before committing!