Skip to content

feat: add security governance (CODEOWNERS, SECURITY.md, .gitignore hardening)#73

Open
pdettori wants to merge 2 commits intomainfrom
orchestrate/security
Open

feat: add security governance (CODEOWNERS, SECURITY.md, .gitignore hardening)#73
pdettori wants to merge 2 commits intomainfrom
orchestrate/security

Conversation

@pdettori
Copy link
Collaborator

Summary

Phase 5 of repo orchestration — security governance files.

New files

.github/CODEOWNERS

  • Routes all PRs to @kagenti/maintainers for review
  • Explicit ownership for src/, plugins/, .github/, governance docs
  • Triggers GitHub's automatic review request on every PR

SECURITY.md

  • Private vulnerability reporting via GitHub Security Advisories (link included)
  • Response timeline table (48h ack, 7-day initial assessment)
  • Security controls table referencing all controls deployed in this repo (trivy, dependabot, bandit, codeql, scorecard, SHA-pinned actions)
  • Security-sensitive areas highlighted for reviewers

Updated files

.gitignore — added missing security-critical patterns:

Pattern Reason
.env.*, .env.local Credential env files
.vscode/ VS Code workspace settings
.idea/ JetBrains IDE files (was commented out)
*.pem, *.key, *.p12, *.jks TLS/crypto private keys
kubeconfig, *kubeconfig* Kubernetes credentials
credentials.*, secrets.* Generic secret files

Already present (not changed)

File Notes
LICENSE Apache 2.0 already in repo
CONTRIBUTING.md References kagenti/kagenti main CONTRIBUTING guide

Recommended branch protection rules for main

These cannot be set via PR — a maintainer should configure in Settings → Branches:

  • Require pull request reviews before merging (1 approval minimum)
  • Require status checks: build (3.11), build (3.12), dependency-review, bandit, trivy-fs
  • Require branches to be up to date before merging
  • Do not allow bypassing the above settings
  • Restrict force pushes to main
  • Require conversation resolution before merging

Establish security governance baseline:

- .github/CODEOWNERS: auto-review routing to @kagenti/maintainers
  for all files, with explicit ownership for src/, plugins/, .github/,
  and governance docs
- SECURITY.md: vulnerability reporting via GitHub Security Advisories,
  response timeline, supported versions, security controls table
  (trivy, dependabot, bandit, codeql, scorecard, SHA-pinned actions),
  and security-sensitive areas for reviewers
- .gitignore: add missing patterns:
  - .env.* and .env.local (credential files)
  - .vscode/ (VS Code workspace)
  - .idea/ (JetBrains IDEs, was commented out)
  - *.pem, *.key, *.p12, *.jks (TLS/crypto keys)
  - kubeconfig, *kubeconfig* (Kubernetes credentials)
  - credentials.*, secrets.* (generic secret files)

LICENSE (Apache 2.0) and CONTRIBUTING.md were already present.

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
Replace @kagenti/maintainers with @kagenti/plugin-adapters-maintainers
per reviewer feedback.

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
Copy link
Collaborator Author

@pdettori pdettori left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated — all occurrences of @kagenti/maintainers in CODEOWNERS replaced with @kagenti/plugin-adapters-maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants