PW.6.1 Configure Compilation and Build Processes Securely
Configure compilers, linkers, and interpreters to use security focused options including stack protection, position independent code, and warnings as errors where feasible. Persist these options as part of the build conf
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Build configuration committed to source control · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Compiler flag catalog by language · Policy repository / GRC workspace
- Warnings as errors policy · Policy repository / GRC workspace
- Exception register for legacy components · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- compiler flags vary across services with no central guidance
- warnings ignored to keep builds green
- interpreters run in unsafe modes for performance
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.5.1 Secure Coding Practices · PW.6.2 Configure Build Tool Security Features