CISSP Domain 1 Cheat Sheet: Security and Risk Management Revision Notes
Quick Insights:
CISSP Domain 1, Security and Risk Management, is the largest domain on the exam at about 16%, and it shapes how you answer questions in the other seven. These notes cover the manager’s mindset, the CIA triad, the ISC2 Code of Ethics canon order, governance, due care vs due diligence, policies and standards, legal and privacy rules (including GDPR and India’s DPDP Act), investigations, and risk management with the SLE, ALE and ARO formulas. They also cover threat modeling, supply chain risk, business continuity (BIA, RTO, RPO, MTD), personnel security and awareness training. Use the exam alerts, the confused-pairs table and the formulas box for fast last-minute revision.
CISSP DOMAIN 1: Security and Risk ManagementÂ
Comprehensive Last-Minute Revision NotesÂ
Aligned to the current ISC² CISSP Common Body of KnowledgeÂ
Exam weight: ~16% – the single largest domain on the examÂ
Edition: October 2026Â
How to use this?
Domain 1 carries more marks than any other part of the CISSP exam, and it quietly sets the rules for the whole paper. Master the mindset here and the other seven domains get easier, because almost every scenario question is, underneath, a risk-management question dressed up in a different domain’s vocabulary.Â
One idea runs through everything: the exam is testing a manager, not a firewall administrator. ISC² wants to see that you can weigh business impact, protect people, and choose the response a prudent security leader would choose. The most technically clever answer is usually a trap.Â
I’ve walked the domain in the order it tends to make sense to a human, not the order ISC² numbered the objectives. Read it end to end a few days out, then the night before, skim three things only: the Exam Alert boxes, the commonly confused pairs table near the end, and the formulas box. That’s your cram layer.Â
MANAGER’S LENS: Throughout, watch the qualifier word in the stem: BEST, FIRST, MOST, PRIMARY, GREATEST, LEAST. Two options are often both ‘correct’; the qualifier decides which one wins. Reading past that word is the most common way strong candidates lose marks they should keep.Â
1. Think like a manager: the CISSP mindset
Before any content, internalise the altitude ISC² expects. You are advising the business, not patching a box. That shapes how you read every scenario:Â
- Protect human life and safety first; always: If any option preserves life or safety, it outranks protecting data, systems, or money. This is the one rule that breaks every tie.Â
- Think risk, not fear: You do not chase every threat. You weigh likelihood against impact and spend proportionately. Security exists to let the business take risks intelligently, not to say no.Â
- Go top-down: Effective security is driven and owned by senior management; the ‘tone at the top’. A programme pushed up from IT without executive sponsorship is a classic wrong answer.Â
- Prefer the managerial action over the technical one: When the exam offers ‘reconfigure the firewall’ next to ‘update the policy and get management approval’, the governance answer is usually what’s being tested.Â
- Address root cause, not symptoms: The BEST answer fixes why the problem happened; a quick patch that leaves the cause in place is a distractor.Â
EXAM ALERT: If a question looks like it has two right answers, re-read for the qualifier and ask: which option a prudent manager would do FIRST, or which BEST serves the business while protecting people? Technical depth rarely wins these.
2. Core security concepts
Everything in security traces back to preserving a handful of properties. The famous three are the CIA triad:Â
- Confidentiality: Keeping information from those who shouldn’t see it. Supported by encryption, access controls, classification, need-to-know. The opposing harm is disclosure.Â
- Integrity: Keeping information accurate, complete, and unaltered except by authorised change. Supported by hashing, digital signatures, change control, input validation. The opposing harm is alteration.Â
- Availability: Making sure information and systems are there when legitimate users need them. Supported by redundancy, backups, failover, capacity planning, DDoS protection. The opposing harm is destruction (or denial).Â
The mirror image of the CIA is the DAD triad. It stands for Disclosure, Alteration, Destruction which is simply what an attacker is trying to cause.Â
| Property | What it protects | Typical controls | If it fails |
| Confidentiality | Secrecy of data | Encryption, access control,Â
classification |
Disclosure / data leak |
| Integrity | Accuracy & trust in data | Hashing, signatures, change control | Alteration /Â
corruption |
| Availability | Access when needed | Redundancy, backups, failover | Destruction / outage |
Modern CBK thinking extends the triad with two more properties you should be able to recognise:Â
- Authenticity: The data or identity is genuine and from the claimed source.Â
- Non-repudiation: A party cannot credibly deny an action they took. Delivered through digital signatures and strong logging; underpins accountability.Â
You’ll also see the access-management chain written as IAAA:Â
- Identification (claiming an identity),
- Authentication (proving it),
- Authorization (what you’re allowed to do), andÂ
- Accounting / Auditing (recording what you did).Â
Keep these four distinct. The exam loves to swap authentication and authorization.Â
Finally, two design ideas worth a line each. Defence in depth means layering controls so no single failure is fatal. Least privilege and need-to-know (covered properly under personnel security) keep access minimal by default.Â
EXAM ALERT: Hashing proves integrity, not confidentiality. Encryption protects confidentiality, not (by itself) integrity. If a stem talks about proving a file wasn’t changed, the answer involves a hash or digital signature; not encryption.Â
3. Professional ethics
ISC² takes ethics seriously enough that you sign the (ISC)² Code of Ethics as a condition of certification. For the exam, the part that actually earns marks is the order of the four canons, because that order resolves conflicts.Â
The canons, in priority sequence:Â
- Protect society, the common good, necessary public trust and confidence, and the infrastructure.Â
- Act honourably, honestly, justly, responsibly, and legally.Â
- Provide diligent and competent service to principals (your employer or client).Â
- Advance and protect the profession.Â
Sequence is everything. When two canons pull against each other, the lower-numbered canon wins. Your duty to the public outranks your duty to your employer, which outranks your duty to the profession’s image.Â
MEMORY HOOK: Read the canons as a chain of loyalty, outward to inward:Â
Public → Honour → Principal → Profession
When an ethics question stumps you, choose the answer that protects the public and preserves trust, even if it embarrasses your employer.Â
MANAGER’S LENS: Organisations also have their own code of ethics, and you’re expected to uphold both. If an employer’s instruction conflicts with the (ISC)² Code or the law, the Code and the law win; quietly doing the right thing, not blindly following orders, is the examinable instinct.Â
EXAM ALERT: Ethics scenarios are rarely about exotic dilemmas. They’re about priority. Spot the conflict, then apply the order. Public safety and trust beat personal gain, employer convenience, and reputation management every time.
TRAINING CALENDAR of Upcoming Batches For CISSP Training
| Start Date | End Date | Start - End Time | Batch Type | Training Mode | Batch Status | |
|---|---|---|---|---|---|---|
| 07-Dec-2026 | 25-Dec-2026 | 07:00 - 12:00 IST | Weekday | Online | [ Close ] | |
| 12-Dec-2026 | 24-Jan-2027 | 10:00 - 14:00 IST | Weekend | Online | [ Open ] | |
| 09-Jan-2027 | 14-Feb-2027 | 19:00 - 23:00 IST | Weekend | Online | [ Open ] | |
| 13-Feb-2027 | 21-Mar-2027 | 09:00 - 13:00 IST | Weekend | Online | [ Open ] | |
| 13-Mar-2027 | 18-Apr-2027 | 19:00 - 23:00 IST | Weekend | Online | [ Open ] |
4. Security governance
Governance is the system by which the organisation directs and controls security. The clean distinction the exam wants: governance sets direction and holds accountability; management executes within that direction. The board governs; the CISO and teams manage.Â
Security has to align with business strategy, goals, mission, and objectives. A control that frustrates the business without a proportionate risk reduction is the wrong answer, however secure it looks. Security is a business enabler, measured by how well it supports value, not by how many things it blocks.Â
Due care vs. due diligenceÂ
These two trip up nearly everyone, so lock them down. Due diligence is doing the homework: investigating, assessing, and understanding your risks and obligations. Due care is doing something about it: taking the reasonable, prudent actions a careful organisation would take once it knows. Diligence is the research; care is the action.Â
The yardstick is the prudent person rule: would a reasonable, careful person in the same role have acted the same way? Failing to exercise due care is negligence, and negligence is where legal liability lives: including downstream liability, where your weakness harms someone else.Â
MEMORY HOOK: Due diligenCE = COLLECT information. Due Care = take Corrective aCtion. Research first, then act.Â
Roles and responsibilities
| Role | Owns / does |
| Senior management | Ultimately accountable and legally liable; sets tone, funds the programme, accepts residual risk |
| Data / information owner | A business leader; classifies data and defines protection and access requirements |
| Data custodian | Usually IT; implements and maintains the controls the owner specifies (backups, patching) |
| Data steward | Responsible for data quality, context, and business meaning |
| System owner | Accountable for a specific system and its security posture |
| Security professional / ISSOÂ | Designs, implements, and advises on controls; functional responsibility |
| User | Follows policy and acceptable use; least privilege and need-to-know apply |
| Auditor | Independently evaluates whether controls are effective and compliant |
| Data controller (privacy)Â | Determines the purpose and means of processing personal data |
| Data processor (privacy)Â | Processes personal data strictly on the controller’s instructions |
Two patterns the exam rewards: the owner sets, the custodian maintains (accountability vs. implementation), and accountability cannot be delegated even when the task is.Â
Control frameworks: Know what each is forÂ
You won’t be asked to recite them, but you must pick the right tool for the job:Â
- ISO/IEC 27001: the certifiable standard for an Information Security Management System (ISMS).
- ISO/IEC 27002: the companion catalogue of control guidance.Â
- NIST Cybersecurity Framework (CSF): a voluntary, outcome-based framework. Core functions:
Identify, Protect, Detect, Respond, Recover and Govern, added in CSF 2.0 (2024).Â
- NIST SP 800-53: the detailed control catalogue for US federal systems. NIST RMF (SP 800-37): the process for applying and authorising those controls.Â
- COBIT: governance and management of enterprise IT (ISACA). Think board-level IT governance, not an ISMS.Â
- SABSA / Zachman: enterprise security and enterprise architecture frameworks. ITIL: IT service management. COSO: enterprise and financial governance / internal control.Â
- PCI DSS: a contractual standard for protecting cardholder data; enforced by the card brands, not by law.Â
EXAM ALERT: Match framework to purpose:Â
certify the ISMS → ISO 27001;Â
govern enterprise IT → COBIT;
structure security architecture → SABSA;Â
manage federal risk end-to-end → RMF.Â
Confusing ‘governance framework’ with ‘control catalogue’ is a reliable distractor.
5. Policies, standards, procedures, baselines, guidelines
This is the documentation hierarchy, from the broad statement of intent down to the step-by-step. Get the mandatory-versus-optional distinction right and most questions here answer themselves.Â
| Document | Nature | What it is |
| Policy | Mandatory | High-level management intent and direction; the ‘why’. Broad and slow to change. |
| Standard | Mandatory | Specific, uniform requirements. E.g., ‘all laptops use AES-256 full-disk encryption’. |
| Baseline | Mandatory | A minimum, consistent level of security / configuration to meet a standard. |
| Procedure | Mandatory | Detailed, step-by-step instructions; the ‘how’. |
| Guideline | Discretionary | Recommended best practice; advisory, not required; the only optional one. |
Policies themselves come in flavours you should recognise:Â
an organisational (master) policy, issue-specific policies (e.g., acceptable use, email), and system-specific policies.Â
By tone they can be regulatory (driven by law), advisory (strongly recommended, most common), or informative (educational).Â
EXAM ALERT: Guidelines are the sole discretionary item in the hierarchy. If a stem hinges on ‘which of these is a recommendation rather than a requirement’, it’s the guideline. Everything else: policy, standard, baseline, procedure is mandatory.Â
6. Compliance, legal, and regulatory issues
CISSP is international, so you’re tested on concepts and categories rather than any one country’s statute. Know the shapes.Â
Categories of lawÂ
| Type | Protects / governs | Standard of proof | Outcome |
| Criminal | Society; serious wrongs | Beyond a reasonable doubt | Imprisonment, fines |
| Civil (tort) | Disputes between parties | Preponderance of the evidence | Monetary damages |
| Administrative / regulatory | Agency rules & industry conduct | More likely than not (lenient) | Fines, sanctions |
Legal systems differ too:Â
common law (precedent-based, e.g., US/UK/India),Â
civil / code law (written codes, much of Europe),Â
plus religious and customary systems.Â
You mainly need to recognise the difference, not practice it.Â
Intellectual propertyÂ
| Protection | Covers | Rough life |
| Patent | A novel, useful invention (public disclosure in exchange for exclusivity) | ~20 years from filing |
| Copyright | The expression of an idea fixed in tangible form; including software code | Author’s life + 70 years |
| Trademark | A brand identifier: name, logo, slogan, mark | Indefinite if used & defended |
| Trade secret | Confidential business information (formula, process) protected by secrecy | As long as it stays secret |
Quick reflexes the exam expects: software → copyright; a secret recipe or algorithm kept confidential → trade secret; a brand name or logo → trademark; a patentable invention → patent (but filing discloses it publicly). Related: licensing models; freeware, shareware, commercial, academic, governed by the EULA.Â
Cross-border and export issuesÂ
- Import/export controls: Notably on strong encryption (e.g., the Wassenaar Arrangement, US EAR/ITAR). Shipping crypto across borders can be regulated.Â
- Transborder data flows & data sovereignty: Personal data is subject to the laws of the jurisdictions it touches; some data must stay in-country.Â
PrivacyÂ
Privacy is the fastest-moving area, and it’s where governance meets law. The reference model most frameworks echo is the set of Fair Information Practices / OECD principles: collection limitation, purpose specification, use limitation, data quality, security, openness, individual participation, and accountability.Â
GDPR (EU) is the benchmark and the one most likely to surface. Key points: it’s extraterritorial (applies to anyone handling EU residents’ data), requires a lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interests), grants data-subject rights (access, rectification, erasure/’right to be forgotten’, portability, objection), mandates breach notification to the supervisory authority within 72 hours, may require a Data Protection Officer (DPO), and carries fines up to €20 million or 4% of global annual turnover, whichever is higher. The actors are the controller (decides purpose and means) and the processor (acts on the controller’s instructions).Â
MANAGER’S LENS: For our Indian readers, the local analogue is the Digital Personal Data Protection (DPDP) Act, 2023, with its Rules operationalising it. It renames the familiar roles, Data Principal (the individual), Data Fiduciary (the controller), Data Processor, introduces a Consent Manager and the Data Protection Board of India, and sets penalties that can reach ₹250 crore per instance. The exam tests GDPR-style concepts; knowing the DPDP mapping is for your real job and your clients.Â
US privacy is sectoral, not one law: HIPAA (health), GLBA (financial), CCPA/CPRA (California consumers), COPPA (children), FERPA (education). And remember PCI DSS is contractual, not legislation.Â
EXAM ALERT: Controller vs. processor is a favourite. The controller determines the ‘why and how’ of processing and carries primary accountability; the processor only does what it’s told. Outsourcing processing never outsources the controller’s accountability.
7. Investigations and evidence
Different investigations answer to different masters, which changes the bar for proof and how carefully you must handle evidence.Â
- Administrative: internal, into a policy or HR matter. Lowest bar; operational focus.Â
- Civil: a dispute between parties; proof on the preponderance of the evidence.Â
- Criminal: involves law enforcement; proof beyond a reasonable doubt; strictest handling.Â
- Regulatory: conducted by or for an oversight body against its rules.Â
EvidenceÂ
Evidence types include real (physical), documentary (records, logs), testimonial (witness), and demonstrative (models, diagrams that explain). To be useful in court, evidence must be relevant, reliable/competent, and legally permissible that is admissible.Â
Two rules worth knowing: the best evidence rule prefers the original document over a copy, and the hearsay rule generally excludes second-hand statements; with a key exception for routine business records (logs kept in the ordinary course of business).Â
Above all, protect the chain of custody: a documented, unbroken record of who collected, handled, stored, and transferred each item, and when. Break the chain and even damning evidence can be thrown out. Collect in order of volatility (most perishable data first, e.g., memory before disk) and keep everything forensically sound.Â
EXAM ALERT: Chain of custody is about the integrity and admissibility of evidence, not its content. If a scenario hinges on whether evidence will ‘hold up in court’, the issue is almost always a gap in the chain of custody or a failure to preserve the original.Â
8. Risk management concepts
This is the beating heart of Domain 1 and, honestly, of the exam. Precision with the vocabulary is half the battle.Â
| Term | Meaning |
| Asset | Anything of value you’re protecting like data, systems, people, reputation |
| Threat | A potential cause of harm (ransomware, flood, insider) |
| Threat agent / actor | The entity that carries out or triggers a threat |
| Vulnerability | A weakness a threat can exploit (unpatched server, weak process) |
| Exposure | An instance of being susceptible to loss from a threat |
| Risk | The likelihood a threat exploits a vulnerability × the resulting impact |
| Control / safeguard / countermeasure | What you put in place to reduce risk |
| Inherent risk | Risk before any controls are applied |
| Residual risk | Risk that remains after controls. You can never reach zero |
| Secondary risk | A new risk introduced by the control you added |
The flow is:Â
Identify assets and risks → assess/analyse → respond → monitor, then repeat.Â
Analysis comes in two styles, usually blended:Â
- Qualitative: subjective ratings (high/medium/low), scenarios, and expert judgement (e.g., the Delphi technique for anonymous consensus). Fast and cheap; no hard numbers.Â
- Quantitative: money and probabilities. Objective and powerful for cost-benefit, but data-hungry and time-consuming. Pure quantitative is rare; most real programmes are hybrid.Â
The quantitative formulas (memorise these)Â
- SLE (Single Loss Expectancy) = AV × EF
Asset Value × Exposure Factor (the % of the asset lost in one event). - ALE (Annualised Loss Expectancy) = SLE × AROÂ
- Single Loss × Annualised Rate of Occurrence (events per year).Â
- Safeguard value = (ALE before − ALE after)
Annual Cost of the safeguard. Positive means the control pays for itself.Â
WORKED EXAMPLE: A customer database is valued at 100,000. A ransomware hit would cost you about 60% of that, so EF = 0.6 and SLE = 100,000 × 0.6 = 60,000. You expect such a hit roughly once every two years, so ARO = 0.5 and ALE = 60,000 × 0.5 = 30,000 per year. You consider EDR plus immutable backups at 10,000 per year, which drops the frequency to about once every ten years (ARO = 0.1), so the new ALE = 60,000 × 0.1 = 6,000. Safeguard value = (30,000 − 6,000) − 10,000 = 14,000 saved per year; clearly worth doing. Flip the control’s price to 30,000 per year and the maths turns negative; you’d need a non-financial reason (regulation, reputation) to justify it.Â
From that example comes an iron rule: never spend more on a control than the asset is worth, or more than the risk it removes. Over-controlling is its own failure.Â
Risk responses (the four T’s)Â
- Terminate / avoid: stop doing the risky activity altogether.Â
- Transfer / share: shift the financial impact to a third party (insurance, outsourcing with contractual liability). The activity continues; someone else carries the loss.Â
- Treat / mitigate / reduce: apply controls to lower likelihood or impact. The residual stays with you.Â
- Tolerate / accept: consciously absorb the risk, documented and signed off. Ignoring risk without a decision is not acceptance; it’s negligence.Â
Related levers: risk appetite (the broad amount of risk the organisation will pursue to meet its goals), risk tolerance (acceptable deviation around a specific objective), and risk capacity (the most it could absorb before real trouble).Â
Controls: Categories and typesÂ
Controls are grouped two ways. By category: administrative/managerial (policies, training, procedures), technical/logical (encryption, firewalls, IAM), and physical (locks, guards, cameras). By function:Â
| Function | Purpose | Example |
| Preventive | Stop an incident before it happens | Access control, encryption, fences |
| Detective | Identify an incident in progress or after | IDS, log review, CCTV monitoring |
| Corrective | Fix and restore after an incident | Patching, restoring from backup |
| Deterrent | Discourage an actor from trying | Warning banners, visible guards |
| Recovery | Return to normal operations | DR site, backup restoration |
| Compensating | Stand-in when the primary control isn’t feasible | Extra monitoring on a legacy system |
| Directive | Direct behaviour toward compliance | Policies, signage, procedures |
For applying controls at scale, know the NIST RMF (SP 800-37) life cycle:Â
Prepare → Categorize → Select → Implement → Assess → Authorize → Monitor.Â
It bakes in continuous monitoring, because risk isn’t a one-off project. Track the programme with a risk register and key risk indicators (KRIs), and route decisions to the people with authority to accept them.Â
EXAM ALERT: You cannot eliminate risk. Residual risk always remains, and it is senior management (or the data owner) who formally accepts it, in writing. An analyst ‘accepting’ risk on their own authority is the wrong answer.Â
9. Threat modelling
Threat modelling means thinking like an attacker, early and deliberately, to find and rank threats before they’re built into a system. A few named approaches:Â
- STRIDE (Microsoft): A checklist of threat types, each the inverse of a security property: Spoofing (↔ authentication), Tampering (↔ integrity), Repudiation (↔ non-repudiation), Information disclosure (↔ confidentiality), Denial of service (↔ availability), Elevation of privilege (↔ authorisation).Â
- PASTA: Process for Attack Simulation and Threat Analysis; a seven-stage, risk-centric method that ties technical threats to business impact.Â
- DREAD: A scoring scheme (Damage, Reproducibility, Exploitability, Affected users, Discoverability) used to rate threats; now largely superseded but still examinable.
- Attack trees, VAST, and Trike: Alternative modelling techniques. MITRE ATT&CK catalogues real adversary tactics and techniques; the cyber kill chain describes attack phases.Â
EXAM ALERT: Keep the verbs straight: STRIDE helps you identify and classify threats; DREAD helps you rate and prioritise them. A question asking how to enumerate threat categories points to STRIDE.
10. Supply chain risk management (SCRM)
Your security is only as strong as your weakest supplier, and attackers know it. SCRM extends your risk thinking out to vendors, their vendors (fourth parties), and the hardware and software you buy.Â
- Vendor due diligence before onboarding: Assess the supplier’s security posture; don’t take it on trust.Â
- Contractual controls: Minimum security requirements, a right-to-audit clause, breach-notification duties, and SLAs with meaningful metrics. Supporting documents: MSA, SOW, and third-party assurance like SOC 2 Type II reports or an ISO 27001 certificate.Â
- Continuous monitoring: Vendor risk is ongoing, not a one-time questionnaire.Â
- Hardware/software integrity: Demand provenance and tamper-resistance. A software bill of materials (SBOM) and hardware bill of materials (HBOM) reveal what’s actually inside a product; a hardware/silicon root of trust and PUFs (physically unclonable functions) anchor trust in the chip itself.Â
EXAM ALERT: Outsourcing transfers the work, never the accountability. If a vendor suffers a breach of your customer’s data, your organisation remains responsible and liable. ‘The vendor is at fault’ is almost always the wrong managerial answer.Â
11. Business continuity requirements
Domain 1 owns the requirements side of continuity; understanding what must survive and how fast , while the actual plan-building and recovery sit in Domain 7. The deliverable here is the Business Impact Analysis (BIA).Â
First, separate the two plans: a Business Continuity Plan (BCP) keeps the whole business running through a disruption (broad), while a Disaster Recovery Plan (DRP) restores IT and operations after a disaster (a subset of BCP).Â
The BIA identifies critical business functions, their dependencies, and how impact grows over time, then sets the timing metrics everyone argues about:Â
| Metric | Means |
| MTD / MTOÂ | Maximum Tolerable Downtime. The longest an outage can last before unacceptable harm |
| RTOÂ | Recovery Time Objective. Target time to restore the function (must be < MTD) |
| RPOÂ | Recovery Point Objective. Maximum acceptable data loss, measured backward in time |
| WRT | Work Recovery Time. Time to verify and resume normal work after systems are back (RTO + WRT ≤ MTD) |
| MTBF / MTTRÂ | Mean Time Between Failures / Mean Time To Repair. Reliability and repair-speed measures |
WORKED EXAMPLE: An order system fails at 2:00 PM. The business can survive at most 8 hours offline before the harm is unacceptable; that 8 hours is the MTD. You set an RTO of 5 hours to get systems running, leaving roughly 3 hours of WRT to re-key and reconcile, so RTO + WRT stays inside the MTD. Backups run every 2 hours, so the worst case is losing the last 2 hours of orders; that 2 hours is the RPO.Â
MANAGER’S LENS: BCP is a business responsibility with visible senior-management ownership, not an IT side-project. Executive sponsorship, defined scope, and the BIA come first; technology choices follow. A plan with no management mandate is the wrong answer even if the tech is perfect.Â
EXAM ALERT: RTO is about time-to-restore; RPO is about data-loss tolerance, and it drives how often you back up. RTO must always be shorter than the MTD. Swapping RTO and RPO is one of the most common slips on the exam.
12. Personnel security
People remain the softest part of any defence, so controls wrap around the whole employment life cycle.Â
- Before hiring: A clear job description, background and reference checks, verification of education and credentials, and signed agreements: NDA (confidentiality) and, where lawful, non-compete.Â
- Onboarding: Provision access on least privilege, have the employee accept the acceptable use policy (AUP), and start security awareness on day one.Â
- During employment: The operational controls that prevent and detect insider abuse (below).Â
- Transfer: Grant the new role’s access and remove the old; otherwise privilege creep / aggregation quietly builds dangerous access.Â
- Termination: De-provision promptly, recover assets, conduct an exit interview, and for hostile exits, disable access at or before notice and escort the person out.Â
- Third parties: Contractors, consultants, and vendors get scoped access governed by agreements, not standing trust.Â
The classic administrative controls, and what each is really for:Â
- Separation of duties (SoD): Split a sensitive process so no one person can complete it alone. Prevents fraud by design.Â
- Dual control / split knowledge: Require two people together to perform a critical action (e.g., two halves of a key).Â
- Least privilege: Only the permissions the role needs. Need-to-know: access to specific information only where the task requires it, even if clearance would allow more.Â
- Job rotation: Move people through roles; cross-trains and surfaces concealed irregularities over time.Â
- Mandatory vacation: Force time off so a substitute covers the role; detects fraud that depends on one person being continuously present.Â
EXAM ALERT: Separation of duties is a preventive control; mandatory vacation and job rotation are detective controls. If a stem wants to uncover fraud a person is actively hiding by always being there, the answer is mandatory vacation.
13. Security awareness, training, and education
The cheapest control with the best return is a workforce that doesn’t fall for the obvious. ISC² separates three tiers, and the distinction is examinable:Â
| Tier | Answers | Audience & aim |
| Awareness | The ‘what’ | All staff; change behaviour and reinforce good habits (posters, phishing simulations) |
| Training | The ‘how’ | Role-based; build a specific skill (e.g., secure coding for developers) |
| Education | The ‘why’ | Security professionals; deeper understanding (certifications, degrees) |
Run it as a programme, not an annual checkbox: refresh at least yearly, tailor content by audience, cover current threats (phishing, pretexting, tailgating, vishing/smishing; and now deepfakes and AI-assisted social engineering), and measure effectiveness with phishing click-rates, quiz scores, and reporting rates. Senior leadership should visibly take part.Â
EXAM ALERT: Awareness is not training. Awareness shifts mindset and behaviour across everyone; training builds a concrete skill for a specific role; education develops expertise. A question contrasting ‘change behaviour’ with ‘teach a skill’ is testing exactly this line.Â
Quick revision: commonly confused pairsÂ
These are the distinctions the exam reaches for again and again. If you can explain each row in a sentence, you’re in good shape.Â
| Concept AÂ | Concept BÂ | The one-line difference |
| Due diligence | Due care | Investigate and understand risk vs. take prudent action on it |
| Policy | Guideline | Mandatory intent vs. optional recommendation |
| Standard | Baseline | Specific uniform requirement vs. minimum acceptable configuration |
| Vulnerability | Threat | A weakness vs. the thing that could exploit it |
| Inherent risk | Residual risk | Before controls vs. what’s left after controls |
| Qualitative | Quantitative | Subjective ratings vs. monetary / probabilistic figures |
| SLEÂ | ALEÂ | Loss per single event vs. expected loss per year |
| Risk appetite | Risk tolerance | Broad risk willing to pursue vs. deviation around one objective |
| Transfer | Mitigate | Shift the financial impact vs. reduce likelihood / impact with controls |
| Least privilege | Need-to-know | Minimum permissions vs. access to specific info a task requires |
| Separation of duties | Mandatory vacation | Prevents fraud by splitting a task vs. detects fraud via forced absence |
| Controller | Processor | Decides purpose & means vs. acts on the controller’s instructions |
| Criminal law | Civil law | Beyond a reasonable doubt vs. preponderance of the evidence |
| Copyright | Trade secret | Protects expression (incl. code) vs. protects confidential info by secrecy |
| Preventive | Deterrent | Physically / technically stops an act vs. discourages the actor |
| RTOÂ | RPOÂ | Time to restore service vs. acceptable amount of data loss |
| BCPÂ | DRPÂ | Keep the business running vs. restore IT after a disaster |
| Awareness | Training | Change behaviour (all staff) vs. build a skill (by role) |
| Authentication | Authorization | Prove who you are vs. what you’re allowed to do |
| Governance | Management | Set direction & accountability vs. execute within it |
Numbers and formulas to lock inÂ
- SLE = AV × EF
ALE = SLE × ARO
Safeguard value = (ALE before − ALE after) − annual control cost. - Never spend more on a control than the asset’s value or the risk it removes.Â
- (ISC)² canon order:Â
Public/society → Honour/legality → Service to principals → Profession (lower number wins a conflict).Â
- GDPR: 72-hour breach notice; fines up to €20M or 4% of global turnover; controller decides, processor executes.Â
- IP life: patent ~20 years (public disclosure); copyright author’s life + 70; trademark indefinite if defended; trade secret while secret.Â
- Continuity timing: RTO + WRT ≤ MTD; RPO drives backup frequency; RTO is always shorter than MTD.Â
- NIST RMF:Â
Prepare → Categorize → Select → Implement → Assess → Authorize → Monitor.Â
- NIST CSF 2.0 functions: Govern, Identify, Protect, Detect, Respond, Recover.
Frequently Asked Questions
How much of the CISSP exam is Domain 1?
Around 16%, it is the largest single domain. Its risk-management thinking also underpins questions across the other seven domains, so it pays back more than its weighting suggests.
What is the order of the (ISC)² Code of Ethics canons?
Protect society and the public first; act honourably and legally; provide diligent service to principals; advance and protect the profession. When two canons conflict, the earlier (lower-numbered) one takes precedence.
What's the difference between RTO and RPO?
RTO is how quickly you must restore a function after an outage. RPO is how much data you can afford to lose, measured backward from the incident . It sets how often you back up. RTO is about time; RPO is about data.
What's the difference between due care and due diligence?
Due diligence is investigating and understanding your risks and duties. Due care is taking the reasonable, prudent action a careful organisation would take as a result. Diligence is the homework; care is acting on it. Failing due care is negligence.
How do you calculate Annualised Loss Expectancy (ALE)?
Find the Single Loss Expectancy (SLE = asset value × exposure factor), then multiply by the annualised rate of occurrence (ARO). So ALE = SLE × ARO. Compare ALE before and after a control, minus the control's annual cost, to judge whether the control is worth it.
Who is allowed to accept residual risk?
Senior management (or the designated data/system owner); the people with the authority and accountability to own the consequences. Risk acceptance is a documented, deliberate decision, never an individual analyst's call.
What's the difference between a data controller and a data processor?
The controller decides why and how personal data is processed and holds primary accountability; the processor only handles data on the controller's instructions. Outsourcing processing does not transfer the controller's accountability.
Does outsourcing transfer liability?
No. You can transfer the work and some financial impact, but accountability and legal responsibility for protecting the data stay with your organisation. This is a recurring exam theme and a real-world trap.
Qualitative or quantitative risk analysis: which should I use?
Qualitative is fast, subjective, and good for ranking when hard data is scarce; quantitative puts money and probability behind decisions but needs reliable data. Most organisations use a hybrid: qualitative to triage, quantitative to justify spend.
