Lesson 1: What compliance actually is
You will be able to: explain compliance as meeting applicable obligations, and use the four-layer model to judge whether a control actually operates.
About 5 min
Compliance means meeting the obligations that apply to your organization. Those obligations come from four places: laws and regulations, contracts with customers and suppliers, standards the organization has adopted or agreed to, and its own internal policies.
Organizations meet obligations through controls: safeguards and practices that reduce a risk or keep it at a level the organization has accepted. A control is not a document. It is something that happens, repeatedly, and can be shown to have happened.
This course uses one model throughout. A control that actually works has four layers, and each layer leaves evidence: records that show what happened.
01 · policy · in practice
Access to production must match job responsibilities.
Evidence it leaves
The approved policy, with its owner and review date.
record access-control-policy.md · v4 · owner: security · next review 2027-01
Exercise 1 of 2: Sort the artifacts
These five artifacts all relate to one control: access to production. Place each one in the layer it belongs to, or in Evidence if it is a record that a layer operated.
- Policy
- The rule and its intent
- Procedure
- Who does what, when, and how
- Implementation
- The mechanism that enforces it
- Management
- Ownership, review, exceptions, correction
- Evidence
- A record that something happened
- 01
Access Control Policy, section 4.2
“Access to production systems is limited to personnel whose job responsibilities require it.”
- Type
- Document
- Owner
- Security
- 02
Runbook: requesting production access
Open an access request ticket → your manager approves → the platform team assigns the time-limited role → access expires after 8 hours.
- Type
- Wiki page
- Owner
- Platform
- 03
Role definition: prod-readonly
session_duration: 8h·requires: sso + phishing-resistant MFA·assignable_by: platform-admins- Type
- Infrastructure as code
- Repo
- infra/iam
- 04
Quarterly access review: standing assignment
The platform lead reviews every production account each quarter. Exceptions are recorded with an expiry date. Findings are tracked until closed.
- Type
- Recurring task
- Owner
- Platform lead
- 05
Q3 access review export
42 accounts reviewed · 2 revoked (tickets OPS-3121, OPS-3122) · signed off by the platform lead on 3 October
- Type
- CSV export + sign-off
- Date
- 3 Oct
Apply it 2 of 2: Repair a control
A team describes its change control like this: “Policy: all production code changes are peer reviewed. Procedure: engineers open a pull request and a teammate approves it before merging.” The repository does not require approvals before merging, and nobody is assigned to check that the process is followed.
Which gaps would stop this team from showing that the control operates? Select all that apply.
Key points
- Compliance means meeting the obligations that apply: laws and regulations, contracts, adopted standards, and internal policies.
- A control is something that happens and can be shown to have happened, not a document.
- Four layers: policy, procedure, implementation, management. Evidence records each one operating.
- Assessors test design and operating effectiveness. A policy alone shows neither.