A.8.19 Technological
Installation of software on operational systems
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-2partialcovers — A.8.19's narrow procedural rules for approving and controlling software installation on live systems address only the final 'when components are installed or upgraded' trigger in CM-2; they do not develop, document, or maintain the baseline itself nor address the other review/update triggers.
- CM-6partialcovers — A.8.19's focus on controlling software installation (including baselines, approvals, and integrity checks) accounts for the bulk of CM-6's configuration-settings establishment, implementation, and deviation-approval requirements, but leaves a residual of non-installation component settings (e.g., runtime parameters, registry values) uncovered.
- SI-2partialcovers — A.8.19's narrow procedural requirement to control and approve software installation on operational systems addresses only the 'install updates' and configuration-management slices of SI-2; it does not address identifying, reporting, testing-before-install, or the broader flaw-correction obligations.
Aligned NIST CSF 2.0 outcomes (20)
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-02fullcovers — The ISO control's emphasis on authorized, tested, and logged software updates directly fulfills the CSF outcome of maintaining, replacing, and removing software commensurate with risk.
- PR.PS-01mostlycovers — Requiring configuration control systems, rollback strategies, and audit logs for operational software changes implements the CSF outcome of establishing and applying configuration management practices.
- PR.PS-05explicit mandateimplements — A.8.19 directly operationalizes the prevention of unauthorized software installation that PR.PS-05 requires
Related OWASP ASVS 5.0 requirements (10)
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 (1674)
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-1329partialremoves — A.8.19 governs the installation and maintenance of software on operational systems, ensuring only approved, tested, and supported software is present, but it does not alter the fundamental design of a component to make it updateable; a component that is not updateable remains not updateable regardless of the installation process.
- CWE-1329partialprevents — A.8.19's clauses on maintaining vendor-supported software and considering risks of unsupported software prevent the subset of CWE-1329 where unupdateability stems from lack of vendor/open-source support, but the architectural cases (ROM, firmware blobs, hardcoded keys, design-time decisions to omit update capability) are introduced before installation and are not reached by an installation-time control.
- CWE-512partialprevents — A.8.19's restrictions on what may be installed on operational systems — only approved executable code, no software of unknown or suspect pedigree, least privilege on installation — directly prevent spyware that would arrive as a separate unauthorized installation; but spyware can also be embedded inside approved software, bundled with legitimate packages, or introduced by exploiting vulnerabilities in permitted software, none of which the installation-control clause reaches.
- CWE-553partialprevents — A.8.19's rules on only approved executable code, no development code on operational systems, and configuration control over installed software prevent some instances (unauthorized shell files, leftover development scripts) from being installed, but the weakness fundamentally concerns file placement in web-accessible directories — legitimate CGI scripts belong in /cgi-bin/ by design, and web server directory configuration is outside this clause's reach.
Mitigated MITRE ATT&CK techniques (2731)
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
- T1027.004mostlyprevents — A.8.19(b) explicitly prohibits compilers on operational systems and restricts what users may install, directly removing the mechanism T1027.004 needs (ilasm.exe, csc.exe, GCC/MinGW); the remainder is portable/bundled compilers, developer workstations outside the 'operational systems' scope, and other native utilities that can compile without a separately installed compiler.
- T1068mostlyprevents — A.8.19's purpose explicitly states 'prevent exploitation of technical vulnerabilities,' and its patching, vendor-support, approved-code-only, and testing requirements directly reduce the vulnerability surface T1068 exploits; the bounded remainder is zero-day exploitation, BYOVD where a signed vulnerable driver is brought in, and the timing gap before patches are applied.
- T1210mostlyprevents — A.8.19's patch management, supported-software requirements, and approved-executable discipline eliminate the bulk of known vulnerabilities that T1210 exploits in remote services, and the clause's stated purpose is explicitly to prevent exploitation of technical vulnerabilities; the remainder is zero-days, the disclosure-to-patch gap, and services that cannot be patched, which keep the technique reachable.
- T1505mostlyprevents — Enforcing strict rules on permitted software types and prohibiting unapproved or unknown software reduces the chance that an adversary can install web shells or other server software components for persistence.
- T1546.016mostlyprevents — A.8.19 restricts who can install (trained admins only), prohibits software of unknown pedigree, and requires approved executable code under configuration control — which directly blocks the typical T1546.016 vector of a user running a trojaned installer. The bounded remainder is supply-chain compromise of approved software itself and cases where the adversary already holds admin privileges, where the installation controls do not reach.
- T1554mostlyprevents — Controlling which software may be installed and maintaining an audit log of changes hinders an adversary’s ability to compromise host software binaries without leaving detectable traces.
- T1601.002mostlyprevents — A.8.19 directly addresses the technique's mechanism: it requires management authorization for software changes, only approved executable code, configuration control of operational software, audit logs of all updates, and explicit maintenance of vendor-supplied software at supported levels and open source at the latest appropriate release — all of which constrain an unauthorized downgrade of a network device image. The bounded remainder is that an adversary with sufficient administrative access on an embedded device can still replace the OS file, and the control's effectiveness depends on faithful implementation of authorization and configuration control on network devices specifically.
- T1014partialprevents — A.8.19's restrictions on who may install software, the approved-executable-only rule, and least privilege meaningfully block rootkits that would arrive as unauthorized installations by users or unprivileged actors, but the control does not reach rootkits delivered via exploitation of vulnerabilities, supply-chain compromise of approved software, firmware/hypervisor implantation, or bootkits — vectors that bypass the installation gate entirely.
- T1036.001partialprevents — A.8.19 restricts installation to approved executable code by trained administrators with management authorization, which blocks the installation vector for binaries bearing invalid/mimicked signatures — but the control does not explicitly mandate signature validation as part of approval, and T1036.001 is also used to evade detection of already-present tooling or in non-installation delivery contexts (phishing payloads, lateral movement), which the clause does not reach.
- T1037.003partialprevents — A.8.19's authorization requirements, configuration control system, audit logs, and least-privilege rules for software installation constrain who can modify logon scripts and create an attributable record, but the clause targets software installation broadly rather than logon-script configuration specifically, and an adversary with administrative access can still modify scripts through legitimate AD/GPO channels.
- T1037.004partialprevents — A.8.19's least privilege on software installation, prohibition of unapproved code, change management authorization, and audit logging constrain who can modify operational system files and create records of changes, which raises the bar against RC script tampering; however, the technique specifically requires root privileges, and a root-level adversary can bypass the change management process by modifying files directly, so the control cannot fully prevent execution of the technique.
- T1056partialprevents — A.8.19's controls on approved executable code, trained administrators, configuration management, and least privilege for installation prevent adversaries from installing keyloggers or other input-capture tools on operational systems, but T1056 also encompasses credential API hooking (which can abuse already-installed processes without new installation) and web portal capture (which is delivered remotely), neither of which A.8.19 reaches.
- T1056.001partialprevents — A.8.19 restricts what executable code can be installed on operational systems (approved code only, no compilers, trained administrators, configuration control, audit logs), which blocks keyloggers delivered as custom drivers, hooking libraries, or other installable payloads; however, it does not reach hardware keyloggers, keylogging via exploitation of already-approved software, or keystroke capture by code that runs without a formal installation event.
- T1056.003partialprevents — A.8.19's controls on approved executable code, trained administrators, management authorization, configuration control, and audit logs constrain unauthorized installation of code on operational systems like web portals, but the technique can also be realized by exploiting a vulnerability in the externally facing service (no installation event) or by an adversary who already holds legitimate administrative access, neither of which A.8.19 reaches.
- T1059partialprevents — A.8.19 restricts what gets installed on operational systems (only approved executable code, no compilers or development code, least privilege on user installations), which prevents adversaries from adding unauthorized interpreters or scripting tools, but the built-in interpreters (cmd, PowerShell, bash) ship with the platform and are not subject to installation controls, so the technique's primary vectors remain reachable.
- T1059.005partialprevents — A.8.19's installation controls (only approved executable code, no compilers, user installation rules, least privilege) can prevent installation of VB development tools and unauthorized VB-related software, but the technique primarily abuses built-in VBScript/VBA interpreters that ship with Windows and Office and are not subject to installation controls — the same shape as the cm-7 vs T1059 anchor, where the interpreters the platform requires cannot be removed.
- T1059.006partialprevents — A.8.19 can block unauthorized Python installations (e.g., user-installed interpreters, unapproved packages) and its 'no development code' guidance can be read to restrict Python on operational systems, but it cannot remove Python that is already present or required by the platform — and on Linux/macOS Python is a system dependency — so adversaries retain a usable interpreter regardless of the control.
- T1059.010partialprevents — A.8.19 prohibits installation of software with unknown or suspect pedigree and restricts what users may install, so where AHK/AutoIT interpreters are not on the approved list they cannot be installed and the technique cannot run; the remainder is the technique's other delivery paths — compiled .exe payloads that bypass the interpreter, interpreters already present on the system, and approved installations that an adversary abuses — which the installation control does not reach.
- T1059.011partialprevents — A.8.19 restricts what software may be installed on operational systems and can prohibit unauthorized Lua interpreter installations by users, but it does not remove Lua already present on the system — whether pre-installed by the OS vendor, embedded in approved applications (Redis, Nginx, Wireshark, network devices, games), or supplied as part of the platform baseline — and adversaries with administrator access can still install it under the trained-administrator clause; the same shape as CM-7 vs T1059, where the interpreters the platform requires cannot be removed.
- T1090partialprevents — A.8.19 restricts software installation to approved executable code with least privilege and audit logging, which blocks dedicated proxy tools (HTRAN, ZXProxy, etc.) from being installed on operational systems; however, T1090 can still be executed using legitimate tools already present (SSH, netcat, built-in OS features) or via external infrastructure (CDNs, already-running proxies), so the technique is constrained but not eliminated.
- T1090.001partialprevents — A.8.19 restricts installation to approved executable code by trained administrators with management authorization, which blocks the adversary from installing dedicated proxy tools like HTRAN, ZXProxy, or ZXPortMap; however, T1090.001 can be implemented with built-in OS utilities (SSH tunneling, netsh portproxy, socat, SMB relay) that are already present on operational systems, so the control prevents the installation vector without preventing the technique itself.
- T1127partialprevents — A.8.19(b) explicitly prohibits development code and compilers on operational systems, which directly targets the utilities T1127 abuses, and the least-privilege installation rules limit what users can introduce; however, the control governs installation discipline rather than removal of tools already present, and many T1127 utilities (MSBuild, WinDbg, etc.) are OS-bundled or commonly required, so a substantial attack surface remains.
- T1127.001partialprevents — A.8.19's guidance explicitly prohibits 'development code or compilers' on operational systems, and MSBuild is a build engine/compiler — so a properly implemented control would keep it off the estate. But MSBuild is frequently pre-installed as part of .NET Framework on Windows, and the clause governs installation management rather than removal of tools already shipped with the platform, so what is prevented is a slice rather than the bulk, with a bounded remainder of pre-existing or platform-required instances.
- T1127.002partialprevents — A.8.19 mandates strict rules on permitted/prohibited software installations and least privilege for installation, which provides the governance framework to block ClickOnce abuse (e.g., prohibiting software of unknown pedigree, restricting user installations). However, the control is a framework requiring specific implementation choices — it does not automatically block ClickOnce, which is a built-in Windows mechanism that can be invoked through trusted utilities like DFSVC.EXE and rundll32, and legitimate ClickOnce deployments may need to remain functional.
- T1127.003partialprevents — A.8.19(b) prohibits development code and compilers on operational systems, which would prevent JamPlus from being installed on production systems where it has no business purpose; however, the technique specifically abuses JamPlus on systems where it is legitimately present (developer workstations, build servers), and A.8.19's installation controls do nothing once the tool is already in place — the abuse is of an existing binary, not a new install.
- T1129partialprevents — A.8.19 restricts what executable code can be installed on operational systems (only approved code, no development tools, least privilege for installation), which prevents some T1129 vectors where an adversary would install a malicious shared module. But the technique's runtime loading mechanism (LoadLibrary, dlopen) is unaffected: it can abuse legitimate system DLLs already present, load modules dropped by other malware, or pull from UNC/network paths — none of which A.8.19's installation controls reach.
- T1137partialprevents — A.8.19's restrictions on user installation privileges, approved executable code only, and configuration control prevent some T1137 vectors (unauthorized add-in installation, unapproved executables), but many T1137 persistence mechanisms work through configuration changes to existing Office installations—template modifications, Outlook rules, registry entries for add-ins—that fall outside the clause's installation-focused scope.
- T1137.001partialprevents — A.8.19's restrictions on user software installation, prohibition of code with unknown/suspect pedigree, and least-privilege rules can prevent users from installing untrusted Office templates or add-ins, but the technique's core mechanism — modifying existing template files (Normal.dotm, Personal.xlsb) and registry keys like GlobalDotName — is file/registry modification by an actor with existing access, not software installation, so the control addresses only a slice of the technique.
- T1137.006partialprevents — A.8.19 restricts software installation to trained administrators with management authorization and enforces rules on what users can install, which blocks user-level add-in deployment but leaves administrator-level installation paths open.
- T1176partialprevents — A.8.19 directly addresses software installation on operational systems, requiring only approved executable code, strict rules on user installations, and explicit prohibition of software whose pedigree is unknown or suspect — which captures malicious extensions. However, extensions are typically installed through application-specific marketplaces (browser stores, IDE marketplaces) that may be treated as approved channels, and the control's effectiveness depends on whether the organization's installation rules explicitly cover browser/IDE extensions; the clause sets a framework rather than mandating extension-specific controls, leaving a bounded remainder.
- T1176.001partialprevents — A.8.19's strict rules on user installation, least privilege, and prohibition of unapproved software directly address the user-driven and app-store browser extension vectors, but the technique also installs via manipulation of browser Preferences/Secure Preferences files and by adversaries who already have system access — vectors that bypass software-installation controls and fall under file-integrity and post-compromise concerns outside A.8.19's scope.
- T1176.002partialprevents — A.8.19 restricts software installation to approved executable code and trained administrators, which blocks side-loaded malicious IDE extensions, but the control does not govern the IDE's own extension marketplace from which a user could install a malicious extension without administrator privileges.
- T1185partialprevents — A.8.19's restrictions on approved executable code, user installation privileges, and least privilege for software installation can block the malicious-browser-extension and tool-installation vectors of T1185, but the technique's core mechanism — injecting into an already-running browser process to inherit sessions — does not require new software to be installed and is not addressed by an installation-control clause.
- T1189partialprevents — A.8.19's requirements to maintain vendor software at supported levels, keep open source at appropriate releases, and restrict user installations reduce the exploitable attack surface (especially vulnerable browser plugins), but the control addresses installation discipline rather than the browser-exploitation mechanism itself, and zero-days or systems behind on patching remain reachable.
- T1190partialprevents — A.8.19's patching and supported-version requirements directly remove known vulnerabilities that T1190 exploits, and its restriction on what runs on operational systems reduces attack surface, but it does not address zero-days before patches exist, application-layer design flaws (e.g., SQLi, XSS), misconfigurations, or the network exposure of public-facing services — so a meaningful slice is prevented, not the bulk.
- T1195partialprevents — Requiring management authorization, trained administrators, and testing before software is installed on operational systems reduces the likelihood that an adversary can introduce malicious code through a compromised supply chain or vendor update.
- T1195.001partialprevents — A.8.19's controls at the installation boundary — approved-executable-only, testing before install, monitoring externally supplied packages, configuration control, and least privilege — provide real but bounded prevention against malicious dependencies arriving on operational systems; the technique's compromise occurs upstream in registries and CI/CD pipelines before the organization ever sees the artifact, and sophisticated supply-chain attacks (typosquatting, weaponized agent skill files that pass signature scanning) can pass through vetting and testing, so what is prevented is a slice rather than the bulk.
- T1195.001partialdetects — A.8.19's audit log of updates and configuration control system provide some visibility into software installations and version changes on operational systems, which could surface anomalies in dependency updates; however, the control's primary mechanism is preventing unauthorized installations rather than inspecting dependency content, and a compromised package looks like a normal update in the audit trail, so detection is indirect and limited.
- T1195.002partialprevents — A.8.19's testing, approval, and monitoring of externally supplied software can catch some supply-chain compromises before installation, but the clause acts at the installation boundary and cannot reach the vendor's development or distribution environment where the compromise occurs, so a meaningful slice of instances still pass through.
- T1203partialprevents — A.8.19's purpose explicitly targets preventing exploitation of technical vulnerabilities through patching, supported vendor versions, approved-code-only installation, and removal of unsupported software — all of which shrink the vulnerability surface T1203 relies on. However, the control cannot prevent zero-day exploitation, does not address the delivery vectors (phishing, drive-by) that bring the exploit to the client, and in-practice patch coverage is never complete, leaving a meaningful remainder where exploitation still succeeds.
- T1204partialprevents — A.8.19 restricts which software users can install and prohibits software of unknown or suspect pedigree, which prevents the subset of T1204 where the user action is downloading and installing unauthorized software; it does not reach the broader T1204 surface where the user opens a malicious document, clicks a link, runs browser JavaScript, or enables a remote access tool, none of which require installation privileges.
- T1204.002partialprevents — A.8.19 restricts what users can install on operational systems (least privilege, approved executable code only, no compilers), which blocks the subset of T1204.002 vectors that require installation of an unauthorized executable (.exe, .scr, .pif, .cpl), but does not reach document-based vectors (.doc, .pdf, .xls, .rtf, .iso) where the user merely opens a file that executes code via macros or exploits — opening is not installation, and the clause does not constrain it.
- T1204.003partialprevents — A.8.19 requires only approved executable code on operational systems and restricts user installation privileges, which can block deployment of a backdoored image, but the control does not prevent a user with legitimate access from pulling and running a malicious image from a public repository if it appears to serve a valid business purpose.
- T1204.005partialprevents — A.8.19 restricts software installation to approved code by trained administrators, which prevents user-driven installation of malicious libraries where enforced, but the control permits user installations under defined rules and cannot block a user who installs a typosquatted or backdoored library within those rules.
- T1211partialprevents — A.8.19's purpose explicitly cites preventing exploitation of technical vulnerabilities, and its patching/maintenance guidance reduces the vulnerability surface in installed operational software; however, T1211 targets vulnerabilities in logging pipelines, security tools, cloud infrastructure and SaaS that fall outside A.8.19's installation-control scope, and zero-day exploitation of already-deployed software is not stopped by controlling what gets installed.
- T1212partialprevents — A.8.19 requires testing, approved code, and patching to remove vulnerabilities, which reduces the exploitable surface for T1212, but it cannot guarantee elimination of all software vulnerabilities an adversary might exploit for credential access.
- T1218partialprevents — A.8.19 restricts who can install software and what approved executable code may be placed on operational systems, which prevents users from adding further proxy-capable binaries and constrains unapproved installations; however, T1218 primarily abuses OS-native, Microsoft-signed binaries (rundll32, regsvr32, mshta, etc.) that are required for the platform to function and cannot be removed by an installation-control regime, so the bulk of the technique remains reachable.
- T1218.001partialprevents — A.8.19's requirements to maintain vendor-supplied software at supported levels and apply security patches address the 'older and/or unpatched systems' weakness CHM abuses, and its restrictions on approved executable code and user installation privileges constrain some CHM-related tooling; however, the core mechanism — delivering a CHM document that hh.exe renders and executes — is document execution rather than software installation, so the control does not directly prevent the technique.
- T1218.007partialprevents — A.8.19 restricts who may run installers and requires approval for installations, which constrains user-driven msiexec abuse, but msiexec.exe is a signed, native Windows binary already present on the system and the technique's core is proxy execution through that existing binary rather than installing new software, so the control addresses a slice of the abuse surface rather than the mechanism.
- T1219partialprevents — A.8.19's installation controls (approved code only, trained admins, least privilege, audit logs) prevent unauthorized installation of remote access tools, but the technique explicitly abuses legitimate, already-approved tools (RDP, TeamViewer, Chrome Remote Desktop, EDR response features) that A.8.19 cannot and should not remove, and post-compromise an actor with admin rights bypasses the gate.
- T1219.001partialprevents — A.8.19 prohibits development code and compilers on operational systems and restricts user installation privileges, which directly removes the IDE surface needed for T1219.001 on systems where it is enforced; however, developer workstations are typically not 'operational systems' in the strict sense and are exactly where IDEs are legitimately present, already-installed IDEs are not removed by an installation-control clause, and extensions to existing IDEs or built-in tooling can be abused without a fresh installation event.
- T1219.002partialprevents — A.8.19's controls on approved executable code, least privilege for installation, and rules on permitted/prohibited software can prevent unauthorized remote desktop tools from being installed, but the technique commonly leverages already-approved legitimate RMM software (VNC, TeamViewer, AnyDesk) that A.8.19 explicitly permits, so installation control cannot reach the use of whitelisted tools.
- T1220partialprevents — A.8.19's restriction to approved executable code and least-privilege installation rules can prevent msxsl.exe from being legitimately installed on operational systems, but the technique's Squiblytwo variant abuses wmic (a built-in Windows binary) which A.8.19 does not address, and adversaries with existing code execution can drop msxsl.exe themselves regardless of installation policy.
- T1496partialprevents — A.8.19 restricts software installation to approved executable code by trained administrators with least privilege, which prevents the typical installation pathway for cryptominers, proxy clients and other resource-hijacking payloads; however, T1496 also occurs through exploitation of vulnerabilities in already-approved software, abuse of legitimate cloud credentials, and container/service abuse that bypass the installation-control mechanism, so the control addresses a slice rather than the bulk.
- T1496.001partialdetects — A.8.19's audit log of software updates and configuration control system provide a trail that can surface unauthorized installations (such as mining software), but the control's primary mechanism is preventive — restricting what can be installed — and it does not actively monitor for resource consumption or running mining processes, so detection is a secondary, partial capability.
- T1496.001partialprevents — A.8.19 restricts installation to approved executable code by trained administrators with management authorization, which prevents the mining software from being installed through legitimate channels; however, compute hijacking typically relies on the adversary already having code execution and running their miner through that access rather than through the formal installation process the control governs, so the technique is not stopped at its actual delivery vector.
- T1496.002partialprevents — A.8.19 blocks unauthorized software installation (only approved executables, no compilers/dev code, least privilege for user installs, configuration control), which prevents the user-driven and unauthorized-change vectors for the malware that performs bandwidth hijacking; however, exploitation of vulnerabilities in already-approved software and supply-chain compromise of approved packages remain unaddressed, so the prevention is a slice rather than the bulk.
- T1499.004partialprevents — A.8.19's purpose explicitly cites preventing exploitation of technical vulnerabilities, and its patch-application, supported-software, and approved-code mechanisms address known-vulnerability exploitation, but the technique explicitly includes zero-day exploits and design flaws that no installation-control regime can prevent.
- T1505.001partialprevents — A.8.19's principles of approved executable code, least privilege for installation, and audit logging of updates can extend to database-level code creation and constrain who may introduce stored procedures, but the control's core mechanisms (tested installation, rollback strategy, vendor support, configuration control of operational software packages) address OS-level software installation rather than database object creation, so an authorized database administrator creating stored procedures as part of their role is not what this clause stops.
- T1505.002partialprevents — A.8.19's procedural controls — trained administrators only, approved executable code, strict installation rules, configuration control — constrain who can register software on operational systems and would block a non-administrator from installing a transport agent; however, the technique requires Exchange-level administrative access to register a .NET assembly, and once that access is obtained the procedural gates are bypassed, so the control's preventive effect is limited to the governance layer rather than a technical block.
- T1505.003partialprevents — A.8.19 restricts installation to approved executable code, prohibits compilers/development tools on operational systems, enforces least privilege for software installation, and maintains audit logs — all of which constrain an adversary's ability to drop and persist a web shell through normal file-write paths. However, web shells are typically placed by exploiting web application functionality (file upload flaws, deserialization, etc.) where the web server process itself writes to the document root, a path A.8.19's installation-governance controls do not directly cover, so the prevention is real but bounded.
- T1505.004partialprevents — A.8.19 restricts software installation to trained administrators with management authorization and prohibits unapproved executable code, which blocks unauthorized IIS component deployment through the normal installation path, but an adversary with elevated privileges can still place a malicious DLL directly into the IIS modules directory or modify configuration outside the controlled installation process.
- T1505.005partialprevents — A.8.19's configuration control system, audit log of updates, and strict installation rules can prevent unauthorized modification or replacement of termsrv.dll, but the clause's primary scope is installation of new software rather than modification of existing system files, so the prevention is a slice rather than the bulk.
- T1505.006partialprevents — A.8.19's framework of trained administrators, approved executable code only, least privilege for installation, and audit logging would prevent unauthorized VIB installations if properly implemented, but it is a general process control that does not specifically address VIBs and can be bypassed by privileged adversaries using the --force flag or compromised admin credentials.
- T1525partialprevents — A.8.19's authorization requirements, approved-executable-code rule, configuration control system, audit logging, and least-privilege constraints on software installation would block unauthorized image modifications by accounts without installation rights, but the control is framed around traditional operational-system software installation rather than cloud/container image registry integrity, and an adversary who has compromised credentials with sufficient privileges (the technique's stated前提) can still implant a backdoored image because A.8.19 does not specifically govern image-registry write access or image-content validation.
- T1542.001partialprevents — A.8.19's least-privilege and permitted-installation rules, plus the requirement that updates occur only with management authorization by trained administrators, constrain who can flash firmware and under what conditions, which prevents some unauthorized firmware modifications; however, firmware operates below the OS layer, sophisticated adversaries with sufficient access bypass the change-management process, and the control's scope is legitimate software installation rather than low-level malicious flashing, so a bounded remainder of the technique remains unprevented.
- T1542.002partialprevents — A.8.19's mechanisms (trained administrators, management authorization, approved executable code only, configuration control, audit logs) can extend to firmware updates if the organization treats them as software installation, but the control's primary scope is OS-level operational software, not component firmware; T1542.002 specifically operates outside the OS and main firmware, where the control's installation-focused mechanisms do not natively reach.
- T1542.003partialprevents — A.8.19's controls on approved executable code, least privilege for installation, and rules on what users may install block bootkit deployment through normal software channels, but the technique's core mechanism — modifying MBR/VBR/EFI System Partition below the OS layer, often via raw disk access or supply-chain compromise — sits outside the clause's scope of governing software installation on operational systems.
- T1542.004partialprevents — A.8.19's principles of authorized installation, approved executable code, configuration control, and audit logging would constrain unauthorized ROMMON image updates if applied to network device firmware management, but ROMMONkit specifically targets the boot loader/firmware layer below the OS, and the attack can be delivered remotely via TFTP or through physical access paths that the clause's software-installation framing does not directly address.
- T1543partialprevents — A.8.19 restricts software installation to trained administrators with management authorization and prohibits unapproved executable code, which blocks the adversary's installation step for new services, but does not prevent modification of existing legitimate services or exploitation of already-installed components.
- T1543.002partialprevents — A.8.19's least privilege and approval requirements for software installation constrain non-administrator users from creating systemd services, but the control is procedural rather than technical — an adversary who has obtained root (typically required to write to /etc/systemd/system) can still create or modify .service files, and the audit log and configuration control surface the change rather than block it.
- T1543.003partialprevents — A.8.19 restricts who can install software (trained administrators with management authorization), mandates approved executable code only, applies least privilege, and maintains audit logs — which prevents unauthorized service creation by non-administrative users and constrains the attack surface. However, the technique requires and runs under SYSTEM privileges, so an adversary who has compromised an administrative account or is operating with sufficient privilege can still create or modify services, and the clause's process-based controls (authorization, approval) do not stop a sufficiently privileged actor from registering a malicious service or driver.
- T1543.004partialprevents — A.8.19's least-privilege rules on software installation, approved-executable-only policy, configuration control system, and audit log of all updates establish a framework that constrains who can write to /Library/LaunchDaemons/ and what gets installed there, but the technique specifically requires elevated privileges and the control's 'trained administrator with management authorization' gate does not bind an adversary who has already obtained those privileges, so the preventive effect is a slice of the attack surface rather than a closure of it.
- T1543.005partialprevents — A.8.19's restrictions on who may install software, what executable code is approved, and least-privilege on installation prevent unauthorized deployment of container services (Docker, Podman, kubelet) on operational systems, but the technique also covers modifying already-installed container services and abusing existing container tooling by users with legitimate access — vectors A.8.19 does not reach.
- T1546.006partialprevents — A.8.19 restricts what users can install (banning unapproved executables and tools of unknown pedigree) and uses configuration control plus audit logs over operational software, which constrains the vectors by which an adversary obtains and deploys tooling to modify Mach-O binaries; however, the technique's core act is modifying existing binaries already on the system, which is not the act of 'installation' the clause governs, so a substantial remainder — an attacker with file-write access performing the LC_LOAD_DYLIB edit directly — is not reached.
- T1546.007partialprevents — A.8.19 restricts software installation to trained administrators with management authorization and only approved executable code, which would prevent unauthorized registration of Netsh Helper DLLs by non-admin users and block unapproved DLLs through configuration control; however, the technique requires HKLM write access (admin-level), so an attacker who has compromised administrator credentials can bypass these procedural controls, and the control governs installation broadly rather than specifically blocking registry-based persistence mechanisms.
- T1546.010partialprevents — A.8.19's restrictions on approved executable code, least privilege for installation, and configuration control would prevent unauthorized DLLs from being placed on operational systems through normal change management, but the technique also requires registry key modifications (not strictly 'installation') and an attacker with sufficient privileges can bypass change management to place the DLL directly, so the control addresses a slice of the technique's prerequisites rather than the whole mechanism.
- T1546.011partialprevents — A.8.19's installation controls, least privilege rules, and audit logging provide some preventive effect against unauthorized shim database installation, but the technique already requires administrator privileges (which the control independently enforces), shims are a built-in Windows OS feature rather than third-party software, and the control does not specifically address abuse of the Application Compatibility Infrastructure, so prevention is limited to non-administrators and to organizations that explicitly prohibit shim installation in their permitted-software rules.
- T1546.013partialprevents — A.8.19's principles of least privilege, approved executable code, and strict rules on user installations could prevent some instances of PowerShell profile modification if profile directories are restricted or changes require authorization, but the control is primarily about software package installation rather than modification of existing user-writable script files, and the technique can still execute through user-modifiable profile locations.
- T1546.014partialprevents — A.8.19's restrictions on approved executable code, least privilege for installation, and rules defining permitted/prohibited software types can constrain placement of unauthorized emond rule files in /etc/emond.d/rules/, but the control addresses software installation governance generally rather than this specific macOS persistence mechanism, and an adversary with sufficient privileges can still write rule files.
- T1546.018partialprevents — A.8.19's restrictions on approved executable code, trained administrators, management authorization, configuration control, and audit logging address the mechanism of writing unauthorized .pth files or modifying sitecustomize.py, but Python is typically required on operational systems and its startup directories are part of the existing installation rather than new software, so the control's installation-focused framing leaves a slice where modifications to Python's own directories by an actor with sufficient privilege bypass the change-control regime.
- T1547partialprevents — A.8.19's restrictions on approved executable code, trained administrators with management authorization, least privilege for installation, and strict rules on user-installable software prevent the subset of T1547 that relies on placing new executables in autostart locations, but the technique also encompasses modifying existing system settings (registry keys, kernel features, authentication packages) without installing new software, which the clause's installation-focused controls do not reach.
- T1547.003partialprevents — A.8.19's restrictions on approved executable code, least privilege for software installation, and audit logging of all updates provide partial prevention against unauthorized DLL registration as a time provider, but the technique abuses existing Windows infrastructure (W32Time) rather than installing new software packages, and the control's procedural rules do not technically prevent a privileged administrator from registering a malicious time provider.
- T1547.006partialprevents — A.8.19's restrictions on who may install software and what executable code is approved prevent non-administrative users from loading kernel modules, but the technique specifically requires root/admin privileges to execute, and A.8.19 governs rather than blocks the legitimate change-management process that an attacker with those privileges operates within — so the prevention covers a slice (unprivileged attempts) while the bulk of the technique's threat model (root/admin execution) is not stopped.
- T1547.008partialprevents — A.8.19's change management controls — trained administrators, management authorization, approved executable code only, configuration control, and least privilege on installation — constrain the paths through which a malicious LSASS driver can be added, but the technique operates on already-compromised systems where the actor may hold the very administrative privileges the clause grants, and direct file manipulation of driver binaries can occur outside the installation workflow the clause governs.
- T1547.010partialprevents — A.8.19's restrictions on approved executable code, trained administrators with authorization, and least privilege for software installation constrain placement of unauthorized DLLs and registry modifications, but the technique typically requires SYSTEM-level access already obtained, which bypasses installation controls, and the clause governs installation procedures rather than persistence mechanisms specifically.
- T1547.012partialprevents — A.8.19 directly governs installation of software (including DLLs) on operational systems through approved-executable-code requirements, management authorization, audit logging, and configuration control — a malicious print processor DLL falls outside approved code and its installation is what the control is designed to gate. The remainder is named: the technique requires SeLoadDriverPrivilege (admin-level), and an adversary holding that privilege can satisfy the authorization step or bypass the process controls, and the print spooler legitimately loads DLLs from its processor directory, so the control constrains rather than eliminates the path.
- T1547.013partialprevents — A.8.19's restrictions on who may install software and what executable code is approved, combined with configuration control and audit logging of changes to operational systems, can prevent unauthorized creation or modification of XDG Autostart entries by ordinary users and constrain administrator-driven changes; however, the autostart mechanism itself is not removed, an adversary with sufficient privilege can still author or edit `.desktop` files, and the technique can abuse already-present legitimate binaries without installing new software, so prevention is a slice rather than the bulk.
- T1548.004partialprevents — A.8.19's restrictions on approved executable code, least privilege for installation, and strict rules on user installation rights constrain the attack surface, but the technique exploits a legitimate macOS API that does not validate program origin or integrity, can modify legitimate programs that use the API, and relies on user credential entry — none of which A.8.19 directly addresses.
- T1553partialprevents — A.8.19's restrictions on approved executable code, trained administrators, and least-privilege installation directly block the installation-based vectors of T1553 (untrusted software landing on operational systems), but the technique also encompasses certificate theft/forge, registry/permission modification of existing trust stores, and other subversion paths that A.8.19 does not address.
- T1553.006partialprevents — A.8.19's least-privilege rules on software installation and restriction of development tools/compilers on operational systems limit who can make the configuration changes T1553.006 requires, but the technique is achieved through built-in utilities (bcdedit, csrutil), registry modification, and kernel exploitation — none of which are software installation, and authorized administrators retain the elevated permissions the technique needs.
- T1554partialrecovers — A.8.19 mandates archiving old versions of software as a contingency measure and using a configuration control system, providing the exact mechanism to restore a compromised binary to its known-good state.
- T1556partialprevents — A.8.19 prevents unauthorized installation of authentication-modifying software (e.g., rogue PAM modules, authentication plugins) by restricting who can install, requiring approved code, and maintaining audit logs of changes to operational software, but it does not prevent in-memory modifications to authentication processes, use of built-in tools by a compromised administrator, or modifications that don't constitute 'software installation' in the clause's sense.
- T1556.001partialprevents — A.8.19's controls on approved executable code, configuration management, least privilege for software installation, and audit logging constrain the file-system and installation vectors an adversary would need to modify LSASS or plant authentication-patching malware on a domain controller, but the technique's core mechanism — in-memory patching of a running authentication process (as in Skeleton Key) — is a runtime integrity concern that A.8.19 does not address, and an actor with domain-admin privileges can bypass the installation controls.
- T1556.002partialprevents — A.8.19 restricts software installation to approved code by trained administrators, which can prevent a malicious password filter DLL from being registered, but the control does not eliminate the risk because an administrator with legitimate access could still install a malicious DLL or an attacker with elevated privileges could bypass the approval process.
- T1556.003partialprevents — A.8.19's configuration control system, audit logging of updates, and least-privilege rules for software installation constrain unauthorized modification of operational software including PAM components, but the clause is primarily framed around installation of new software rather than tampering with existing system files, and an adversary with sufficient privilege can still bypass these procedural controls.
- T1556.004partialprevents — A.8.19's purpose explicitly targets integrity of operational systems and preventing exploitation of technical vulnerabilities, and its controls (trained administrators, management authorization, approved executable code only, configuration control, audit logs) directly constrain unauthorized software installation including malicious patches to system images; however, the technique specifically targets network devices whose firmware update paths often sit outside the standard operational-system software installation process the clause governs, and an adversary with administrative access to the device can still bypass the authorization and approval gates, so the control reduces but does not eliminate the technique.
- T1556.006partialprevents — A.8.19's controls on authorized administrators, approved executable code, configuration control and audit logging provide some prevention against the 'patching MFA programs' variant of the technique, but the bulk of T1556.006 — abusing legitimate features like Conditional Access Policy exclusions, registering adversary-controlled MFA methods, and modifying the hosts file — operates through configuration changes and identity-provider interfaces that fall outside A.8.19's software-installation scope, and the technique presupposes the adversary already holds administrative access that A.8.19's authorization gates do not stop.
- T1556.007partialprevents — A.8.19's configuration control system, restriction to approved executable code, and audit logging of updates constrain on-premises vectors such as DLL injection into PTA agents or modification of AD FS configuration files, but the technique's cloud-side vector (registering a new PTA agent via the Entra web console) and the fact that the adversary often operates with already-privileged access fall outside the clause's scope of software installation on operational systems.
- T1556.008partialprevents — A.8.19 restricts software installation to approved code by trained administrators, which blocks the adversary's ability to plant a malicious DLL on the system, but the control does not prevent an administrator from being tricked or coerced into installing a malicious DLL that appears legitimate.
- T1560.001partialprevents — A.8.19's restrictions on what software users can install can block third-party archive utilities (7-Zip, WinRAR, WinZip) from being present, but the built-in OS utilities (tar, zip, diantz, makecab, xcopy, certutil) that T1560.001 primarily relies on are part of the platform and cannot be removed by an installation-control policy, so the technique still runs against the bulk of its denominator.
- T1560.002partialprevents — A.8.19 restricts what software users and administrators can install on operational systems, which prevents adversaries from dropping additional archival libraries, but the technique's primary vector is libraries preinstalled on the platform (bzip2, zip, zlib) that A.8.19's installation controls do not reach, leaving the bulk of the technique's mechanism intact.
- T1564.006partialprevents — A.8.19's restrictions on installing only approved executable code and enforcing least privilege for software installation block the vectors that require dropping new binaries (VirtualBox, QEMU emulators) or installing third-party virtualization software, but the technique's native/built-in paths — Hyper-V already present on Windows, Windows Sandbox as an OS feature, and VM creation on existing ESXi infrastructure — are not installations the control reaches, so a meaningful slice of the technique remains open.
- T1565.003partialprevents — A.8.19's configuration control system over operational software and audit logging of updates constrain unauthorized modifications to installed binaries — one vector for T1565.003 — but the technique's core runtime manipulation (file association changes, masquerading, in-memory data tampering) occurs post-installation and is not reached by installation-stage controls.
- T1566.001partialprevents — A.8.19 restricts what users can install on operational systems and requires approved executable code only, which can block payloads that attempt to persist via installation; however, the technique's core mechanism is user execution of an attachment, which often runs in-memory or exploits the opening application without requiring installation, so the control addresses a slice of the technique rather than its primary path.
- T1566.004partialprevents — A.8.19's restriction on user installation privileges and enforcement of approved-only executable code can prevent the outcome where a vished user is tricked into installing a remote management tool, but it does not reach the social engineering itself, credential disclosure, or directing users to malicious URLs — the technique's other delivery paths remain intact.
- T1569.002partialprevents — A.8.19's restrictions on approved executable code, least privilege for installation, and prohibition of unvetted software block the path where an adversary registers a new malicious service binary on an operational system, but the technique also runs by modifying existing services or invoking the SCM API with tools already present (sc.exe, PsExec), which A.8.19 does not reach.
- T1574partialprevents — A.8.19's controls on approved executable code, trained administrators, least privilege for installation, and prohibition of unvetted software prevent the subset of T1574 sub-techniques that require dropping a malicious payload onto the system (e.g. installer-based or side-loaded components), but the technique's core mechanism — manipulating how the OS locates and runs already-installed programs via search order, PATH, registry, or linker hijacking — operates on existing software and is outside the clause's installation-focused scope.
- T1574.001partialprevents — A.8.19's installation governance — approved executable code only, configuration control system, audit logs, least privilege for installation — blocks the pathway where unauthorized DLLs are introduced as 'new software' onto operational systems, but it does not reach DLL hijacking techniques that work by substituting or repositioning DLLs already present on the system, exploiting search order, or dropping DLLs through a foothold obtained by other means, since the control governs installation rather than runtime file integrity.
- T1574.004partialprevents — A.8.19's least-privilege rules on software installation and the requirement that only approved executable code be installed constrain where untrusted files (including malicious dylibs) can be placed, but the control targets formal installation processes rather than the runtime file-placement vector dylib hijacking exploits, leaving writable search paths and macOS-specific library-loading behavior outside its scope.
- T1574.005partialprevents — A.8.19's controls on approved executable code, trained administrators with management authorization, configuration management, and audit logging reduce the likelihood of malicious binaries being placed in installer directories, but the technique specifically exploits file system permissions weaknesses on installer binaries/directories that A.8.19 does not directly address — the hijack can succeed even when installation processes are fully controlled, so the preventive effect is indirect and bounded.
- T1574.007partialprevents — A.8.19's controls on approved executable code, trained administrators, configuration management, and least-privilege installation rules block the placement of unauthorized binaries into PATH directories, but the technique can also succeed by modifying the PATH variable itself or by writing into directories the user already controls — neither of which is a software installation and neither of which A.8.19 addresses.
- T1574.008partialprevents — A.8.19's restrictions on approved executable code, configuration control, audit logs, and least-privilege installation rules constrain the placement of unauthorized binaries on operational systems, which is a precondition for search-order hijacking; however, the technique exploits directory write access and existing program behavior rather than formal installation, so an adversary with directory write capability through another vector can still drop a hijacking binary despite the control.
- T1574.009partialprevents — A.8.19's configuration control system (item e), approved-executable-code requirement (item b), and least-privilege installation rules can catch unquoted paths during the change/install review and restrict where executables may be placed, but the clause targets the installation act and does not mandate path-quoting review of existing service registrations or shortcuts, so the prevention is a slice of the technique's surface rather than a closure.
- T1574.010partialprevents — A.8.19 requires approved executable code, least privilege for installation, and configuration control, which together prevent unauthorized replacement of service binaries, but the technique exploits file permission weaknesses that exist independently of the software installation process, so the control constrains the attack surface rather than closing it completely.
- T1599partialprevents — A.8.19 keeps operational software patched, restricts installations to approved code, and enforces configuration control and audit logging on operational systems including network devices, which reduces the vulnerability-exploitation path into routers/firewalls; but T1599's primary mechanism is gaining sufficient rights on the boundary device (credential compromise, exploitation of running services, misconfiguration abuse), which A.8.19 does not address.
- T1600partialprevents — A.8.19's controls on approved executable code, trained administrators, management authorization, testing, and audit logs prevent the subset of T1600 that involves unauthorized software installation or modification on network devices, but do not address configuration changes to existing encryption settings, key-space reduction, or hardware-level disabling of crypto capabilities.
- T1601partialprevents — A.8.19 constrains the legitimate software installation process on operational systems (including network devices) through trained administrators, management authorization, approved code, configuration control, and audit logs, which blocks the casual or unauthorized-installation path to T1601; however, it does not prevent adversaries who exploit vulnerabilities to modify the system image, who compromise an authorized administrator's credentials, or who perform in-memory modifications during runtime, so the technique remains reachable through paths the control does not cover.
- T1601.001partialprevents — A.8.19's authorization, audit-log, configuration-control and least-privilege requirements directly constrain the storage-side vector (adversary using standard operator procedures to overwrite the image), but the in-memory modification paths via debug commands and ROMMONkit boot-loader manipulation sit below the installation layer the clause governs, and an adversary wielding legitimate admin credentials still drives the standard procedure the clause authorizes.
- T1610partialprevents — A.8.19's principles of trained administrators, management authorization, approved executable code, least privilege for installation, and strict rules on permitted software types can be applied to container deployment, constraining unauthorized or malicious container creation; however, the control is framed around traditional software installation on operational systems and does not specifically address container orchestration platforms (Kubernetes, Docker, Kubeflow), and container deployment is a legitimate operational activity that must be permitted, so the control manages rather than prevents the technique.
- T1612partialprevents — A.8.19's restrictions on who may install software (trained administrators only), what may be installed (approved executable code only), and least privilege over installation would constrain unauthorized container builds, but the technique specifically targets the Docker build API which is commonly available to developers and operators in containerized environments, and A.8.19 does not specifically address container image construction as a distinct installation path.
- T1677partialprevents — A.8.19's configuration control system, audit log of all updates, and 'only approved executable code' requirements can constrain unauthorized changes to CI configuration files and build artifacts that feed operational systems, but the control's primary scope is installation ON operational systems rather than the build pipeline itself, leaving the core of T1677 — poisoning CI configs, indirect file injection, and malicious pull requests against self-hosted runners — largely outside its reach.
- T1684partialprevents — A.8.19's restrictions on user installation privileges, approved-executable-only rules, and least privilege for software installation prevent the 'introduction of malicious payloads or software' outcome of social engineering, but the control does not address the other T1684 outcomes (password resets, MFA changes, financial approvals, sensitive disclosure) and a trained administrator can still be socially engineered into authorizing a change.
- T1687partialprevents — A.8.19 requires only approved executable code on operational systems and mandates testing before installation, which reduces the attack surface by keeping unpatched defensive software off production, but it does not eliminate the underlying vulnerabilities in the defensive software itself, leaving a bounded remainder.
- T1689partialprevents — A.8.19's requirements to maintain vendor and open-source software at supported/current levels, restrict installation to approved executable code via trained administrators, and enforce configuration control directly prevent the installation-based downgrade vectors (e.g., rolling back to an unpatched version, installing an older PowerShell), but cannot prevent downgrade mechanisms that exploit built-in backward compatibility or protocol negotiation (HTTPS→HTTP, boot manager downgrade) without new installation.
Prevented OWASP Web Top 10 (2025) risks (1)
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).
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.