ISC · Security and Confidentiality and Privacy · 8 practice questions
When Is the NIST Cybersecurity Framework the Right Choice?
NIST CSF organizes enterprise cybersecurity risk around Govern, Identify, Protect, Detect, Respond, and Recover. Below, sort framework requests by the deciding clue: cybersecurity functions and posture profiles, a certifiable ISMS, or broader enterprise IT governance.
Try one first
Hint
Focus on which framework is organized around the listed core functions and exclude frameworks primarily tied to certification or external attestation.
Answer D. The NIST Cybersecurity Framework is organized around the core functions Govern, Identify, Protect, Detect, Respond, and Recover and is widely used as a non-certifiable, high-level structure to organize and communicate an organization's cybersecurity program. Because the company is not seeking certification or preparing an external attestation report, the CSF is the most appropriate primary framework.
Why not A: SOC 2 tempts because the Trust Services Criteria define security-related controls and are commonly used in third-party attestation reports. It is not the best choice here because SOC 2 is attestation-focused for service organizations and the stem excludes preparing an external attestation report.
Why not B: ISO/IEC 27001 tempts because it is a recognized, certifiable information security management standard that organizations adopt when they want formal certification. It is less appropriate here since the stem rules out seeking certification and ISO 27001 does not organize a program around the CSF's named core functions.
Why not C: COBIT tempts because it provides enterprise IT governance and control guidance, making it seem broadly relevant to cybersecurity. However, COBIT is focused on IT governance and business alignment rather than the specific cybersecurity function structure (Govern, Identify, Protect, Detect, Respond, Recover) that the company wants to use.
Sort it
Does the request center on the six cybersecurity functions or risk-based current and target cybersecurity posture?
Does the request call for a certifiable information security management system?
Does the request center on governance and management of enterprise IT broadly?
| Item | Goes to |
|---|---|
| A manufacturer wants to organize cybersecurity around Govern, Identify, Protect, Detect, Respond, and Recover. | NIST CSFThe six function names directly identify NIST CSF. |
| Management wants formal certification of the manufacturer's information security management system. | ISO/IEC 27001The deciding clue is certification of an ISMS, not a cybersecurity posture profile. |
| The board wants governance guidance connecting enterprise IT objectives, business goals, and value delivery. | COBITThe scope is enterprise IT governance and management, not specifically cybersecurity posture. |
| Management wants a Current Profile, a Target Profile, and risk-based priorities for closing cybersecurity gaps. | NIST CSFCurrent and Target Profiles support cybersecurity gap assessment and prioritization. |
| Management wants a certifiable ISMS standard, even though certification will occur later. | ISO/IEC 27001The requested standard must support ISMS certification; the timing does not change that requirement. |
| The board wants oversight of IT performance, resources, and business alignment beyond cybersecurity. | COBITThe explicit focus beyond cybersecurity points to broader enterprise IT governance. |
| The manufacturer already uses COBIT but needs a separate cybersecurity Current and Target Profile for board reporting. | NIST CSFCSF supplies the requested cybersecurity profiles while COBIT remains useful for broader IT governance. |
| Management wants a common cybersecurity posture language that can later map to detailed controls, without seeking certification. | NIST CSFCSF provides a high-level posture and communication structure that can map to detailed controls. |
| Management wants a framework for governing and managing enterprise IT as a whole, including cybersecurity. | COBITCybersecurity is included, but the requested scope is enterprise IT overall. |
| Management wants an auditable ISMS requirements standard as the basis for external certification. | ISO/IEC 27001An ISMS requirements standard supporting certification points to ISO/IEC 27001. |
| The board wants cybersecurity priorities reported through the six CSF functions, including Govern. | NIST CSFBoard involvement does not make this COBIT; the specified cybersecurity functions identify CSF. |
| Management wants a voluntary cybersecurity posture framework that works across industries and supports risk-based improvement targets. | NIST CSFCross-industry cybersecurity posture assessment and improvement targets match CSF's purpose. |
Key points
- Remember: The six named cybersecurity functions point to NIST CSF, not ISO 27001 or COBIT.
- Not seeking certification is a supporting clue, not enough by itself to identify NIST CSF.
- Existing COBIT guidance can remain while CSF organizes cybersecurity posture reporting.
How the exam traps you
- Choosing COBIT whenever the request mentions the board or governance. Look at the scope: cybersecurity posture profiles favor CSF; broader enterprise IT governance favors COBIT.
- Choosing ISO 27001 because it is a recognized security standard. A certifiable ISMS favors ISO 27001. The six named cybersecurity functions identify NIST CSF.
Question 2
Hint
Focus on whether the item is guidance an organization may choose to use, or a legally enforceable requirement that applies to certain entities.
Answer A. The NIST Cybersecurity Framework is voluntary guidance organizations may adopt to structure their cybersecurity risk-management activities (identify, protect, detect, respond, recover). It provides best-practice categories and implementation guidance but is not itself a law or enforceable regulation. The other choices are regulatory requirements that apply to covered entities or public companies.
Why not B: This is tempting because HIPAA includes technical, physical, and administrative safeguards related to information security, but the HIPAA Security Rule is a federal regulation enforced by HHS (OCR) that applies to covered entities and business associates, it is not voluntary guidance.
Why not C: This distractor may sound like a set of best practices, yet the GLBA Safeguards Rule imposes regulatory obligations on certain financial institutions (and is enforceable), so it is not a voluntary framework.
Why not D: Candidates might associate SEC guidance with corporate governance, but SEC disclosure requirements for public companies are regulatory obligations about what must be reported to investors and are not a voluntary cybersecurity framework.
Question 3
Hint
Focus on whether the board wants certification/attestation or a flexible, risk‑based profile for management reporting; choose the framework suited to current/target profiling and prioritized gaps.
Answer A. The NIST CSF is a flexible, risk‑based framework specifically designed to help organizations describe current and target cybersecurity states and to prioritize gaps for remediation in a management‑friendly way. COBIT remains appropriate for broader IT governance and complements NIST CSF rather than requiring replacement. Because the company is not seeking certification and has no industry-driven compliance requirement, a certifiable standard or narrowly scoped compliance standard is not the best primary profiling tool.
Why not B: Tempting because CIS Controls are practical and prioritized for implementation, but they are an implementation control set rather than a high‑level, risk‑based profiling framework for board‑level current/target state reporting. CIS Controls can complement NIST CSF for technical remediation but are not the best standalone profiling framework for management reporting.
Why not C: Tempting because ISO/IEC 27001 is a well‑known ISMS standard and supports external attestation, but the stem states the company is not pursuing certification. ISO/IEC 27001 is typically more attestation‑oriented and heavier weight than NIST CSF for quickly producing a concise, risk‑based current/target profile and prioritized remediation roadmap.
Why not D: Tempting because COBIT covers governance and high‑level control objectives, but COBIT is not primarily a risk‑focused, cyber‑specific profiling tool. It won't by itself provide the cyber‑focused, current/target state profiling and prioritized gap analysis the board requested.
Question 4
Hint
For each choice, identify its primary purpose: a detailed control catalog, a certifiable ISMS standard, an enterprise cybersecurity risk framework, or an IT governance model.
Answer A. NIST CSF 2.0 is a voluntary, enterprise-focused cybersecurity risk-management framework intended to provide a common language for governance and the lifecycle of cyber risk. Version 2.0 explicitly incorporates a governance function and organizes the core lifecycle functions as Govern, Identify, Protect, Detect, Respond, and Recover, matching the stem's stated needs. It is intended for stakeholder-level communication rather than as a prescriptive system-level control catalog or a certifiable ISMS.
Why not B: Tempting because ISO/IEC 27001 addresses enterprise information security through an ISMS and is widely used to formalize organizational security practices. It fails because ISO/IEC 27001 is primarily a certifiable management-system standard focused on establishing, operating, and (optionally) certifying an ISMS; the stem excludes pursuing formal certification and requests a function-organized, stakeholder-facing cyber risk framework instead.
Why not C: Tempting because SP 800-53 provides a comprehensive set of security and privacy controls used for selecting and implementing system-level safeguards. It fails here because the company asked for an enterprise-level, voluntary framework to align governance and stakeholder discussion, not a prescriptive control catalog intended for system control selection and implementation.
Why not D: Tempting because COBIT provides high-level guidance on governance and management of enterprise IT and aligns IT objectives with business needs. It fails here because COBIT is a broader IT governance model rather than a cybersecurity-specific, lifecycle-organized risk framework structured around the Identify/Protect/Detect/Respond/Recover functions called for in the stem.
Question 5
Hint
Focus on the organization's stated need: a broad, risk-based framework for enterprise cybersecurity, without an industry-specific compliance trigger or a current certification objective.
Answer B. NIST CSF 2.0 is a broadly applicable, risk-based framework intended to help organizations govern, assess, and improve cybersecurity across the enterprise. It provides structure and priorities without being tied to an industry-specific legal requirement or to immediate certification. Given the stem's exclusions, CSF 2.0 is the best overall choice.
Why not A: PCI DSS is a compliance standard focused specifically on payment-card data security. While important if the retailer must meet payment-card requirements, PCI DSS is not designed as a broad, enterprise-wide governance framework for all cybersecurity risks.
Why not C: The HIPAA Security Rule applies to covered entities and business associates handling protected health information. It is not an appropriate enterprise-wide framework for a general retailer absent a healthcare-specific context.
Why not D: ISO/IEC 27001 is a respected standard, but certification is not required to adopt an effective framework. Waiting for a certification decision delays practical improvements when management already wants a risk-based structure now.
Question 6
Hint
Select the option whose primary purpose is to portray current vs. target cybersecurity posture and to be cross-walked to controls, rather than the option primarily intended for certification, governance oversight, or technical implementation.
Answer A. The NIST CSF is explicitly designed as a high-level, risk-based framework to describe current and target cybersecurity posture and to prioritize risk-based gaps while facilitating consistent communication with leadership and external stakeholders. It is intended to be cross-walked to more prescriptive control sets or assurance standards, so it fits when certification is not the immediate goal.
Why not B: ISO 27001 tempts because it is a risk-based, auditable ISMS standard that supports certification; however, it is primarily used when an organization intends to implement and certify an ISMS, so it is less suited as the immediate, high-level posture-assessment and communication framework described here.
Why not C: COBIT tempts because it provides governance and management guidance valuable to executives; however, it is broader than a cybersecurity posture framework and is not optimized for describing current versus target cybersecurity state to external customers.
Why not D: The CIS Controls tempt because they give a prioritized, technical set of safeguards to implement; however, they are a prescriptive control baseline rather than a high-level framework intended for posture assessment and stakeholder communication.
Question 7
Hint
Separate the idea of a voluntary framework from the idea of a binding legal or contractual requirement.
Answer B. The NIST CSF is a voluntary framework that helps organizations structure cybersecurity risk management and controls. Adopting the CSF can support and demonstrate a sound security program, but it does not itself satisfy every legal, regulatory, or contractual obligation. Compliance depends on the specific requirements that apply to the organization and its data.
Why not A: This is tempting because NIST guidance is often associated with federal entities, but the CSF is a voluntary framework widely used across the private sector; it is not limited to federal agencies or contractors.
Why not C: A framework helps structure risk management, but it does not replace the need for ongoing risk assessments. Organizations must assess risks to select, prioritize, and evaluate controls consistent with the CSF's risk-based approach.
Why not D: Adopting a recognized framework can help meet parts of regulatory expectations, but legal compliance depends on the specific statutes, regulations, and contractual terms that apply; framework adoption alone does not guarantee compliance.
Question 8
Hint
Focus on the exact set of cybersecurity functions named in the stem and distinguish a general framework from a regulation or certifiable standard.
Answer B. The NIST Cybersecurity Framework is a broadly used, industry-agnostic framework organized around the functions Govern (in CSF 2.0), Identify, Protect, Detect, Respond, and Recover. It is intended to help organizations structure and improve cybersecurity risk management without being an industry-specific regulation or a certifiable management-system standard.
Why not A: COBIT is a governance and management framework for enterprise IT controls and is focused on governance, risk, and value delivery for IT broadly. It does not use the specific CSF function set named in the stem and is less tailored as a general-purpose cybersecurity program framework.
Why not C: ISO/IEC 27001 is a certifiable information security management standard for establishing an ISMS. The stem excludes certifiable management-system standards and specifically lists the CSF function names, so ISO/IEC 27001 is not the best fit.
Why not D: The HIPAA Security Rule is a U.S. regulatory requirement applying to covered entities and business associates in healthcare. It is not a general-purpose cybersecurity framework for a retailer and does not use the CSF function taxonomy described in the question.
Common questions
What are the six functions of NIST CSF 2.0?
Govern, Identify, Protect, Detect, Respond, and Recover. These names are the clearest framework-selection clue.
When should a company choose NIST CSF instead of ISO 27001?
NIST CSF fits a request for cybersecurity posture profiles, risk-based priorities, and stakeholder communication. ISO 27001 fits a request for a certifiable information security management system.
Should a company replace COBIT with NIST CSF?
Not necessarily. COBIT can guide broader enterprise IT governance while NIST CSF provides cybersecurity Current and Target Profiles for board reporting.
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Regulations and standards and frameworks
- PCI DSS vs. NIST CSF vs. ISO 27001 vs. COBIT
- Do NIST CSF and ISO 27001 Satisfy HIPAA or PCI DSS?
- SOC 2 vs ISO 27001 vs PCI DSS vs NIST CSF
- PCI DSS Scope: Card Data, Hosted Checkout, and Admin Systems
- ISO 27001 vs NIST CSF vs SOC 2: Which Should You Choose?
- SEC Cybersecurity Disclosure: The Four-Business-Day Clock
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.