A.8.10 Technological
Information deletion
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 (14)
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
- MP-6mostlycovers — A.8.10's deletion requirement (including sanitization for media to meet legal/regulatory needs) accounts for the bulk of MP-6's sanitization mandate before disposal/reuse, but leaves a residual on MP-6's explicit strength/integrity calibration to security categorization that A.8.10 does not directly address.
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).
Related OWASP ASVS 5.0 requirements (7)
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 (3248)
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-1266fullblocks — A.8.10 mandates secure deletion methods and verification for decommissioned devices, so a well-implemented control ensures sensitive data is scrubbed before the device leaves the organization, leaving no exploitable residue.
- CWE-1330mostlyremoves — A.8.10 mandates deletion methods — physical destruction (via 7.14), cryptographic erasure, overwriting, and degaussing — that effectively neutralize data remanence in memory circuits. Applied where no deletion policy existed, it removes existing CWE-1330 instances on-premises and for physical media under the organization's control. The bounded remainder is cloud services (where the organization depends on the provider's deletion methods and can only verify or request) and equipment returned to vendors where auxiliary storage removal may not address remanence in the device's main memory.
- CWE-226mostlyblocks — Explicitly requires secure deletion of information before resources are reused or disposed.
- CWE-530partialremoves — A.8.10 mandates deletion of obsolete versions, copies and temporary files wherever they are located, which removes the weakness for exposed backup files that are obsolete and contain sensitive information; however, it does not address backups that are still required (e.g., for disaster recovery) but misplaced in an accessible location, where the remedy is access control or relocation rather than deletion, leaving a nameable remainder.
Mitigated MITRE ATT&CK techniques (3206)
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
- T1005partialprevents — A.8.10 securely deletes information that is no longer required, so the slice of T1005 that targets obsolete data, temporary files, and old copies cannot find what has been removed; however, the technique still runs against data that remains in active use, and A.8.10 explicitly does not address that remainder.
- T1025partialprevents — A.8.10 reduces sensitive data at rest on removable media by deleting it when no longer required, which partially prevents T1025 from succeeding in collecting sensitive data; however, data still legitimately required remains on the media and the technique still runs against whatever is there, so the prevention is a reduction of available files rather than a closure of the technique.
- T1039partialprevents — A.8.10 reduces the data available on shares by deleting obsolete, temporary and no-longer-required information, so the technique cannot succeed against that portion; but data that legitimately must remain on the share for business operations is unaffected, and the adversary's search and collection against it still runs.
- T1213partialprevents — A.8.10 deletes information that is no longer required, removing a slice of what T1213 would otherwise mine (obsolete versions, temporary files, retained-beyond-need sensitive data), but the bulk of T1213's target — current, in-use information in repositories that must be retained to support the business — is unaffected by deletion policies and remains fully reachable.
- T1213.001partialprevents — A.8.10 reduces the information available in Confluence by deleting sensitive data when no longer required, but it does not prevent the adversary from accessing Confluence or stop the mining technique from running — information that legitimately needs to remain in Confluence (policies, documentation, project schedules) is still mineable, so the technique executes against a reduced surface rather than being prevented.
- T1213.002partialprevents — A.8.10 reduces the sensitive information available in SharePoint by deleting obsolete versions, copies, temporary files and data no longer required, which shrinks what an adversary can mine; however, much of the content listed in T1213.002 (policies, network diagrams, system documentation, project schedules) must legitimately remain in SharePoint for the organization to function, and A.8.10 does not stop the adversary from accessing and reading that current content.
- T1213.005partialprevents — A.8.10 reduces the sensitive data available to be mined by enforcing retention limits and deletion in messaging platforms, but it does not prevent the adversary from accessing the messaging application itself or from mining whatever current/recent messages remain — the technique still runs and still yields value, so only a slice of the data class is removed.
- T1530partialprevents — A.8.10 prevents a slice of T1530 by ensuring sensitive data is deleted when no longer required, eliminating the over-retained data that misconfigured or stolen-credential access would otherwise expose; it does not prevent the technique against data that legitimately must remain in cloud storage, which is the bulk of the technique's surface.
- T1552partialprevents — Securely deleting credentials and other sensitive files when they are no longer needed reduces the chance an adversary will find unsecured credentials in files or other locations.
- T1552.001partialprevents — A.8.10 deletes information no longer required, including obsolete copies and temporary files, which removes some credential-bearing files the adversary would otherwise find; it does not prevent credentials from being stored in active configuration files, credential stores, or source code, which are the primary targets of T1552.001, nor does it stop the search itself.
- T1552.003partialprevents — A.8.10 mandates deletion of obsolete copies and temporary files, which can include shell history files, but the control's scope is policy-driven retention rather than real-time prevention of credential exposure through command history.
- T1552.004partialprevents — A.8.10 deletes obsolete keys, temporary key files and copies no longer required, removing a slice of what T1552.004 searches for, but the technique's primary targets are keys in active use (SSH keys, TLS certificates, device keys) which by definition cannot be deleted under the clause's 'no longer required' mandate.
- T1589partialprevents — A.8.10's purpose is explicitly to prevent unnecessary exposure of sensitive information, and deleting obsolete data, copies, temporary files and old records removes material an adversary could otherwise harvest from the organization's own systems and data sets; however, T1589 is broad — active scanning of authentication services, social media, phishing for information, and current operational identities (employee names, emails, MFA configs) are unaffected by deletion, so only a slice of the technique's surface is closed.
- T1594partialprevents — A.8.10 deletes information that is no longer required, so a portion of what T1594 would otherwise harvest from victim-owned websites is removed before the search runs and cannot be found; however, the website still exists with currently-needed content, the search still executes, and information legitimately retained remains discoverable, so prevention is bounded to the no-longer-needed slice.
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.