CISSP Domain 1 Without the Jargon: Security and Risk Management
6 min read6 views
Super Admin
Security and Risk Management is the first of the eight CISSP domains and one of the most heavily weighted. It is also the domain candidates most often call "dry", because it reads like a list of definitions. Underneath the vocabulary, though, is a single idea: security exists to serve the business, and every decision is a trade-off between risk, cost and what the organisation is trying to achieve.
This article walks through the key ideas in plain language, shows how they connect, and ends with a few questions you can use to check your understanding.
Why Domain 1 sets the tone for the whole exam
The CISSP is often described as a management exam, and Domain 1 is where that reputation comes from. Many questions across all eight domains are really asking a Domain 1 question in disguise: who is accountable, what does the policy say, what is the most appropriate response given the business context? If you understand this domain well, a large share of the scenario questions elsewhere become easier, because you will recognise the "think like a manager" answer.
The exam itself is a computerised adaptive test of 100 to 150 questions over three hours, with a passing score of 700 out of 1000. Current details are on the ISC2 CISSP page.
The key ideas
Governance: direction from the top
Security governance is how senior leadership sets direction and holds people accountable. It is not the same as security management. Governance decides what the organisation wants to achieve and how much risk it will tolerate; management decides how to achieve it day to day. The board and executives own the risk. The security team advises, implements and reports, but it does not get to decide on its own that a risk is acceptable.
A useful exam habit: when a question asks who is ultimately responsible for protecting an asset, the answer is almost always senior management or the data owner, not the security administrator.
Due care versus due diligence
These two terms are tested often because they sound alike. The simplest way to separate them:
- Due diligence is doing your homework: researching, assessing and understanding the risks before you act. Reviewing a vendor's security before signing a contract is due diligence.
- Due care is doing the right thing once you know: implementing and maintaining reasonable safeguards. Actually enforcing the controls in that contract is due care.
Think of diligence as "investigate" and care as "act". Failing at either can expose an organisation to claims of negligence.
Policies, standards, procedures and guidelines
Security documentation forms a hierarchy, and the exam expects you to know which layer is which.
| Document | Mandatory? | Level of detail | Example |
|---|---|---|---|
| Policy | Yes | High-level intent, approved by senior management | "All sensitive data must be protected in storage and transit." |
| Standard | Yes | Specific, measurable requirements that support a policy | "Data at rest must use an approved strong encryption algorithm." |
| Procedure | Yes | Step-by-step instructions | "How to enable disk encryption on a new laptop, steps 1 to 9." |
| Guideline | No | Recommendations and good practice | "Consider using a password manager for long passphrases." |
| Baseline | Yes | A minimum configuration level | "All servers must meet the approved hardening template." |
The word that matters most is mandatory. Guidelines are the only item in the hierarchy that is advisory.
Risk and risk response
Risk is the likelihood that a threat will exploit a vulnerability, combined with the impact if it does. Once a risk is identified and assessed, there are four broad ways to respond:
- Mitigate (reduce): apply controls to lower likelihood or impact.
- Transfer (share): move the financial impact to someone else, typically through insurance or a contract.
- Avoid: stop the activity that creates the risk.
- Accept: consciously decide to live with the risk, usually because the cost of treating it exceeds the expected loss.
Two points catch candidates out. First, transferring risk does not transfer accountability: if a cloud provider loses your customers' data, your organisation still answers to those customers. Second, ignoring a risk is not the same as accepting it. Acceptance is a documented decision by someone with the authority to make it.
Quantitative analysis puts numbers on this. The classic formulas are worth memorising:
SLE = Asset Value (AV) x Exposure Factor (EF)
ALE = SLE x Annualised Rate of Occurrence (ARO)
Example: AV = 200,000; EF = 0.25; ARO = 0.5
SLE = 50,000
ALE = 25,000 per year
If a control costs more each year than the ALE it removes, it is hard to justify on financial grounds alone.
Legal and regulatory issues
Domain 1 also covers the legal environment security works within. You do not need to be a lawyer, but you should recognise the broad categories: criminal, civil and administrative law; intellectual property such as copyrights, trademarks, patents and trade secrets; licensing; privacy requirements; and the issues raised when data crosses national borders. The exam favours general principles over the details of any single country's statute.
Closely related is professional ethics. Every CISSP agrees to the ISC2 Code of Ethics, whose canons put protecting society and the common good first, followed by acting honourably and legally, serving principals diligently and competently, and advancing the profession. When an ethics question offers several reasonable actions, the canon order is often the tie-breaker.
A short glossary
- Asset
- Anything of value to the organisation: data, systems, people, reputation.
- Threat
- A potential cause of harm, such as an attacker, a flood or a careless employee.
- Vulnerability
- A weakness a threat could exploit.
- Residual risk
- The risk that remains after controls are applied.
- Risk appetite
- The amount of risk leadership is willing to pursue or retain to meet its objectives.
- Data owner
- The senior person accountable for a data set and its classification.
Common traps in Domain 1 questions
- Choosing a technical fix when the question asks about governance or accountability.
- Treating insurance as if it removes the organisation's responsibility.
- Confusing a standard, which is mandatory, with a guideline, which is not.
- Picking the most secure option when the question asks for the most appropriate one for the business.
Check your understanding
Try these before reading the answers.
- A company reviews a payroll vendor's audit reports before signing. Is this due care or due diligence?
Answer: Due diligence. It is investigation before acting. - A risk costs an estimated 10,000 a year; the only control costs 40,000 a year. Leadership signs off on living with it. Which response is this?
Answer: Acceptance, properly documented by someone with authority. - Which document in the hierarchy is not mandatory?
Answer: The guideline. - An organisation buys cyber insurance. Who remains accountable for a breach of customer data?
Answer: The organisation itself. The financial impact can be shared; accountability cannot.
Conclusion
Domain 1 rewards understanding over memorisation. If you can explain why governance sits above management, why diligence comes before care, and why accepting a risk is a decision rather than an omission, you have the mindset the rest of the CISSP keeps testing. Learn the vocabulary, but always ask the question the exam is really asking: what would a responsible leader do here?
CISSP
2,111 practice questions
How ready are you for CISSP?
Take the entry assessment and see exactly which domains need work.
Take the assessment24 questions · about 15 minutes · no account needed
CISSP
Discussion (0)
No discussion here yet — be the first to comment.
Please sign in to join the discussion.