A.8.32 Technological
Change management
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (21)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CM-3fullcovers — ISO A.8.32 establishes the overarching change-management program that directly satisfies the full intent of CM-3 by requiring documented procedures, impact assessment, authorization, testing, implementation, and record-keeping for all system changes.
- CM-4mostlycovers — A.8.32's change-management process (including assessment of security-relevant effects) accounts for the bulk of CM-4's pre-change impact-analysis requirement; residual exists because A.8.32 does not explicitly mandate privacy-impact analysis or the same depth of formal documentation that CM-4 requires.
- SA-10mostlycovers — A.8.32's change-management process and security-preserving requirements account for the bulk of SA-10's developer configuration management and approved-change controls, but a real residual remains on the developer-specific assignment, configuration-item identification, and integrity-documentation details that sit outside a generic organizational change-management control.
- CM-9partialcovers — A.8.32's narrow focus on preserving security during change execution addresses only a slice of CM-9's broader requirements for a full configuration management plan spanning roles, lifecycle identification, item definition, and implementation.
Aligned NIST CSF 2.0 outcomes (16)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- PR.PS-01mostlycovers — The ISO control's formal change-control procedures, impact assessment, authorization, testing, and documentation directly implement the configuration-management practices required by PR.PS-01.
- ID.AM-08domain mandateimplements — A.8.32 operationalizes change management as the mechanism that keeps security properties intact across the full asset life cycle that ID.AM-08 requires; the link is within the shared domain of life-cycle security but is not an explicit citation of change management by the CSF outcome.
- ID.RA-07domain mandateimplements — A.8.32 directly operationalizes the change-management process that ID.RA-07 requires for risk-impact assessment and tracking; the link is within the shared risk-management domain but the CSF outcome does not name the specific change-control mechanism.
Related OWASP ASVS 5.0 requirements (9)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (3262)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CWE-1068mostlyblocks — Change management can catch drift after the fact, but does not guarantee initial implementation matches design.
- CWE-912mostlyblocks — Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
- CWE-1038partialfinds — Change-management processes should evaluate the security impact of enabling or altering automated optimization features.
- CWE-114partialblocks — Change management can gate risky deployments but does not inherently block untrusted process control.
- CWE-1174partialfinds — Change management processes can enforce validation checks during code reviews and releases.
- CWE-1188partialblocks — Requiring documented specification, testing, and acceptance of changes ensures that new or modified components are not initialized with insecure default settings that would otherwise be left in production.
- CWE-1321partialblocks — Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.
- CWE-1394partialblocks — Change-management processes should detect and remediate default cryptographic keys.
- CWE-430partialblocks — Change management verifies that handler mappings remain correct after updates.
- CWE-440partialfinds — Change management can catch specification deviations introduced by modifications.
- CWE-449partialblocks — Change management can catch UI defects before release but does not itself define correct action semantics.
- CWE-459partialfinds — Change-management processes may require cleanup verification, but the control itself does not address the weakness.
- CWE-477partialblocks — Change management can trigger reviews that remove obsolete functions but does not directly address them.
- CWE-489partialblocks — Change management can enforce removal of debug code as part of release gates.
- CWE-508partialblocks — Change-management processes can prevent unauthorized introduction of malicious code.
- CWE-511partialblocks — Change management reviews reduce the chance of unauthorized malicious code insertion.
- CWE-553partialblocks — Change management can catch the addition of such files if reviewed, but is not a direct mitigation.
- CWE-561partialfinds — Change-management processes may catch dead code during reviews but are not designed to address it.
- CWE-672partialblocks — Change-management processes can introduce or remove resource-lifetime controls.
- CWE-684partialblocks — Change management processes reduce the chance of unintended functional deviations during updates, though they do not directly address initial specification conformance.
- CWE-689partialblocks — Ensures changes to access controls are managed, preventing interim exposure during copy.
- CWE-825partialblocks — Change-management processes can require re-validation of memory safety after modifications, indirectly reducing the weakness.
Mitigated MITRE ATT&CK techniques (3552)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- T1543.003mostlyprevents — Mandatory change-control procedures and testing for new or modified Windows services limit an adversary’s ability to install persistent malicious services.
- T1078.001partialprevents — Change management can include acceptance criteria in deployment plans that require default accounts to be disabled or credentials rotated before a new system goes live, preventing the introduction of new default-account attack surface; however, the control does not directly mandate disabling existing default accounts (A.8.9's job) and does not address default accounts already present, so the prevention is a slice of the technique's surface rather than the bulk.
- T1190partialprevents — Change management prevents a slice of T1190 by requiring impact assessment, testing, and authorization before changes are deployed — catching misconfigurations and ensuring security patches are applied in a controlled way — but it does not prevent software bugs, design flaws, or zero-day vulnerabilities from existing in the application, which constitute the bulk of the technique's surface.
- T1195partialprevents — Change management's testing, acceptance, and authorization requirements (b, d, e) can catch some supply chain compromises before deployment, but the control governs changes the organization makes rather than verifying third-party integrity, testing is typically functional rather than security-focused, and sophisticated compromises are designed to evade it.
- T1195.002partialprevents — Change management mandates testing and authorization before implementation, which can block a manipulated update from reaching production, but the control governs the organization's own change process and cannot prevent compromise that occurs upstream at the supplier before the software is received.
- T1204.003partialprevents — Change management requires that image deployments go through formal planning, authorization, and testing, which provides opportunities to catch malicious images through source verification or security scanning, but the control mandates a process rather than specific image-integrity checks, so prevention depends on what the implementation actually tests.
- T1204.005partialprevents — Change management requires planning, authorization, and testing of changes including new dependencies, which can catch malicious libraries through review of third-party packages before they are added to a system; however, it does not inherently mandate security review of dependencies (that is A.8.25/A.8.28), developers frequently install libraries outside formal change processes (especially in development and CI/CD contexts), and a sufficiently convincing malicious package can pass authorization and testing, so what is prevented is a slice rather than the bulk.
- T1210partialprevents — Change management ensures security patches and updates go through planning, testing, authorization, and controlled deployment, which can prevent exploitation of remote services by remediating known vulnerabilities; however, it does not mandate patching, does not address zero-days or unpatched systems, and is a process control that facilitates remediation rather than directly blocking exploitation attempts.
- T1505.003partialdetects — Enforced change-management processes and acceptance testing make unauthorized insertion or modification of web shells far more difficult to achieve undetected.
- T1525partialprevents — Change management's authorization, testing, and documentation requirements for image modifications can prevent unauthorized implants from being deployed, but the control is procedural and does not directly scan image content for malicious code, and an adversary with sufficient credentials could authorize their own changes through the process.
- T1542.004partialprevents — Change management's authorization, testing and documentation requirements would block unauthorized ROMMON firmware loads if properly enforced on network devices, but ROMMONkit is specifically designed to be stealthy, can be loaded remotely via TFTP, and firmware-level changes on network infrastructure often fall outside the rigor of typical change control, leaving a substantial slice where the technique still runs.
- T1546.013partialprevents — Change management can include PowerShell profiles in its scope via baseline configuration, file integrity monitoring, and managed deployment, which constrains unauthorized modifications; however, the core mechanism (change approval) does not inherently prevent an adversary with code execution from modifying profile.ps1 outside the process, and the technique persists unless profiles are specifically hardened under the change program.
- T1546.015partialprevents — Change management requires Registry modifications to go through formal authorization, testing and documentation, which should prevent unauthorized COM hijacking changes, but it is a process control that depends on technical enforcement (Registry auditing, file integrity monitoring) to actually block the modification; adversaries with sufficient privileges can bypass the process and not all Registry changes may fall within its scope.
- T1547.001partialprevents — Change management requires authorization, testing and documentation for changes to system configuration including registry keys and startup folders, which constrains unauthorized additions; however, it is a process control whose enforcement depends on access controls and monitoring, and an adversary with sufficient privileges can bypass the procedure, leaving a bounded remainder where the technique still succeeds.
- T1547.012partialprevents — Change management requires authorization, testing and documentation for system modifications; adding a print processor is a system change that should pass through this process, so an unauthorized addition would be caught. However, it is a process control dependent on review and segregation of duties — an adversary holding SeLoadDriverPrivilege may bypass or self-authorize the change, and emergency-change pathways exist, so the technique is not fully prevented.
- T1548.005partialprevents — Change management's review and authorization of changes (items a, b) can prevent the introduction of misconfigured permission grants, role assignments, and IAM policies that create escalation paths, but it cannot prevent abuse of legitimately configured JIT access, impersonation, or PassRole features by an adversary who has compromised a sufficiently privileged account — the technique runs against existing configurations, not against changes.
- T1552.001partialprevents — Change management review and testing requirements can prevent the introduction of new insecure credential storage through controlled changes (e.g., catching embedded passwords in new config files before deployment), but it does not address existing files, user-created credential stores, or the adversary's ability to search for and read credentials already present on the system.
- T1574partialprevents — Change management requires planning, authorization, testing and managed implementation of changes to system configurations (PATH, library paths, registry entries) that T1574 sub-techniques typically abuse, so a properly governed change would be caught at the testing or authorization stage; however, it is a process control that an attacker with existing access can bypass, and it does not actively block the technique from running on systems or components outside the change-management scope.
- T1677partialprevents — A.8.32 mandates a formal change process with authorization, testing, and impact assessment, which can block unauthorized modifications to CI/CD configuration files, but the control governs process rather than enforcing technical gates, so a change that bypasses the process or is maliciously authorized is not prevented.
- T1684partialprevents — Change management's formal authorization, testing and review requirements act as a gate that catches malicious changes an adversary tries to slip through via social engineering, but T1684 extends well beyond change approval (password resets, MFA changes, financial approvals, sensitive disclosures) where A.8.32 has no mechanism.
Prevented OWASP Web Top 10 (2025) risks (15)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A01partialblocks — A.8.32's formal change-management process (impact assessment, authorization, testing, documentation) catches many classes of access-control defects before they reach production, but leaves real residual (e.g. CSRF, path-traversal naming issues, and logic errors that survive review) exactly as graded for the identical A01 category in the AC-3 anchor.
- A02partialblocks — A.8.32's formal change-management process (impact assessment, authorization, testing, documentation) catches and blocks many insecure configuration states from reaching production, but does not itself harden defaults, enforce secure baselines, or eliminate all misconfiguration vectors (e.g., runtime cloud settings or incomplete hardening outside the managed change window).
- A06partialblocks — A.8.32 mandates formal change-management processes (impact assessment, authorization, testing, documentation) across the SDLC that catch and block many insecure-design defects before they reach production; it does not guarantee that the initial architecture or threat model itself is sound, so the coverage is a genuine but bounded slice of the class.
- A08partialblocks — A.8.32's formal change process (planning, authorization, testing, documentation, emergency fallbacks) directly blocks many integrity failures at the source by catching unsigned updates, unvetted CI/CD pipeline changes, and insecure deserialization paths before they reach production; it does not cover all supply-chain or runtime trust failures outside managed change windows.
- A10partialblocks — A.8.32's formal change-management process (impact assessment, testing, authorization, documentation, and contingency/fallback planning across the SDLC) directly reduces the chance that error-handling paths will be introduced with leaks, fail-open behavior, or inconsistent states, but does not guarantee that every exceptional-condition defect is caught or eliminated.
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.