Skip to content

Cache Poisoning

What is Cache Poisoning?

An attack that corrupts cached data to redirect users to malicious destinations, commonly targeting DNS caches and web application caches.

Information Security

Frameworks that govern cache poisoning

ISO 27001:2022View framework →NIST Cybersecurity Framework 2.0View framework →CIS Controls v8View framework →

What the standards actually require on cache poisoning

Requirements naming cache poisoning across 2 standards, quoted from the control text.

ITU-T X.805 - Security Architecture for End-to-End Communications2 controls

X.805 Clause 8 defines 5 Threat Categories that the X.805 Security Architecture is designed to mitigate + provides a Threat-Dimension Countermeasure Matrix linking each threat to specific Dimensions.

X805-Threats-Destruction-Corruption-Removal-Disclosure-Interruption-72Cell-Matrix-Application · ITU-T X.805 5 Threat Categories - Destruction + Corruption + Removal + Disclosure + Interruption + Threat-Dimension Countermeasure Matrix + 72-Cell Matrix Application + STRIDE + MITRE ATT and CK + Network Modular Risk Assessment →
GLI-33 - Gaming Laboratories International Event Wagering Systems1 control

DNS for the system uses a secure primary and a secure secondary server, logically and physically separate; the primary sits in a secure data centre or an appropriately secured hypervisor; logical and physical access is restricted to authorised personnel;

gli-33-gaming-laboratories-international-event-wagering-systems::B.6.1 · B.6.1 Domain Name Service (DNS) Requirements →

Questions people ask about cache poisoning

What is Cache Poisoning?
An attack that corrupts cached data to redirect users to malicious destinations, commonly targeting DNS caches and web application caches.
Why is Cache Poisoning important for compliance?
Cache Poisoning is a key concept in Information Security. Understanding cache poisoning helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Cache Poisoning?
Cache Poisoning appears in the requirement text of ITU-T X.805 - Security Architecture for End-to-End Communications, GLI-33 - Gaming Laboratories International Event Wagering Systems. Across these standards we have identified 3 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Cache Poisoning?
Explore our compliance framework pages to see how cache poisoning applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Cache Poisoning applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Explore on Platform
Written and maintained by Gerard Blokdyk, The Art of Service.