CVE-2023-2904

Checksums and integrity protection during transformation/packing detect unauthorized modification of data assumed to be immutable before it is transmitted.

Least-privilege access controls directly block unauthorized writes to assumed-immutable data.

Integrity mechanisms for data-at-rest prevent modification of elements expected to remain immutable.

Protecting data-in-use integrity stops runtime tampering of values treated as constant.

Logical access controls reduce the attack surface for modifying internal assumed-immutable state.

Hardened configuration baselines limit opportunities to alter data presumed immutable.

Secure SDLC practices include design reviews that identify and protect data assumed to be immutable.

A.8.26 requires identifying and specifying requirements (including segregation of access, resilience against malicious attacks like injections, input validation, output controls, and cryptography per 8.24) that can stop exploitation of MAID in many cases, but leaves a bounded remainder where requirements are identified yet insufficiently enforced at runtime or for non-application contexts.

A.8.27 mandates security-by-design principles (least privilege, fail securely, distrust external input, defence-in-depth, zero-trust verification) plus design reviews that can catch and stop MAID-style mutation of assumed-immutable objects before they ship, but the clause is a process that depends on how rigorously those principles are applied and does not itself guarantee the protection mechanism is present at every relevant boundary.

Secure coding standards discourage mutable storage for values that must remain constant.

Security testing can detect unauthorized modification paths for assumed-immutable data.