Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 38 ยท Compliance and Governance

Compliance Frameworks Overview

A plain-language tour of cloud compliance: ISO 27001, SOC 2, PCI DSS, HIPAA, GDPR, CIS benchmarks and NIST CSF, how controls map to evidence, and compliance vs security.

Compliance means proving that your organisation follows a set of rules. Those rules may come from the law (GDPR, HIPAA), from the industry (PCI DSS for card payments), from customers who ask for an audit report (SOC 2) or from a voluntary standard (ISO/IEC 27001). In the cloud, compliance matters for a practical reason as well: customers, banks and partners often will not do business with you until you can show evidence that you protect their data.

This lesson is a map of the landscape, not legal advice. You will learn what the main frameworks are, how they are structured, how cloud providers help and how to track controls and evidence. Always check the exact current text of a framework with your compliance officer or auditor, because requirements change.

This course explains concepts for learning. It is not legal advice, and passing an audit does not by itself guarantee that a system is secure.

Standards, regulations and benchmarks

Three different kinds of document are often mixed up:

  • Regulations and laws are mandatory and enforced by authorities, such as GDPR in the EU, HIPAA in the United States health sector or national data protection laws.
  • Standards and attestations are voluntary frameworks checked by an auditor, such as ISO/IEC 27001 (certification) and SOC 2 (an attestation report).
  • Benchmarks and guidelines give detailed technical advice you can measure against, such as the CIS Benchmarks and the NIST Cybersecurity Framework.
Framework Type Who it concerns Core idea
ISO/IEC 27001 Certifiable standard Any organisation An information security management system (ISMS) built on risk assessment, with controls from Annex A
SOC 2 Audit report (AICPA) Service providers, especially SaaS Controls judged against the trust criteria: security, availability, processing integrity, confidentiality, privacy
PCI DSS Industry standard Anyone storing, processing or transmitting payment card data Concrete requirements: network security, strong access control, encryption, monitoring, testing
HIPAA US law Healthcare organisations and their business associates Safeguards for protected health information (administrative, physical, technical)
GDPR EU regulation Anyone handling personal data of people in the EU Lawful basis, data subject rights, breach notification, privacy by design
NIST CSF Voluntary framework Any organisation Functions: Govern, Identify, Protect, Detect, Respond, Recover
CIS Benchmarks Technical baselines Cloud and OS administrators Hardening settings with a pass or fail check, for AWS, Azure, Google Cloud and Kubernetes
CSA CCM Cloud control matrix Cloud providers and customers Cloud-specific control domains, mapped to many other standards

Read the table as a family tree. Most frameworks overlap heavily: access control, encryption, logging, change management and incident response appear in nearly all of them. A control mapping lets one implemented control satisfy several frameworks at once, which saves a great deal of work.

Shared responsibility applies to compliance too

Cloud providers undergo audits themselves and publish the results: ISO certificates, SOC reports and PCI attestations are available through each provider's compliance portal (for example AWS Artifact, Microsoft Service Trust Portal and Google Cloud Compliance Resource Center). That covers the provider's part: physical security, hypervisors, data centres.

It does not make your workload compliant. Customer-side controls, such as who can read your database, whether your storage is encrypted and whether you retain logs, remain your job. Using a PCI-compliant cloud does not make your payment application PCI compliant. The idea is the same as in the shared responsibility model described at the start of this course.

flowchart TB
    subgraph Prov["Provider evidence (inherited)"]
      A["Data centre security"] --- B["Hypervisor and hardware"]
    end
    subgraph Cust["Your evidence (customer controls)"]
      C["IAM and MFA"] --- D["Encryption settings"]
      D --- E["Logging and retention"]
      E --- F["Patching and configuration"]
    end
    Prov --> Audit["Auditor reviews both"]
    Cust --> Audit

Auditors accept provider reports for provider controls, but expect your own evidence for your controls.

From requirement to control to evidence

Compliance work follows one pattern:

  1. Requirement: a sentence in the framework, such as "access to systems is restricted to authorised users".
  2. Control: what you do about it, such as "all production access uses SSO with MFA, and admin rights are reviewed quarterly".
  3. Evidence: proof the control exists and operates, such as the identity provider's MFA setting, a quarterly review ticket and log samples.

Auditors test two things: whether a control is designed properly and whether it operated consistently during the audit period (often 6 to 12 months for SOC 2 Type 2). Dated evidence collected continuously beats screenshots gathered in a panic the week before the audit.

Try it: a control and evidence tracker

This small script tracks controls mapped to several frameworks, flags missing or stale evidence and shows coverage per framework. All control names and dates are invented.

Python Track controls, frameworks and evidence

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The report shows why mapping pays off: fixing the stale encryption evidence (C2) improves four frameworks at once.

Automating compliance in the cloud

Manual checks do not scale. Typical building blocks are:

  • Continuous configuration checks against benchmarks, using cloud-native services (AWS Config, Azure Policy, Google Security Command Center) or posture tools; see posture management and misconfiguration.
  • Policy as code to prevent non-compliant resources from being created at all; see policy as code.
  • Evidence collection tools that pull configuration snapshots, access reviews and logs automatically and keep them dated.
  • Tagging and inventory, so you know which resources hold regulated data and where they are.
  • Change management: pull requests, approvals and pipeline logs are excellent evidence that changes were reviewed.

Compliance is not the same as security

A system can pass an audit and still be breached, because audits sample controls at points in time and frameworks set a minimum. The reverse also happens: a secure system with no documentation may fail. Aim for both: use the frameworks as a checklist of minimum expectations, run your security programme on real risks and keep evidence as a by-product of good engineering rather than a separate chore.

A practical starting path

  1. Decide which obligations apply (laws first, then customer demands).
  2. Inventory your data and systems, and classify the data.
  3. Pick one framework as your backbone (ISO 27001 or SOC 2 are common) and map the others to it.
  4. Implement and automate the controls; assign an owner to each.
  5. Collect evidence continuously, review it regularly and prepare for the auditor.
  6. Re-assess risks at least yearly and after major changes.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which of these is a mandatory law rather than a voluntary standard?

    GDPR is an EU regulation enforced by authorities. ISO 27001, CIS Benchmarks and NIST CSF are voluntary.
  2. 2. Your cloud provider has a PCI DSS attestation. What does that mean for your payment application?

    Compliance is shared. The provider's report covers the infrastructure it runs; your configuration and application are in your scope.
  3. 3. What are the three steps in the chain used in compliance work?

    Each requirement is met by a control, and each control needs evidence that it exists and operates.
  4. 4. Why does a control mapping save effort?

    Frameworks overlap heavily, so a single control with good evidence, such as enforced MFA, can be reused across audits.

Summary

  • Compliance comes from laws, standards and benchmarks; ISO 27001, SOC 2, PCI DSS, HIPAA, GDPR, NIST CSF and CIS Benchmarks are the usual names.
  • Providers' certifications cover their part only; you remain responsible for your own configuration and data.
  • Work from requirement to control to dated evidence, and map one control to many frameworks.
  • Automate checks, policy enforcement and evidence collection.
  • Compliance is a floor, not proof of security; do both well.

Next: Policy as Code