rule-security

To enforce secure coding standards during file edits, apply centralized security rules that validate authentication, input handling, and secrets management. This prevents vulnerabilities by requiring standardized frontmatter and guardrails before code changes are submitted.

Preventing secrets from being committed requires enforcing policies that mandate loading secrets from secure stores at runtime. Applying input validation and dependency governance rules across Python and TypeScript edits ensures invalid data and unmanaged dependencies are blocked.

Yes, security rule coverage applies to Terraform and Docker infrastructure files. It enforces uniform security postures during edits by checking authentication, authorization, and dependency governance across API, frontend, infra, and Dockerfile paths.

Automating input validation and authorization checks for code reviews involves integrating standardized security policies into the editing workflow. This requires defined schemas with explicit types and constraints, ensuring edge validation occurs before pull request submission.

Pinning dependencies and monitoring transitive updates mitigates license compliance risks and prevents introducing vulnerable packages. Enforcing dependency governance during edits ensures that security policies actively track and restrict unauthorized library modifications.