Build secure design principles into application architecture. These include least privilege and mediation that checks every user action, in keeping with the rule never to trust user input. For example, error checking should be carried out and documented for every input, covering size, data type and permitted ranges or formats. Good design further requires shrinking the attack surface of the application infrastructure, for instance by closing unprotected ports and services, removing programs and files that are not needed, and renaming or removing default accounts.
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 57 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
You are reading one control. How much of CIS Controls v8 have you already done?
CIS Controls v8 CIS-16.10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 240 were rejected on the ISO 27001:2022 pair alone.