# Secure Development ### Purpose Secure development ensures that security is built into delivery rather than added at the end. ### Secure Development Practices Teams should use: * secure coding practices * code review * dependency scanning * secrets management * least privilege access * secure configuration * logging and monitoring * vulnerability management * threat modelling where appropriate * security testing before release ### Security Evidence Projects should retain: * security requirements * threat model * access control record * vulnerability scan results * penetration test results where applicable * remediation records * risk acceptance records --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://framework.aic.io/company-operating-manual/engineering-and-technical-standards/secure-development.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.