Files
ECC/.kiro/steering/security.md
T
Eric BellavanceandClaude Opus 5.5 1e895858d0 docs(kiro): use always inclusion for always-on steering files
Kiro only loads steering files automatically in every conversation when
they use `inclusion: always`; `auto` loads them only when the request
matches the description. Switch the always-on steering files to
`always` and update README, install.sh and docs accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 13:23:13 -04:00

1020 B

inclusion, name, description
inclusion name description
always security Security best practices including mandatory checks, secret management, and security response protocol.

Security Guidelines

Mandatory Security Checks

Before ANY commit:

  • No hardcoded secrets (API keys, passwords, tokens)
  • All user inputs validated
  • SQL injection prevention (parameterized queries)
  • XSS prevention (sanitized HTML)
  • CSRF protection enabled
  • Authentication/authorization verified
  • Rate limiting on all endpoints
  • Error messages don't leak sensitive data

Secret Management

  • NEVER hardcode secrets in source code
  • ALWAYS use environment variables or a secret manager
  • Validate that required secrets are present at startup
  • Rotate any secrets that may have been exposed

Security Response Protocol

If security issue found:

  1. STOP immediately
  2. Use security-reviewer agent
  3. Fix CRITICAL issues before continuing
  4. Rotate any exposed secrets
  5. Review entire codebase for similar issues