Compliance
What is Compliance?
ComplianceThe discipline of meeting legal, regulatory, contractual, and internal security requirements through documented controls, evidence collection, and ongoing assessment.
Compliance is the practice of ensuring that an organization's people, processes, and technology adhere to the laws, regulations, industry standards, and contractual obligations applicable to its business. In cybersecurity, this typically covers data-protection law (GDPR, Regulation (EU) 2016/679, enforceable since 25 May 2018; CCPA; HIPAA), industry frameworks (PCI DSS, SOC 2, ISO/IEC 27001:2022), and sector-specific rules (SOX, GLBA, FedRAMP).
A mature programme is more than a checklist. It defines control objectives, maps each to authoritative sources through a crosswalk so that one implemented control (say, centralized logging) satisfies many frameworks at once, generates evidence (policies, configuration exports, logs, attestations), and is verified through internal audits and external assessment. The assurance models differ in kind: ISO/IEC 27001 certifies that an Information Security Management System exists and is audited by an accredited body, whereas a SOC 2 report is an AICPA attestation describing controls against the Trust Services Criteria — a Type II report tests their operating effectiveness over a period, usually 6–12 months, not just a point in time.
Requirements also move. PCI DSS retired v3.2.1 on 31 March 2024, and its 51 future-dated v4.0 requirements became mandatory after 31 March 2025, forcing changes such as phishing-resistant MFA and tighter script-integrity controls on payment pages. The enduring caveat: compliance is a minimum baseline, not an end state. Target breached in 2013 while holding a valid PCI attestation — being compliant on paper does not guarantee being secure.
flowchart TD
A[Identify obligations:<br/>laws, standards, contracts] --> B[Define control objectives]
B --> C[Crosswalk: one control →<br/>many frameworks]
C --> D[Implement controls]
D --> E[Collect evidence:<br/>policies, logs, attestations]
E --> F[Internal audit]
F --> G{External assessment:<br/>ISO cert / SOC 2 / QSA}
G -- Gaps --> D
G -- Pass --> H[Certification / report<br/>re-assess as rules change]● Examples
- 01
A SaaS provider undergoing a SOC 2 Type II audit to satisfy enterprise customers.
- 02
A retailer maintaining PCI DSS controls to process payment card data.
● Frequently asked questions
What is Compliance?
The discipline of meeting legal, regulatory, contractual, and internal security requirements through documented controls, evidence collection, and ongoing assessment. It belongs to the Compliance & Frameworks category of cybersecurity.
What does Compliance mean?
The discipline of meeting legal, regulatory, contractual, and internal security requirements through documented controls, evidence collection, and ongoing assessment.
How do you defend against Compliance?
Defences for Compliance typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Compliance?
Common alternative names include: Regulatory compliance, Security compliance.