DOMAIN 1 · Security and Risk Management
Security governance and ISMS
Connect business objectives, risk ownership, policies, and continual improvement through an information security management system.
Start with business decisions
Section titled “Start with business decisions”Security governance establishes direction, responsibility, and oversight. A useful starting question is what the organization needs to achieve and which information failures would prevent it. Buying a control before establishing that context can produce strong protection for the wrong asset. NIST CSF 2.0 explicitly places governance alongside identifying, protecting, detecting, responding, and recovering.1
For CISSP study, connect a technical recommendation to its business consequence, accountable decision maker, and evidence of effectiveness. Governance supplies the reason and authority; operational work implements that direction.
Understand the management system
Section titled “Understand the management system”An information security management system (ISMS) integrates security into organizational management. ISO/IEC 27001 specifies ISMS requirements; ISO/IEC 27002 provides control guidance. They serve related purposes but are not interchangeable documents.23
JIPDEC’s public user guide explains risk assessment, treatment, support, and operation in an ISMS. This is broader than maintaining a collection of security products.4 A practical implementation therefore includes people, repeatable processes, and records showing that decisions were followed through.
Separate direction from implementation
Section titled “Separate direction from implementation”| Management artifact | Purpose | Illustrative example |
|---|---|---|
| Policy | Establish intent and responsibility | Customer information must be protected according to business impact |
| Standard | Specify consistent mandatory requirements | Approved encryption must protect restricted information in transit |
| Procedure | Describe an executable sequence | Request, approve, provision, and verify a new account |
| Guideline | Support judgment with recommended practices | Suggested approaches for writing useful access-review notes |
These examples are a teaching convention rather than quotations from an ISO clause. Organizations should define their own document hierarchy and exception authority clearly.
Make accountability visible
Section titled “Make accountability visible”A business owner should explain the consequences of losing a service or exposing information. Security specialists analyze threats and recommend treatment. Operators implement controls. A person with the appropriate authority decides whether remaining risk is acceptable.
Combining these responsibilities without independent review can hide conflicts. An exception should identify its owner, justification, compensating measures, expiration, and review trigger. An undocumented exception can quietly become a permanent operating practice.
Use frameworks for different questions
Section titled “Use frameworks for different questions”CSF outcomes help communicate where an organization is and where it wants to be. A Current Profile describes selected present outcomes; a Target Profile expresses desired outcomes. The difference can inform priorities.1 ISO public materials instead explain the requirements and control-guidance roles of the 27001 and 27002 standards.23
A mapping between frameworks can reduce duplicate work. It does not prove that meeting one framework automatically satisfies every requirement of another.
Example: introducing a customer portal
Section titled “Example: introducing a customer portal”Suppose a firm moves customer records into a new portal. Management first identifies the service scope and acceptable disruption. Owners classify the records and assess access risks. The team selects controls, allocates resources, and records decisions. After launch, access reviews, incident findings, and service evidence reveal whether protection is working.
A quarterly review might find that departed contractors retain access. The response includes fixing accounts and correcting the offboarding process, then checking whether the correction persists. This is an illustrative improvement cycle, not an ISO certification checklist.
Avoid common misconceptions
Section titled “Avoid common misconceptions”Certification applies to a defined scope; it does not promise that incidents cannot occur. A completed policy is not evidence that staff follow it. Likewise, security governance is not a task delegated entirely to IT: decisions about resources and business risk need management involvement. Improve the system using observed results rather than counting documents alone.
Continue learning
Section titled “Continue learning”Read risk assessment for decision inputs and information classification for connecting information value to protection.
Footnotes
Section titled “Footnotes”-
NIST, The Cybersecurity Framework 2.0, sections 2–3 and Appendix A. ↩ ↩2
-
ISO, ISO/IEC 27001:2022 public overview. Full standard text is not reproduced here. ↩ ↩2
-
ISO, ISO/IEC 27002:2022 public overview. Full standard text is not reproduced here. ↩ ↩2
-
JIPDEC, ISMSユーザーズガイド, 2025, sections 5–10; original summary, no standard text reproduced. ↩
Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution