Security Policy

This package contains guidance, not a deployable service. Security issues here usually fall into one of these categories:

• unsafe operational advice
• insecure coding examples
• recommendations that weaken release or access controls
• documentation that encourages leaking secrets or bypassing auditability

Reporting

Report a security problem in this guidance through the reporting channel in the repository's root SECURITY.md. Include the affected file, the risky statement or example, why it is unsafe, and a safer alternative.

Do not open a public issue for material that could encourage insecure deployments before it is reviewed.

Scope

This policy applies to:

• playbooks
• checklists
• templates