ISC · Security and Confidentiality and Privacy · 7 practice questions
PCI DSS vs. NIST CSF vs. ISO 27001 vs. COBIT
Choose the authority whose primary purpose matches the stated objective. Below: compare legal duties, security standards, and governance frameworks using the clues that determine the exam answer.
Try one first
Hint
Match each need to the framework's primary purpose: one must be payment-card specific; the other must focus on IT governance and measuring governance maturity.
Answer A. PCI DSS is the industry-specific standard that governs requirements for entities that store, process, or transmit payment cardholder data. COBIT is an IT governance framework designed to align IT processes and controls with enterprise objectives and to measure governance maturity. Because the stem excludes external attestation and ISMS certification and asks specifically for governance-alignment and maturity measurement, PCI DSS plus COBIT best match the two needs.
Why not B: Tempting because NIST CSF is widely used to organize cybersecurity activities and supports communicating cyber risk. It is incorrect here because NIST CSF is principally a risk-management and communications framework, not primarily an IT governance framework for aligning controls to enterprise objectives and measuring governance maturity, roles that COBIT fills.
Why not C: Tempting because ISO/IEC 27001 addresses information security program requirements and is widely respected. It is wrong for item 1 because ISO/IEC 27001 is an ISMS certifiable standard and is broader than the payment-card-specific PCI DSS; the stem explicitly excludes pursuing ISMS certification and asks for the industry-specific standard for cardholder data.
Why not D: Tempting because SOC 2 assesses controls and ITIL is a familiar IT framework for processes. It is incorrect because SOC 2 is an attestation report framework for service organizations, not the industry standard that governs payment cardholder data, and ITIL is an IT service-management best practice set rather than an IT governance framework intended to align enterprise objectives and measure governance maturity.
Side by side
| Laws and regulations | Security standards | Governance and risk frameworks | |
|---|---|---|---|
| Sources | GDPR; HIPAA Security Rule. | PCI DSS; ISO/IEC 27001. | NIST CSF; COBIT. |
| Basic status | GDPR: EU regulation. HIPAA Security Rule: U.S. federal regulation. | PCI DSS: industry contractual standard. ISO/IEC 27001: certifiable international standard. | Generally voluntary frameworks unless adoption is required by law or contract. |
| Primary purpose | GDPR: personal data protection. HIPAA Security Rule: ePHI security. | PCI DSS: cardholder data security. ISO/IEC 27001: information security management system (ISMS) requirements. | NIST CSF: cybersecurity risk management. COBIT: governance and management of enterprise information and technology. |
| Relevant scope | GDPR: personal data processing within its legal scope. HIPAA Security Rule: ePHI of covered entities and business associates. | PCI DSS: cardholder data environment. ISO/IEC 27001: defined ISMS scope. | NIST CSF: enterprise cybersecurity outcomes. COBIT: enterprise IT governance and management. |
| Decisive exam clues | Applicable GDPR duties; legally binding ePHI security requirements. | PCI DSS: storing, processing, or transmitting cardholder data. ISO/IEC 27001: external ISMS certification. | NIST CSF: Govern, Identify, Protect, Detect, Respond, Recover; communicate cybersecurity risk to the board and compare Current and Target Profiles. COBIT: enterprise IT accountability, business alignment, and performance monitoring. |
| Certification distinction | Legal compliance is not ISO/IEC 27001 certification. | ISO/IEC 27001 provides a basis for independent ISMS certification; PCI DSS addresses separate card-security requirements. | NIST CSF and COBIT are not ISO-style organizational ISMS certification standards. |
| Can it replace other obligations? | Applicable legal duties remain even when standards or frameworks are adopted. | ISO/IEC 27001 certification does not replace PCI DSS, GDPR, or HIPAA duties. | NIST CSF and COBIT can complement scoped requirements, not eliminate them. |
Key points
- Remember: choose by the stated objective, not by which authority sounds broadest or most official.
- Board involvement alone does not mean COBIT; communicating cybersecurity risk and comparing Current and Target Profiles point to NIST CSF.
- PCI DSS can be contractually mandatory without being a federal regulation.
- Certification does not replace applicable legal or payment-card obligations.
How the exam traps you
- Choosing PCI DSS as the complete enterprise cybersecurity framework. Use PCI DSS for the cardholder data environment and NIST CSF for broader cybersecurity risk management.
- Treating ISO/IEC 27001 certification as a substitute for legal compliance. Apply GDPR or the HIPAA Security Rule when required; ISMS certification does not replace those duties.
- Choosing COBIT whenever the question mentions the board. Choose NIST CSF for cyber risk communication and profiles; choose COBIT for enterprise IT accountability, alignment, and performance.
Question 2
Hint
Identify which baseline the subcontract requires for CUI on a contractor's nonfederal systems and remember that voluntary frameworks, industry‑specific standards, or third‑party certifications do not automatically replace a named contractual baseline.
Answer A. When a DoD prime contract's CUI protection requirements are flowed down to a subcontractor for CUI on the subcontractor's nonfederal systems, the contractually required baseline for those nonfederal systems is NIST SP 800-171. NIST SP 800-53 is the broader federal control catalog for federal systems, PCI DSS specifically addresses payment-card environments, and the NIST CSF is a voluntary, high-level framework, each may be relevant in its scope but do not, by themselves, satisfy a contractually specified 800-171 baseline absent explicit contract allowance.
Why not B: This is tempting because 800-53 is associated with federal systems and DoD, but 800-53 is the federal control catalog for federal information systems. For CUI that resides on a contractor's nonfederal systems and where the subcontract flows down a contractor baseline, NIST SP 800-171 is the directly applicable contract-driven baseline.
Why not C: This distractor plays on the CSF's prominence, but the CSF is voluntary and high-level. It can help organize or map controls, yet adopting the CSF alone does not automatically meet a specific contractual requirement to implement NIST SP 800-171 unless the contract explicitly permits such a substitution.
Why not D: ISO/IEC 27001 certification demonstrates a formal ISMS and may overlap substantially with required controls, but certification does not by itself satisfy a contract clause that names a particular baseline unless the subcontract explicitly authorizes substitution or maps the certification to the required controls.
Question 3
Hint
Classify each option by type before choosing: framework, regulation, attestation report, or certifiable standard.
Answer C. The NIST Cybersecurity Framework (CSF) is a voluntary framework organizations use to organize, assess, and communicate cybersecurity risk. It provides guidance to structure a cybersecurity program and is not itself a law, an external attestation, or a certifiable standard, so it best fits the 'voluntary framework' category.
Why not A: A SOC 2 report is an external attestation report issued by an auditor about controls relevant to Trust Services Criteria; it documents assurance over controls rather than serving as an internal voluntary framework.
Why not B: HIPAA's Security Rule is a U.S. sector-specific regulation that imposes legal requirements on covered entities and business associates; it is not a voluntary, general-purpose cybersecurity framework.
Why not D: ISO/IEC 27001 is an international certifiable standard for an information security management system (ISMS); organizations can be certified against it, so it is a standard/certification, not a voluntary guidance framework like the NIST CSF.
Question 4
Hint
Separate the items into three buckets: law/regulation, industry or contractual standard, and voluntary risk-management framework.
Answer B. GDPR is an EU legal/regulatory regime and is therefore a binding legal requirement where it applies. PCI DSS is an industry/contractual standard imposed through payment-card networks and acquiring relationships rather than being a general statute. The NIST Cybersecurity Framework is a widely used voluntary framework appropriate for organizing an enterprise cybersecurity risk-management program.
Why not A: This is tempting because PCI obligations often feel mandatory in practice, but PCI DSS is typically contractual/industry-enforced rather than statutory. GDPR is not voluntary when it applies. ISO/IEC 27001 is normally voluntary and is not generally required by law unless a specific statute or contract says so.
Why not C: This distractor appeals to the idea that only storing card numbers creates PCI scope, but accepting payment cards usually creates at least some PCI obligations even if storage is outsourced or limited. COBIT is a governance framework and not the cardholder-data security standard.
Why not D: This is tempting if a candidate incorrectly equates GDPR applicability with physical presence; GDPR can apply extraterritorially in the circumstances described. PCI DSS is not a broad enterprise cybersecurity framework, and NIST CSF covers all aspects of cybersecurity risk management, not just privacy.
Question 5
Hint
Choose the framework best suited for high-level board communication and flexible current-vs-target profiling rather than immediate control-level implementation or certification.
Answer D. The NIST Cybersecurity Framework is a voluntary, high-level, outcome-focused framework intended to help organizations communicate cybersecurity risk to governance bodies, profile current versus target states, and organize improvement activities. Given Raven's need for board-level communication and flexible current-vs-target profiling (with no regulatory or certification mandate), CSF is the most appropriate top-level organizing framework. It is commonly mapped to more detailed control catalogs later if implementation detail is required.
Why not A: COBIT tempts because it links IT governance and business objectives and is useful for enterprise-level governance. It is less directly suited to Raven's request for a concise, cyber-specific, board-facing profiling tool focused on current-versus-target cybersecurity state; COBIT is broader and governance-oriented rather than purpose-built for quick cyber risk profiling.
Why not B: SP 800-53 tempts because it is a comprehensive, authoritative control catalog used for baseline selection and federal compliance. It is less appropriate here because Raven's initial need is a concise, board-facing framework for profiling and communication; SP 800-53 is better used later as a source of detailed controls for implementation and compliance.
Why not C: ISO/IEC 27001 tempts because it provides an auditable ISMS and strong governance constructs. It is less suitable as the immediate primary framework here because starting with a certifiable ISMS can introduce more prescriptive process and overhead when certification is not an objective; ISO 27001 is often chosen when an organization intends to implement and maintain a formal ISMS.
Question 6
Hint
For each item, ask: is it fundamentally a statutory/regulatory requirement, a voluntary framework/guidance, or an international formal standard used for certification?
Answer A. Option A correctly assigns each item by its general nature. The HIPAA Security Rule is a binding U.S. regulation for covered entities and business associates; the NIST CSF is a voluntary risk-management framework; ISO/IEC 27001 is an international formal standard against which organizations may be certified; and COBIT is a governance/control framework (not a law or an ISO-style certifiable standard). The stem asked for general status, not whether a sector or contract makes an item mandatory.
Why not B: This option tempts candidates who mistake official-sounding guidance for binding law or who treat all control models as certifiable standards. In fact, HIPAA is a binding regulation (not voluntary guidance), NIST CSF is voluntary (not a law), and COBIT is a governance framework rather than a formal certifiable standard like ISO/IEC 27001.
Why not C: Option C plays on the similarity between prescriptive requirements and formal standards. However, HIPAA is regulatory law and is not an ISO-style certification standard, and ISO/IEC 27001 is an international standard organizations may certify against, it is not itself a statute or binding law.
Why not D: This choice may attract those who overstate the formal status of some frameworks. NIST CSF is a voluntary framework (not a certifiable formal standard), ISO/IEC 27001 is a formal standard usable for certification (not merely general guidance), and COBIT is not a binding law/regulation.
Question 7
Hint
Separate the payment-card obligation from the broader enterprise risk-management goal. Ask which choice handles both without assuming one framework replaces a more specific standard.
Answer B. PCI DSS is a payment-card-specific standard that applies contractually to systems that store, process, or transmit cardholder data and therefore must be met for the cardholder data environment. The NIST Cybersecurity Framework is well suited to enterprise-wide risk identification, prioritization, and communication and can complement PCI DSS. The best action is to satisfy PCI DSS for the CDE while adopting NIST CSF for broader enterprise cybersecurity risk management.
Why not A: Tempting because NIST CSF covers cybersecurity broadly, but the retailer has a contractual obligation to comply with PCI DSS for systems that handle cardholder data. A general framework can complement PCI DSS but does not eliminate the merchant-agreement requirement to meet the payment-card standard.
Why not C: PCI DSS is narrowly targeted to protecting cardholder data and the cardholder data environment. Treating it as the company's complete enterprise cybersecurity framework is inappropriate because it is not designed to address all business objectives, assets, or non-payment risks across the enterprise.
Why not D: ISO/IEC 27001 certification can improve overall security posture but does not supersede a separate contractual PCI DSS obligation. The retailer must still meet PCI requirements for cardholder-data systems even if it pursues ISO 27001.
Common questions
What is the difference between NIST CSF and COBIT?
NIST CSF organizes cybersecurity outcomes, communicates cyber risk, and compares Current and Target Profiles. COBIT addresses broader enterprise IT governance, including business alignment, accountability, and performance monitoring.
Does ISO 27001 certification replace PCI DSS or HIPAA compliance?
No. ISO/IEC 27001 certification addresses an information security management system, while PCI DSS and the HIPAA Security Rule impose separate requirements within their applicable scopes.
Is PCI DSS a law or a framework?
PCI DSS is an industry security standard enforced through payment-card relationships and agreements, not a federal regulation. It addresses the cardholder data environment rather than the entire enterprise cybersecurity program.
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
- 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?
- When Is the NIST Cybersecurity Framework the Right Choice?
- 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.