Skip to content

security-policies

Authentication patterns, data handling and secrets management rules

Metadados

  • category: security-policies
  • priority: high

Aplica-se a

  • all

Tags

  • security
  • auth
  • secrets

Conteudo do artefato

Security Policies

Purpose

Define security rules that agents must follow for authentication, authorization, data handling and secrets management.

Rules

  • Never hardcode secrets, keys or credentials in source code.
  • Use environment variables or a secrets manager for sensitive configuration.
  • Validate and sanitize all external inputs.
  • Apply the principle of least privilege for all access controls.
  • Log security-relevant events without exposing sensitive data.
  • Use parameterized queries or ORM methods to prevent injection.

Examples

  • Correct: apiKey = process.env.STRIPE_API_KEY
  • Wrong: const apiKey = "sk_live_12345"

Enforcement

  • Secrets scanning in CI/CD pipeline.
  • Security review gate in the delivery workflow.
  • Use .gitignore to prevent accidental commits of sensitive files.

Arquivo

  • packs/engineering-base/rules/security-policies.md

Voltar para rules

Artifact-first documentation for looply.