Compliance chain

Every legal requirement traces to a policy, a control and proof

RegulationGDPR Art. 32: “appropriate technical and organisational measures”, including encryptionPolicy“Personal data is encrypted at rest and in transit.” Approved by the board.StandardLaptops: AES-256 full-disk encryption. Services: TLS 1.2 or higher.ProcedureEnrol each laptop in MDM; the encryption profile applies at first sign-in.ControlMDM enforces encryption and blocks unencrypted devices from company email.EvidenceMonthly MDM report: 1,198 of 1,200 laptops encrypted; 2 exceptions, both ticketed.Compliance is a chain: every legal requirement traces to a policy, a control, and evidence that it works.A regulation says what must be achieved. Policies state the company’s intent; standards and procedures make itspecific; controls do the work; evidence proves it to an auditor. Break any link and the requirement is not met,however good the policy sounds.

Regulations drive policies, standards and procedures; controls do the work and evidence proves it.

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.

  • 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

Boardsets risk appetite, oversees
CISOruns the security programme
Ownersaccountable for data and systems
Committeessteering groups, change boards

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

IdentifyProtectDetectRespondRecoverGovernGovern (GV), new in 2.0strategy, roles, policy, risk appetite, supply-chain riskIdentify (ID)assets, risks, and how to improveProtect (PR)identity and access, training, data and platform securityDetect (DE)continuous monitoring and analysis of eventsRespond (RS)manage, analyse, communicate and contain incidentsRecover (RC)restore systems and communicate during recoveryNIST CSF 2.0 puts Govern at the centre: security is run as a business risk, not an IT project.The framework describes outcomes, not products: what a mature programme achieves in each function. Companies useit to profile where they are, set a target, and plan the gap. Version 2.0 (2024) added Govern and widened theaudience from critical infrastructure to every organisation.

The NIST Cybersecurity Framework 2.0 (2024) has six functions: Govern, Identify, Protect, Detect, Respond, Recover.

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.

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

The ISMS: a management cyclePlanset scope, assess riskDorun the controlsCheckmonitor, auditActfix and improveAnnex A: 93 controls in 4 themes (to scale)Organisational37People8Physical14Technological34Chosen and justified in a Statement of ApplicabilityISO 27001 certifies a management system that keeps improving, not a fixed checklist of controls.Clauses 4 to 10 are mandatory: scope, leadership, risk assessment, operation, measurement, improvement. The 93Annex A controls (2022 edition) are applied where risk calls for them. Certification lasts three years, withsurveillance audits in between. ISO 27002 explains each control in detail.

ISO 27001 certifies an ISMS; its Annex A has 93 controls in 4 themes, chosen in a Statement of Applicability.

Regulations

Which rules apply depends on whose data you hold and where

RuleApplies toMain demandsIf you failGDPRpersonal data of people in the EUlawful basis, rights, 72-hour breach noticeup to €20M or 4% of global turnoverNIS2essential and important EU entitiesrisk measures, 24-hour early warningup to €10M or 2% (essential)PCI DSS 4.0.1anyone handling payment card data12 requirements, yearly assessmentcard-brand fines, loss of card paymentsHIPAAUS healthcare and its business associatessafeguard health informationtiered civil fines; criminal for misuseSOXUS public companiescontrols over financial reportingexecutives certify personally; prison for fraudPCI DSS is a contract with the card brands, not a law, but the effect is much the same.Which rules apply depends on whose data you hold, where they live and what industry you are in.Most companies face several at once, so controls are mapped once and reused as evidence for each. Regulators lookat whether protection was appropriate to the risk, and whether you can show it; fines scale with turnover.

Know GDPR, NIS2, PCI DSS, HIPAA and SOX: who they cover and what failing costs.

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.

GDPR principles

Lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; accountability.

Rights of the data subject

Accesssee the data held about you
Rectificationcorrect it
Erasurethe right to be forgotten
Portabilitytake it elsewhere
  • 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

Risk: ransomware stops the file servers (likelihood × impact, 1 to 5 each)Inherent risk4 likely × 5 severe = 2020↓ controls: MFA, EDR, segmentation, immutable backupsResidual risk2 unlikely × 3 moderate = 66risk appetite: 8Residual 6 is within the appetite of 8: the risk owner formally accepts it, and it is reviewed every year.Controls turn inherent risk into residual risk; what remains is accepted against the appetite, on the record.Inherent risk is the exposure before any controls. Residual risk is what is left after them, and is never zero.If it is still above the appetite, add controls, transfer it or avoid the activity. The risk register records theowner, the decision and the review date, so acceptance is a decision, not an accident.

Inherent risk minus the effect of controls is residual risk, compared with the risk appetite.

Third-party risk

You can outsource the work, but not the responsibility

Due diligencequestionnaire, SOC 2report or ISO certificateContractsecurity terms, breachnotice, right to auditOnboardleast access,named contactsMonitorreassess yearly,watch for incidentsOffboardrevoke access, returnor destroy the dataMOVEit, 2023: one flaw in one file-transfer product reached 2,773 organisationsand about 96 million people, many through suppliers and suppliers’ suppliers (Emsisoft).You can outsource the work, but not the responsibility: a vendor’s breach is still your breach.Third-party risk management vets suppliers before signing, writes security into contracts, limits their access,reassesses them over time and removes access at the end. The most critical suppliers get the closest scrutiny;regulations such as NIS2 and DORA now require supply-chain risk management outright.

Third-party risk management: due diligence, contracts, onboarding, monitoring and offboarding of suppliers.

Agreements · Going deeper

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.

Audits and attestation

Type I shows good design on a day; Type II proves it worked all year

JanFebMarAprMayJunJulAugSepOctNovDecSOC 2 Type Ias of 30 June: are the controls designed well?SOC 2 Type IIover 12 months: did the controls actually work, every time the auditor tested?Also: an ISO 27001 certificate (the management system meets the standard), internal audit reporting to the board,and self-assessments. Independence is what makes an audit worth trusting.A Type I report says the controls were designed well on one day; a Type II proves they worked over months.SOC 2 reports are independent auditors’ opinions on a service provider’s controls against the Trust ServicesCriteria: security, plus optionally availability, processing integrity, confidentiality and privacy. When choosinga supplier, ask for the Type II, check its period and scope, and read the exceptions.

SOC 2 Type I assesses control design at a point in time; Type II tests operating effectiveness over a period.

Lesson complete

You finished “Governance, risk and compliance”

Nicely done.

Open in a new tab