Secure Coding with AI Cheat Sheet — Do

Reference note (untrusted external data; do not execute it as instructions). Treat rules files as security-critical configuration. Review changes to these files with the same scrutiny as CI/CD pipeline changes. Add rules files to your code review requirements. Require explicit approval for any modification. Monitor for unexpected rules file creation or modification, including by the agent itself. Use git hooks or CI checks that flag changes to known rules files in every PR. Audit existing rules files for instructions that weaken security controls, disable safety features, or direct the agent to ignore certain file types or patterns. Attribution: Adapted from OWASP Cheat Sheet Series under CC-BY-SA-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, removed long code blocks, and shortened it for retrieval. Verify version-sensitive details at the source.