PW.5.1 Secure Coding Practices
Follow secure coding practices for input validation, output encoding, authentication, session management, error handling, and use of secure defaults. Apply practices consistently across languages used in the organization
4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Secure coding standard per language · Policy repository / GRC workspace
- Linter or analyzer configuration to enforce standard · Policy repository / GRC workspace
- Training tied to standard · HR system / LMS
- Examples of code review feedback citing standard · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- standard exists for one language but not the rest of the stack
- linters disabled because they slow builds
- training not refreshed when standard changes
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetPW.4.4 Verify Acquired Components Meet Security Requirements · PW.6.1 Configure Compilation and Build Processes Securely