CVE-2023-29320

Establishing and updating awareness policy promotes adherence to secure design principles through ongoing training, preventing related violations.

Mandating the policy be consistent with laws, standards, and guidelines enforces secure design principles in security governance and oversight.

Deficiencies violating secure design principles are tracked and corrected through planned actions, limiting attacker opportunities from design flaws.

Documenting, disseminating, and periodically reviewing maintenance policies and procedures enforces core secure design principles for system maintenance activities.

Documented policy with defined scope, roles, responsibilities, and periodic review directly enforces secure design principles and management commitment.

Baseline selection enforces adherence to established secure-design principles rather than ad-hoc or insufficient control choices.

Requires risk determinations for architecture/design decisions, tailoring rationale, and alignment with enterprise architecture to avoid violations of secure design principles.

Regular SSP updates force review of whether the system's evolving design continues to follow documented secure design principles after changes.

A.5.8 mandates integrating secure design risk assessment, requirements derivation (including from threat modelling), and periodic review into the project life cycle, which stops many violations of secure design principles from reaching production; it leaves a bounded remainder (post-design implementation or coding errors not caught by project-level reviews).

A.8.25 mandates secure design and secure-SDLC practices (requirements, checkpoints, secure coding, testing per 8.28/8.29) that directly implement well-established secure design principles, so the violation cannot be exploited in well-implemented cases; the bounded remainder is outsourced development where assurance (8.30) may not be obtained or non-mandated principles outside the org's chosen methodology.

A.8.27 mandates establishing, documenting, and applying secure design/engineering principles (security by design, least privilege, default deny, fail securely, assume breach, zero trust, distrust external input, hardening, design review against attack patterns) directly to prevent violations of those principles in the resulting system; the bounded remainder is that a flawed implementation of the principles (or their incomplete application to outsourced development) can still allow the violation to arise and be exploitable.

Secure coding practices help realize secure design principles at implementation time.

Security testing can detect violations of secure design principles before release.