Compliance chain
Every legal requirement traces to a policy, a control and proof
Regulations drive policies, standards and procedures; controls do the work and evidence proves it.
Follow one requirement from law to proof. The GDPR says to protect personal data with appropriate measures, including encryption. The company’s policy, approved by the board, says: personal data is encrypted at rest and in transit. A standard makes it specific: AES-256 on laptops, TLS 1.2 or higher on services. A procedure says how: enrol every laptop in device management. The control does it: MDM enforces encryption and blocks devices that are not. And evidence proves it: one thousand one hundred and ninety-eight of twelve hundred laptops encrypted, two exceptions, both ticketed.
Governance documents · Going deeper
Policies, standards, procedures and guidelines, and who owns them
A policy states intent, a standard sets mandatory specifics, a procedure gives steps, a guideline advises.
A policy states intent, a standard sets mandatory specifics, a procedure gives steps, a guideline advises. Policy high-level, mandatory statement of intent, approved by senior management. Changes rarely. Examples: acceptable use, information security, data retention. Standard mandatory specifics that make a policy measurable: algorithms, password length, patch deadlines. Procedure step-by-step instructions for a task, such as onboarding a user or responding to phishing. Guideline recommended practice, not mandatory, where judgement is needed. Baseline a minimum secure configuration for a type of system. Who governs. Common policies also include acceptable use, change management, access control, incident response, business continuity and the software development lifecycle. Each is reviewed on a schedule and when the business changes.
- Policy high-level, mandatory statement of intent, approved by senior management. Changes rarely. Examples: acceptable use, information security, data retention.
- Standard mandatory specifics that make a policy measurable: algorithms, password length, patch deadlines.
- Procedure step-by-step instructions for a task, such as onboarding a user or responding to phishing.
- Guideline recommended practice, not mandatory, where judgement is needed.
- Baseline a minimum secure configuration for a type of system.
Who governs
Common policies also include acceptable use, change management, access control, incident response, business continuity and the software development lifecycle. Each is reviewed on a schedule and when the business changes.
NIST CSF 2.0
NIST CSF 2.0 puts Govern at the centre of security
The NIST Cybersecurity Framework 2.0 (2024) has six functions: Govern, Identify, Protect, Detect, Respond, Recover.
The most widely used framework is NIST’s Cybersecurity Framework. Version two, from 2024, added a sixth function at the centre: Govern. Strategy, roles, policy, risk appetite and supply-chain risk. Security as a business decision. Around it, the cycle: identify your assets and risks, protect them, detect attacks, respond to incidents, recover from them, and feed the lessons back in. It describes outcomes, not products, so any organisation can measure itself against it.
Using a framework · Going deeper
Profiles, tiers, and the other frameworks you will meet
CSF profiles and tiers; also know ISO 27001, NIST SP 800-53, CIS Controls, COBIT and SOC 2.
CSF profiles and tiers; also know ISO 27001, NIST SP 800-53, CIS Controls, COBIT and SOC 2. How CSF is used. Write a current profile (what you achieve today), a target profile (what you need), and a plan for the gap. Tiers 1 to 4 (partial, risk informed, repeatable, adaptive) describe how mature the practice is. Other frameworks. ISO/IEC 27001 certifiable management system, international. NIST SP 800-53 a large control catalogue, required for US federal systems. NIST Risk Management Framework categorise, select, implement, assess, authorise, monitor. CIS Controls 18 prioritised, practical safeguards; a common starting point. COBIT IT governance and management. Cloud Security Alliance CCM controls for cloud services.
How CSF is used
Write a current profile (what you achieve today), a target profile (what you need), and a plan for the gap. Tiers 1 to 4 (partial, risk informed, repeatable, adaptive) describe how mature the practice is.
Other frameworks
- ISO/IEC 27001 certifiable management system, international.
- NIST SP 800-53 a large control catalogue, required for US federal systems.
- NIST Risk Management Framework categorise, select, implement, assess, authorise, monitor.
- CIS Controls 18 prioritised, practical safeguards; a common starting point.
- COBIT IT governance and management.
- Cloud Security Alliance CCM controls for cloud services.
ISO 27001
ISO 27001 certifies a system that keeps improving
ISO 27001 certifies an ISMS; its Annex A has 93 controls in 4 themes, chosen in a Statement of Applicability.
ISO 27001 is the international standard companies get certified against. At its heart is a management system that runs in a cycle: plan, by setting scope and assessing risk; do, by running controls; check, by monitoring and auditing; act, by fixing and improving. Annex A lists ninety-three controls in four themes: thirty-seven organisational, eight about people, fourteen physical and thirty-four technological. You choose which apply, and justify it in a Statement of Applicability.
Regulations
Which rules apply depends on whose data you hold and where
Know GDPR, NIS2, PCI DSS, HIPAA and SOX: who they cover and what failing costs.
Different rules cover different data. The GDPR covers personal data of people in the EU, with fines up to twenty million euros or four percent of global turnover. NIS2 covers essential and important services in the EU. PCI DSS covers anyone handling payment cards. HIPAA covers US healthcare data. And Sarbanes-Oxley makes executives of US public companies personally certify their financial controls. PCI DSS is technically a contract with the card brands, not a law. In practice, the effect is the same.
Privacy · Going deeper
Privacy principles, data subject rights and the roles behind them
Know data subject rights, privacy by design, the DPO, DPIAs and cross-border transfers.
Know data subject rights, privacy by design, the DPO, DPIAs and cross-border transfers. GDPR principles. Lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; accountability. Rights of the data subject. Data protection officer (DPO) required for some organisations; advises and monitors compliance independently. Data protection impact assessment (DPIA) required before high-risk processing. Privacy by design and by default collect the minimum and protect it from the start. International transfers personal data leaves the EU only with safeguards, such as an adequacy decision or standard contractual clauses.
GDPR principles
Lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; accountability.
Rights of the data subject
- Data protection officer (DPO) required for some organisations; advises and monitors compliance independently.
- Data protection impact assessment (DPIA) required before high-risk processing.
- Privacy by design and by default collect the minimum and protect it from the start.
- International transfers personal data leaves the EU only with safeguards, such as an adequacy decision or standard contractual clauses.
Residual risk
Controls shrink a risk; what is left is accepted on the record
Inherent risk minus the effect of controls is residual risk, compared with the risk appetite.
Back to risk, now with controls in place. Ransomware stopping the file servers: likely, four, and severe, five. Inherent risk twenty. The company adds MFA, EDR, segmentation and immutable backups. Now it is unlikely, two, and moderate, three, because backups restore quickly. Residual risk six. The board’s risk appetite is eight. So the risk owner formally accepts the remaining six, and it is reviewed every year.
Third-party risk
You can outsource the work, but not the responsibility
Third-party risk management: due diligence, contracts, onboarding, monitoring and offboarding of suppliers.
Your data lives with your suppliers too. Before signing, do due diligence: a security questionnaire, and their SOC 2 report or ISO certificate. Write security into the contract: breach notification, the right to audit. Give them only the access they need. Reassess them every year, and watch for incidents. And at the end, revoke access and get the data back or destroyed. Why it matters: in 2023, one flaw in the MOVEit file-transfer product reached two thousand seven hundred organisations and nearly a hundred million people, many through suppliers of suppliers.
Agreements · Going deeper
SLA, MSA, SOW, NDA, MOU and BPA
Know the agreement types: SLA, MSA, SOW, NDA, MOU and BPA.
Know the agreement types: SLA, MSA, SOW, NDA, MOU and BPA. Service level agreement (SLA) measurable service commitments, such as 99.9% availability or a four-hour response, with remedies. Master service agreement (MSA) the overall terms for a long relationship, with individual work added under it. Statement of work (SOW) the specific deliverables, timeline and price for one piece of work. Non-disclosure agreement (NDA) keeps shared information confidential. Memorandum of understanding (MOU) a statement of intent between parties, usually not legally binding. Business partners agreement (BPA) how partners share profits, decisions and responsibilities. Rules of engagement for testers and incident partners: what they may do, and when.
- Service level agreement (SLA) measurable service commitments, such as 99.9% availability or a four-hour response, with remedies.
- Master service agreement (MSA) the overall terms for a long relationship, with individual work added under it.
- Statement of work (SOW) the specific deliverables, timeline and price for one piece of work.
- Non-disclosure agreement (NDA) keeps shared information confidential.
- Memorandum of understanding (MOU) a statement of intent between parties, usually not legally binding.
- Business partners agreement (BPA) how partners share profits, decisions and responsibilities.
- Rules of engagement for testers and incident partners: what they may do, and when.
Audits and attestation
Type I shows good design on a day; Type II proves it worked all year
SOC 2 Type I assesses control design at a point in time; Type II tests operating effectiveness over a period.
How do you trust a supplier’s controls without auditing them yourself? Independent reports. A SOC 2 Type I report looks at one date: on the thirtieth of June, were the controls designed well? A Type II covers a period, here twelve months: did the controls actually work, every time the auditor tested? That is the one to ask for. Alongside it: ISO certificates, internal audit reporting to the board, and self-assessments. What makes any of them trustworthy is independence.
Lesson complete
You finished “Governance, risk and compliance”
Nicely done.