Coverage Exclusion
A category of loss carved out of an insurance policy regardless of how the policyholder behaved -- war and hostile action, infrastructure failure, prior known incidents, or bodily injury and property damage handled by other lines. An exclusion is about the NATURE of the loss, which distinguishes it from a condition, which is about the policyholder's own ongoing obligations. The insurer generally bears the burden of proving an exclusion applies, and its precise wording governs rather than any general understanding of the term. Exclusions are examined on CISM, CRISC and CGRC.
Why It Matters
In practice, the exclusion that matters most in cyber is hostile or war-like action, because attribution and motive are genuinely contestable: a financially motivated ransom demand cuts against a hostile-action characterisation even when the tooling overlaps with state-linked activity, and the policy's own wording decides whether attribution by a government is required. Because the insurer must prove the exclusion applies, an invocation is the start of a fact-specific dispute rather than the end of a claim, which is why coverage counsel is engaged early rather than after the denial is final. Another commonly misread exclusion is betterment: a policy restores what existed before the incident and does not fund security improvements beyond that baseline. On certification exams such as CISM, CRISC and CGRC, expect questions distinguishing exclusions from conditions, and on who carries the burden of proof for each.
Practice this topic
Test your knowledge of Coverage Exclusion concepts with exam-style practice questions.
Related GRC terms
Risk Assessment
The process of identifying, analyzing, and evaluating potential risks to an organization's information assets to determine the likelihood and impact of threats exploiting vulnerabilities. Risk assessment methodologies include qualitative (rating risks as High/Medium/Low), quantitative (calculating Annual Loss Expectancy using SLE x ARO = ALE), and hybrid approaches. Frameworks like NIST SP 800-30, ISO 27005, and FAIR provide structured risk assessment processes. The output drives risk treatment decisions: accept, mitigate, transfer (insurance), or avoid. Risk assessment is the cornerstone of CISSP Domain 1, CISM, and CISA certifications.
Vulnerability Assessment
A systematic process to identify, quantify, and prioritize security vulnerabilities in systems, applications, and networks using automated scanning tools and manual review. Common tools include Nessus, Qualys, OpenVAS, and Rapid7 InsightVM. Vulnerability assessments differ from penetration testing, they identify weaknesses without actively exploiting them. Results are typically scored using CVSS (Common Vulnerability Scoring System) and prioritized by severity, asset criticality, and exploitability. Regular vulnerability assessments are required by PCI DSS, HIPAA, and other compliance frameworks and are a key topic in Security+, CySA+, and CISSP certifications.
Penetration Testing
An authorized simulated cyberattack on a computer system, network, or application performed to evaluate its security posture and identify exploitable vulnerabilities. Pentest types include black box (no prior knowledge), white box (full system knowledge), and gray box (partial knowledge). The methodology follows phases: planning and scoping, reconnaissance, scanning, exploitation, post-exploitation, and reporting. Industry standards include the PTES, OWASP Testing Guide, and NIST SP 800-115. Penetration testing is the focus of OSCP, PenTest+, CEH, and GPEN certifications and a key assessment method in CISSP Domain 6.
Compliance
The act of conforming to established guidelines, specifications, regulations, or legislation related to information security and data protection. Key compliance frameworks include PCI DSS (payment card data), HIPAA (healthcare data), SOX (financial reporting), GDPR (EU personal data), and FedRAMP (US government cloud). Non-compliance can result in significant fines, legal liability, and reputational damage. Organizations use controls frameworks (NIST CSF, ISO 27001, CIS Controls) to demonstrate compliance. Compliance management is a central topic in CISA, CISM, and CISSP Domain 1 (Security and Risk Management).
NIST Framework
A set of guidelines and best practices published by the National Institute of Standards and Technology to manage cybersecurity risk, most commonly referring to the NIST Cybersecurity Framework (CSF) with its five core functions: Identify, Protect, Detect, Respond, and Recover. NIST also publishes the SP 800 series (including 800-53 for security controls, 800-171 for CUI, and 800-63 for digital identity). The framework is voluntary but widely adopted across industries and required for U.S. federal agencies. NIST provides the foundation for many organizational security programs and is heavily referenced in CISSP, CISM, and Security+ certifications.
ISO 27001
An international standard for information security management systems (ISMS) that specifies requirements for establishing, implementing, maintaining, and continually improving an organization's security management program. ISO 27001 follows a Plan-Do-Check-Act (PDCA) cycle and requires organizations to assess risks, implement appropriate controls (from the Annex A control set), and undergo regular audits. Certification is granted by accredited third-party auditors and is valid for three years with annual surveillance audits. ISO 27001 is globally recognized and often required by enterprise customers and partners. It is a key framework in CISM, CISA, and CISSP GRC domains.