Security Notes
Governance, Risk & Compliance

Compliance, Frameworks & Regulations

Overview of the most important security frameworks, regulations, and standards you'll encounter in security engineering interviews and on the job. Each section answers: what is it, why it exists, what it requires, and what interviewers ask about it.

18 min read 14 sections 6 model answers version 5 · updated 2026-10-15

Start here: the basics in plain words

Compliance means being able to show an outsider (a customer, an auditor, a regulator) that you protect information the way you're supposed to. The names on this page blur together until you sort them into four kinds of thing:

Laws and regulations

you must follow if they apply to you, with fines if you don't: GDPR (personal data of people in the EU), HIPAA (US health data), NIS2 (EU essential services).

Industry and contract rules

you must follow to do certain business: PCI DSS if you handle card payments, because the card brands require it.

Standards you choose to certify against

to prove you're well run: ISO 27001 (a certificate from an accredited auditor) and SOC 2 (an auditor's report, common in the US).

Frameworks

that are guidance, not pass/fail: NIST CSF and NIST SP 800-53, used to organise and measure a security programme.

A concrete example: a European SaaS company that stores customer data and takes card payments must follow GDPR (law) and PCI DSS (card rules). It gets ISO 27001 certified and a SOC 2 report because its customers' procurement teams ask for them. It uses NIST CSF internally to plan its roadmap.

Control

A specific safeguard, e.g. "MFA for all admins" or "logs kept for 12 months".

Audit

An independent check that the controls exist and actually work, backed by evidence.

Evidence

Proof for the auditor: screenshots, tickets, access-review records, config exports. Engineers produce most of it.

Scope

Which systems, teams and locations the certification or regulation covers. A narrow scope can make a certificate say less than it seems.

Compliant ≠ secure

Passing an audit shows controls existed when sampled; it doesn't mean an attacker can't get in.

Memory hook

"law, contract, certificate, guidance"Ask which of the four a name is, and you know whether it's mandatory, who checks it, and what failing costs.


NIST Cybersecurity Framework (CSF)

Current versionCSF 2.0 (released February 2024) Published by: NIST (National Institute of Standards and Technology, USA) Mandatory?: No — voluntary for most; effectively required for federal agencies and their contractors

What it is

A risk-based framework for managing cybersecurity risk. Originally aimed at critical infrastructure, now widely adopted across all sectors globally. CSF 2.0 added a new Govern function.

Six Functions (CSF 2.0)

FunctionWhat it covers
Govern (GV)NEW in 2.0: organizational context, roles, risk management strategy, policies
Identify (ID)Asset management, risk assessment, supply chain risk
Protect (PR)Access control, awareness training, data security, platform security
Detect (DE)Continuous monitoring, anomaly detection, adverse event analysis
Respond (RS)Incident response planning, communication, mitigation
Recover (RC)Recovery planning, improvements, communication after incident

Why it matters in interviews

  • Provides a common vocabulary for discussing security posture
  • "How does your security program map to the NIST CSF?" is a common question at senior levels
  • Helps frame your incident response/detection answers: "In the Detect phase, we use..."

NIST SP 800-53

Current versionRev 5 (2020) Full name: Security and Privacy Controls for Information Systems and Organizations

What it is

A comprehensive catalog of security and privacy controls. Think of it as an encyclopedia of security requirements — over 1,000 controls across 20 control families.

Key Control Families

FamilyCodeExamples
Access ControlACLeast privilege, account management, remote access
Audit & AccountabilityAUAudit logging, log retention, review
Configuration ManagementCMBaseline config, change control
Identification & AuthenticationIAMFA, password complexity, PKI
Incident ResponseIRIR plan, testing, handling, reporting
System & Communications ProtectionSCTLS, boundary protection, cryptography
Supply Chain Risk ManagementSRNEW in Rev 5 — supply chain controls

Who uses it

  • US federal agencies (mandatory)
  • Companies seeking FedRAMP authorization (cloud providers)
  • Defense contractors (often required)
  • Any organization wanting a comprehensive controls baseline

Interview relevance

  • Understanding 800-53 shows you know controls-based thinking: "This maps to AC-6 (Least Privilege)" or "IR-4 (Incident Handling) requires this playbook"
  • Often referenced in cloud security assessments

NIST SP 800-61 (Incident Response)

Full nameComputer Security Incident Handling Guide (Rev 2)

What it is

The authoritative guide for building an incident response capability. Defines the IR lifecycle:

Preparation → Detection & Analysis → Containment, Eradication & Recovery → Post-Incident Activity

Key concepts

  • Incident vs event: an event is any observable occurrence; an incident is an event that violates policy or threatens security
  • Incident severity categories: functional impact (data integrity, availability), information impact (data classification affected)
  • Evidence collection and chain of custody
  • Communication: when to involve legal, management, law enforcement, external parties

SOC 2

Published byAICPA (American Institute of CPAs) Mandatory?: No — but de facto required for SaaS companies selling to enterprises

What it is

An auditing standard for service organizations (SaaS companies, cloud providers) that evaluates controls related to the five Trust Service Criteria (TSC):

CriterionWhat it covers
SecurityProtecting system resources against unauthorized access (required)
AvailabilitySystem is available for operation as committed
Processing IntegritySystem processing is complete, valid, accurate, timely
ConfidentialityInformation designated as confidential is protected
PrivacyPersonal information is collected, used, retained, and disclosed properly

Type I vs Type II

Type I

point-in-time — "controls are suitably designed as of date X"

Type II

period-of-time (usually 6-12 months) — "controls operated effectively over the period" — this is what enterprise customers actually want

Memory hook

Type I is a photo, Type II is a video. Type I proves your controls look right on one day (designed properly). Type II proves they actually worked over months (operating effectively) — the auditor pulls evidence across the whole period, e.g. "show me every access review for the last 9 months." Mnemonic: I = instant (a snapshot), II = time (a track record). Enterprises want Type II because anyone can pass inspection for a day; Type II shows the controls run continuously. Also remember SOC 2 is a report, not a pass/fail certificate — it's an auditor's attestation against the Trust Service Criteria, of which only Security ("Common Criteria") is mandatory; the other four are opt-in based on what you commit to customers.

Why it matters

A SOC 2 Type II report is what enterprise customers ask for in security questionnaires. Having it means: a third-party auditor verified your security controls work.

Common controls testedaccess reviews, change management, encryption at rest/transit, vulnerability management, incident response, log retention.

🎯

On the job. When a vendor sends a SOC 2 Type II report, read four things before the opinion letter: the scope (is the product you're buying actually in it?), the period (a report that ended 10 months ago needs a bridge letter), the exceptions in the testing section, and the complementary user entity controls — the controls the vendor expects you to run, such as enforcing MFA on your own accounts. A clean opinion on the wrong scope is worth nothing.


ISO 27001

Published byISO (International Organization for Standardization) Mandatory?: No — but required in many EU/UK/global enterprise deals and supply chains

What it is

An international standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS).

Structure

Main clauses (4-10)

organizational context, leadership, planning, support, operation, performance evaluation, improvement

Annex A

93 controls across 4 themes: Organizational (37), People (8), Physical (14), Technological (34)

Certification

third-party audit by an accredited certification body → ISO 27001 certificate (valid 3 years, annual surveillance audits)

Full deep dive (clauses, Annex A, Statement of Applicability, audit cycle, interview Q&A): ISO/IEC 27001.

ISO 27001 vs SOC 2

ISO 27001SOC 2
ScopeISMS (process + controls)Controls for specific services
GeographyGlobal (especially EU/UK/Asia)Primarily US
OutputCertificateAudit report
FocusManagement systemControl effectiveness
Memory hook

ISO 27001 certifies the factory, SOC 2 inspects the products. ISO 27001 is about having a working management system (an ISMS — the process for how you manage risk continuously), and you get a certificate. SOC 2 is about whether your specific controls actually operate, and you get a report an auditor wrote that customers read. Geography rule of thumb: ISO = the global/EU answer, SOC 2 = the US answer — many companies end up doing both because different customers ask for different ones. Mnemonic: ISO = system + certificate (global); SOC 2 = controls + report (US).


PCI-DSS

Full namePayment Card Industry Data Security Standard Current version: PCI-DSS v4.0 (2022) Mandatory?: Yes — for any organization that stores, processes, or transmits cardholder data

What it is

12 requirements for protecting cardholder data (credit/debit card numbers). Enforced by card brands (Visa, Mastercard) through merchant agreements. Non-compliance → fines, increased transaction fees, loss of ability to accept cards.

12 Requirements (grouped)

Build and maintain a secure network

  1. Install and maintain network security controls (firewalls)
  2. Apply secure configurations to all system components

Protect account data3. Protect stored account data (encryption, masking of PAN) 4. Protect cardholder data in transit (TLS, no WEP)

Maintain a vulnerability management program5. Protect against malicious software (AV) 6. Develop and maintain secure systems (patching, secure dev)

Implement strong access control7. Restrict access on need-to-know 8. Identify and authenticate access 9. Restrict physical access

Monitor and test networks10. Log and monitor all access to system components 11. Test security of systems regularly (pen tests, ASV scans)

Maintain an information security policy12. Support information security with organizational policies and programs

Key concepts for interviews

Cardholder Data Environment (CDE)

scope of PCI assessment — minimize CDE to reduce compliance burden

Tokenization

replace PANs with tokens; tokens are useless outside the payment processor → reduces CDE scope dramatically

SAQ vs ROC

Self-Assessment Questionnaire (smaller merchants) vs Report on Compliance (larger merchants, requires QSA)

v4.0 changes

customized implementation option (risk-based alternative controls), evolved MFA requirements, new software security requirements

📰

Real incident — Target (2013). Target had been certified PCI DSS compliant a few months before attackers used credentials stolen from its heating and refrigeration contractor to get into the network and install malware on point-of-sale terminals, stealing about 40 million card numbers. Compliance is a point-in-time check against a list; it didn't require isolating vendor access from the card environment strongly enough, and it didn't make anyone act on the alerts.


GDPR

Full nameGeneral Data Protection Regulation Jurisdiction: European Union + EEA; applies to any company processing EU residents' data regardless of where the company is located Effective: May 25, 2018 Penalties: Up to €20M or 4% of global annual revenue (whichever higher)

Core Principles

Lawfulness, fairness, transparency

data must be processed lawfully; users must know how their data is used

Purpose limitation

data collected for one purpose can't be used for a different purpose

Data minimization

collect only what you need

Accuracy

keep data accurate and up to date

Storage limitation

don't keep data longer than necessary

Integrity and confidentiality

protect data appropriately (encryption, access controls)

Accountability

organizations must demonstrate compliance

Rights of Data Subjects

RightDescription
Right of accessUser can request a copy of their data
Right to rectificationCorrect inaccurate data
Right to erasure ("right to be forgotten")Delete data in certain circumstances
Right to portabilityReceive data in machine-readable format
Right to objectObject to processing for direct marketing
Right to restrict processingPause processing while dispute is resolved

Technical Requirements for Engineers

Data breach notification

72 hours to notify supervisory authority; "without undue delay" to data subjects if high risk

Privacy by design

security controls baked in from the start, not bolted on

DPIA (Data Protection Impact Assessment)

required before processing high-risk data

Data processing agreements (DPAs)

required when sharing data with processors (cloud providers, SaaS tools)

Encryption and pseudonymization

strongly recommended; can reduce obligations in breach scenarios

📰

Real incident — British Airways (2018, fined 2020). Attackers changed a script on BA's website so that card details typed into the payment page were also sent to a look-alike domain; about 400,000 customers were affected. The UK regulator fined BA £20 million (cut from a proposed £183 million), citing basic failings such as no multi-factor authentication on remote access and poor monitoring. GDPR penalties follow the security failures, not just the breach.


CCPA

Full nameCalifornia Consumer Privacy Act (+ CPRA amendment, effective 2023) Jurisdiction: California, USA — applies to businesses processing CA residents' data above certain thresholds Comparison to GDPR: narrower rights, lower penalties, more opt-out focused (vs GDPR's opt-in)

Key Rights

  • Right to know what personal information is collected
  • Right to delete personal information
  • Right to opt out of sale or sharing of personal information
  • Right to non-discrimination for exercising rights

Technical implication

"Do Not Sell My Personal Information" opt-out mechanism must be implemented in UI and data pipelines.


HIPAA

Full nameHealth Insurance Portability and Accountability Act Jurisdiction: USA — healthcare providers, health plans, healthcare clearinghouses, and their business associates Protected data: Protected Health Information (PHI) — any individually identifiable health information

Key Rules

Privacy Rule

standards for use/disclosure of PHI

Security Rule

administrative, physical, and technical safeguards for electronic PHI (ePHI)

Breach Notification Rule

notify affected individuals within 60 days; HHS if > 500 individuals

Technical Safeguards (Security Rule)

  • Unique user identification (no shared accounts)
  • Emergency access procedure
  • Automatic logoff
  • Encryption and decryption of ePHI
  • Audit controls (hardware, software, procedural)
📰

Real incident — Anthem (2015). Attackers used a phishing email to get into the health insurer and stole records of about 79 million people. In 2018 Anthem paid the US Department of Health and Human Services $16 million — then the largest HIPAA settlement — over failures including no enterprise-wide risk analysis and weak access controls.


FedRAMP

Full nameFederal Risk and Authorization Management Program Jurisdiction: USA — cloud service providers selling to US federal agencies Based on: NIST SP 800-53 Rev 5 controls, tailored for cloud

What it is

A standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services used by federal agencies.

Authorization Levels

LevelBased onExample workloads
Low125 controlsPublic-facing, no sensitive data
Moderate325 controlsPII, some sensitive data (most agencies)
High421 controlsLaw enforcement, emergency services, financial

Getting FedRAMP authorized is expensive (18+ months, $1M+) and is essentially the price of entry for selling to the US federal government.


CIS Benchmarks

Published byCenter for Internet Security What they are: Consensus-based configuration guidelines for operating systems, cloud services, containers, databases, browsers, etc.

Key benchmarks for security engineers:

  • CIS Benchmark for Ubuntu Linux
  • CIS Benchmark for AWS Foundations
  • CIS Benchmark for Kubernetes
  • CIS Benchmark for Docker
  • CIS Benchmark for macOS

Two implementation levels

Level 1

recommended minimum security settings that don't significantly impact functionality

Level 2

defense in depth; may reduce functionality; for high-security environments

Free PDFs available at cisecurity.org. Used as the baseline for many hardening scripts and cloud Security Hub findings.

In practiceCIS benchmarks are mostly consumed through scanners. Typical output against the CIS AWS Foundations Benchmark, abridged:

[PASS] 1.5  Ensure MFA is enabled for the 'root' user account
[FAIL] 1.4  Ensure no 'root' user account access key exists          ← root has a programmatic key: fix today
[FAIL] 3.1  Ensure CloudTrail is enabled in all regions               (eu-north-1, ap-south-2 missing)
[PASS] 2.1.1 Ensure S3 Bucket Policy is set to deny HTTP requests
Score: 41/58 controls passed

The score is for dashboards; the work is triaging which FAILs are real risk (a root access key) and which are accepted exceptions you document.


Framework Comparison Table

FrameworkTypeMandatory?ScopeKey output
NIST CSF 2.0Risk managementVoluntary / fed requiredOrganization-wideRisk posture
NIST 800-53Control catalogFed mandatorySystems/programsControl baseline
NIST 800-61IR guidanceVoluntaryIR capabilityPlaybooks
SOC 2Audit standardVoluntary / de factoService operationsAudit report
ISO 27001Management systemVoluntaryISMSCertificate
PCI-DSSIndustry standardMandatory (card data)Cardholder data envCompliance report
GDPRRegulationMandatory (EU residents)Personal dataLegal compliance
CCPARegulationMandatory (CA residents)Personal dataLegal compliance
HIPAARegulationMandatory (health data)PHILegal compliance
FedRAMPAuthorizationMandatory (US federal)Cloud servicesAuthorization to Operate
CIS BenchmarksConfig guidelinesVoluntarySystem configurationHardened config

Interview Questions

Q
What's the difference between SOC 2 Type I and Type II?
Model answer

Both assess a service organization's controls against the Trust Service Criteria, but over different timeframes. Type I is point-in-time — the auditor attests that the controls are suitably designed as of a specific date, essentially a snapshot. Type II covers a period, usually six to twelve months, and tests that the controls actually operated effectively throughout — the auditor samples evidence across the whole window, like every access review and change record over those months. Enterprises want Type II because designing a control well on one day proves little; Type II shows it runs continuously. I'd also note SOC 2 produces an auditor's report, not a pass/fail certificate, and only the Security criterion is mandatory — availability, confidentiality, processing integrity, and privacy are included based on what you commit to customers.

Q
You process EU customer data and have a breach. What are your GDPR obligations?
Model answer

The headline obligation is the 72-hour notification: if the breach is likely to result in a risk to individuals' rights and freedoms, you must notify the relevant supervisory authority within 72 hours of becoming aware, and if it's a high risk, also notify the affected individuals without undue delay. The notification has to describe the nature of the breach, the categories and approximate number of people and records affected, the likely consequences, and the measures taken. Beyond notification, you must document the breach internally regardless of whether it's reportable, so the clock and the documentation start immediately on detection — which is exactly why incident response and forensics readiness matter. Whether you're the controller or a processor changes who notifies whom: a processor must notify its controller without undue delay, and the controller notifies the authority.

Q
A customer requires PCI-DSS compliance. What's the first thing you do to scope it?
Model answer

Define the cardholder data environment — identify everywhere card data is stored, processed, or transmitted, and everything connected to it, because PCI scope is all of that plus connected systems. The single most valuable move is to minimize scope: the less of your environment that touches card data, the smaller and cheaper the assessment, so I'd look at whether we can avoid handling card data at all by outsourcing to a compliant payment processor and tokenization, keeping raw PANs out of our systems entirely. Then segment the network so the cardholder data environment is isolated from the rest, which keeps unrelated systems out of scope. So the first step is data-flow mapping to establish scope, immediately followed by scope reduction through outsourcing and segmentation, before assessing controls against the twelve requirements.

Q
How does NIST CSF relate to NIST 800-53?
Model answer

They operate at different altitudes. The Cybersecurity Framework is the high-level, voluntary, outcome-oriented model organized around its core functions — Govern, Identify, Protect, Detect, Respond, Recover — and it's meant to be readable by executives and applicable to any organization. NIST 800-53 is the detailed control catalog: hundreds of specific security and privacy controls used for US federal systems and underpinning FedRAMP. So CSF tells you what outcomes to aim for and gives a common language for risk, while 800-53 provides the specific controls you implement to achieve them — CSF even maps its subcategories to 800-53 controls. In short, CSF is the strategic framework, 800-53 is the implementation control set it can reference.

Q
What's a DPIA and when is it required?
Model answer

A Data Protection Impact Assessment is a GDPR process for evaluating and mitigating the privacy risks of a processing activity before you start it. It's required when processing is likely to result in a high risk to individuals' rights and freedoms — for example large-scale processing of special-category data, systematic monitoring of public areas, or extensive profiling and automated decision-making with significant effects. The DPIA documents the processing, assesses necessity and proportionality, identifies risks to data subjects, and defines mitigations; if significant residual risk remains, you must consult the supervisory authority before proceeding. Practically it's how privacy-by-design becomes concrete — you do the risk analysis up front rather than after a regulator asks. For an engineer it often means being pulled in to describe data flows and the technical safeguards.

Q
Your cloud product needs FedRAMP Moderate. Roughly how does that process work?
Model answer

FedRAMP is the standardized authorization for cloud services used by US federal agencies, built on NIST 800-53 controls, with Low, Moderate, and High baselines — Moderate being the common one, covering a few hundred controls. The path: you implement the Moderate control baseline, document everything in a System Security Plan, and engage an accredited third-party assessor, a 3PAO, to independently test the controls and produce a security assessment report. Then you pursue an authorization either through a sponsoring agency that grants an Authority to Operate, or via the FedRAMP program office. After authorization, it's not done — there's continuous monitoring, with ongoing scanning, monthly reporting, and annual assessments. It's a heavy, months-to-over-a-year effort, which is why teams plan for the documentation and continuous-monitoring burden, not just the initial control implementation.