ISC · Security and Confidentiality and Privacy · 9 practice questions
Do NIST CSF and ISO 27001 Satisfy HIPAA or PCI DSS?
Framework alignment, certification, and control mappings do not by themselves establish HIPAA or PCI DSS compliance. Below: judge management's proposed compliance conclusions against the requirements that actually bind the company.
Try one first
Hint
Separate the role of a voluntary framework or standard from the role of an actual law or regulation.
Answer C. Voluntary frameworks and standards like the NIST Cybersecurity Framework help organize and improve security programs but do not replace statutes, regulations, or contract obligations. Compliance requires identifying applicable legal requirements (e.g., specific data-protection, breach-notification, or sectoral rules) and meeting those requirements; adopting a framework may support but does not automatically satisfy them.
Why not A: This is tempting because NIST CSF is well respected, but recognition does not convert a voluntary framework into legal compliance. Laws frequently require specific notices, processes, or controls beyond what mere adoption of a framework guarantees.
Why not B: Good governance (documentation and reviews) is valuable evidence of diligence, but it does not by itself satisfy legal requirements that may mandate particular safeguards, reporting, or substantive controls.
Why not D: ISO 27001 is an international standard and certification can strengthen a control environment, but certification or adopting a standard does not automatically meet all legal or regulatory obligations.
What should you do?
The situation
Harbor Clinic is a HIPAA covered entity that maintains electronic protected health information and stores patient cardholder data. Its merchant agreement requires PCI DSS compliance. Harbor adopts NIST CSF, obtains ISO 27001 certification, and completes a controls crosswalk to HIPAA and PCI DSS. No applicable law or contract recognizes these steps as substitutes for compliance. Management has not evaluated whether Harbor actually meets each regime's requirements.
Evaluate HIPAA and PCI DSS requirements directly, using the framework, certification, and crosswalk as support.
Best HIPAA and the merchant agreement impose separate obligations. None of Harbor's organizing or certification steps establishes compliance by itself.
Declare compliance with both regimes because Harbor aligned its program to NIST CSF.
Wrong NIST CSF organizes cybersecurity risk management. Alignment does not establish that Harbor meets HIPAA or PCI DSS requirements.
Use ISO 27001 certification instead of separate HIPAA and PCI DSS compliance evaluations.
Wrong Certification supports the security program but does not replace either regime's specific requirements.
Declare compliance because the completed crosswalk links Harbor's controls to both regimes.
Wrong The crosswalk documents alignment. It does not demonstrate that Harbor actually satisfies the mapped requirements.
Evaluate HIPAA only because PCI DSS is an industry standard rather than federal law.
Wrong Harbor's merchant agreement requires PCI DSS compliance. Contractual obligations remain binding despite framework alignment or certification.
Key points
- Remember: A framework organizes the program; HIPAA and the merchant agreement determine what the company must satisfy.
- PCI DSS can be contractually mandatory even though it is not a federal regulation.
- NIST CSF alignment and ISO 27001 certification remain useful without replacing direct HIPAA and PCI DSS evaluations.
How the exam traps you
- Treating NIST CSF alignment or ISO 27001 certification as automatic compliance. Evaluate the applicable HIPAA and PCI DSS requirements directly.
- Treating a completed crosswalk as proof that mapped obligations are satisfied. A crosswalk shows alignment, not whether the company actually meets each requirement.
- Calling PCI DSS optional because it is an industry standard. The company's merchant agreement makes PCI DSS binding.
Question 2
Hint
Think in three categories: legal/regulatory obligations (HIPAA), industry/contractual standards (PCI DSS), and voluntary frameworks or attestations (NIST CSF, ISO 27001, SOC 2); which apply directly to MediHost?
Answer C. Because the stem explicitly identifies MediHost as a HIPAA business associate, it is directly subject to the HIPAA Security Rule for the ePHI it handles. The stem also states MediHost is in scope for PCI DSS, so PCI obligations apply to its cardholder-data environment. Voluntary frameworks and attestation reports (NIST CSF, ISO 27001, SOC 2) can structure controls and provide assurance but do not by themselves replace legal or industry-specific requirements.
Why not A: This is tempting because ISO 27001 and NIST CSF overlap with many HIPAA and PCI control objectives and can make compliance easier. It is wrong because those are voluntary frameworks or standards and cannot legally substitute for the specific regulatory and industry requirements of the HIPAA Security Rule or PCI DSS.
Why not B: This distractor tempts because candidates often conflate 'covered entities' with the idea that only providers are regulated. It fails because business associates are separately required to comply with HIPAA when they create, receive, maintain, or transmit ePHI under contract; PCI DSS does not eliminate HIPAA obligations.
Why not D: This distractor tempts because SOC 2 provides third-party assurance about controls and is commonly requested by customers. It fails because a SOC 2 report is an attestation framework, not a legal or industry-specific standard, and does not by itself satisfy HIPAA or PCI DSS obligations.
Question 3
Hint
Identify which external authorities impose mandatory controls for the in‑scope portal and whether they allow compensating measures.
Answer A. NIST CSF and ISO/IEC 27001 are frameworks and certification schemes that help an organization structure and document its security program, but they do not relieve the organization of specific binding external obligations. Because both the state regulation and the contract‑incorporated industry standard expressly require MFA for privileged remote access and do not allow compensating controls, Orion must implement MFA for the in‑scope portal. Orion should map and document the mandated control within its chosen frameworks to demonstrate compliance.
Why not B: This is tempting because NIST CSF supports risk-based tailoring and compensating controls, but incorrect here: an express external requirement that mandates MFA and disallows alternatives cannot be set aside by internal risk acceptance alone.
Why not C: This plays on the misconception that only laws create obligations; in reality, a contract that Orion has agreed to and that incorporates an industry standard creates binding contractual obligations that must be observed unless the contract allows deviation.
Why not D: This is tempting because certification shows an implemented ISMS, but ISO/IEC 27001 certification does not automatically satisfy a distinct regulatory or contractual mandate that prescribes a specific control and disallows alternatives.
Question 4
Hint
Distinguish voluntary control frameworks and third‑party services from obligations that are defined by statute, regulation, or contract; consider what duties can remain after outsourcing a payment function.
Answer C. The NIST Cybersecurity Framework is a voluntary control framework that supports design and maturation of a security program but does not by itself resolve statutory, regulatory, or contractual obligations. Whether the GLBA Safeguards Rule (and related FTC enforcement) applies depends on whether the company meets the regulatory definition of a 'financial institution' or otherwise falls under FTC jurisdiction; that legal assessment is independent of adopting NIST. Likewise, outsourcing payment processing can reduce direct PCI DSS scope but does not automatically eliminate merchant responsibilities such as vendor oversight, contractual attestation requirements, or obligations related to any retained cardholder data.
Why not A: This is attractive because outsourcing often reduces direct PCI scope, but it overstates the effect: merchants commonly retain obligations (for example, oversight of the processor, network segmentation, tokenization exceptions, or responsibilities for any retained cardholder data) and should not treat external requirements as merely internal policy choices.
Why not B: This is tempting because candidates may equate 'not a bank' with no GLBA/FTC obligations, but nonbank entities can still fall within the Safeguards Rule or FTC jurisdiction depending on their activities; adopting a voluntary framework does not by itself determine statutory or contractual applicability.
Why not D: This distractor is plausible because ISO 27001 evidences a mature ISMS, but certification alone does not automatically satisfy specific statutory, regulatory, or contractual obligations such as the GLBA Safeguards or PCI DSS; those obligations require separate assessment and controls.
Question 5
Hint
Ask whether framework alignment 'supports' compliance or actually 'replaces' specific legal requirements, focus on the deletion-request obligation.
Answer A. Voluntary frameworks like the NIST CSF can provide persuasive evidence that an organization has a structured security program and reasonable safeguards. However, they do not automatically satisfy specific statutory or regulatory obligations; because North Peak has not separately evaluated whether its deletion-request process meets the law's timing and documentation requirements, the company could still be noncompliant despite framework alignment.
Why not B: Tempting because recognized frameworks signal mature controls and broad laws can seem satisfied by best practices. It fails because the stem explicitly states the law does not treat framework use as automatic compliance, and framework alignment alone does not address discrete obligations like deletion-request timing and documentation.
Why not C: Tempting because legal compliance is ultimately determined by statutes and regulations. It fails because voluntary frameworks often provide relevant, persuasive evidence about how safeguards are implemented and whether they are reasonable, useful in an assessment even though they do not by themselves determine compliance.
Why not D: Tempting because regulators frequently recognize framework alignment when evaluating programs. It fails because regulators and laws can enforce specific operational requirements (for example, timing and documentation for deletion requests) regardless of framework alignment; lack of exact prescribed wording does not make such gaps immaterial.
Question 6
Hint
Distinguish an industry security standard from a legal privacy regime, and consider which GDPR obligations (e.g., lawful basis, data‑subject rights, DPIA) are commonly implicated by profiling/targeted marketing.
Answer B. PCI DSS is an industry standard focused on payment‑card security and can support technical controls (encryption, access controls, logging). GDPR is a broader legal regime that imposes additional obligations tied to personal‑data processing, such as lawful basis, data‑subject rights, purpose limitation, retention, and potential DPIAs for profiling, so the new marketing/analytics activity requires a GDPR‑focused analysis even if some PCI DSS controls are present.
Why not A: Tempting because both aim to protect data, but incorrect: GDPR is a legal framework with obligations (lawful basis, rights, purpose/retention limits, DPIAs) that PCI DSS does not address; technical card‑security controls do not automatically fulfill those legal privacy requirements.
Why not C: Tempting because PCI DSS focuses on cardholder data, but incorrect: GDPR applies to personal data generally, not only payment cards; targeted marketing and analytics processing of other personal data can still trigger GDPR obligations regardless of whether full card numbers are stored.
Why not D: Tempting because GDPR is statutory law, but incorrect: GDPR does not negate industry or contractual obligations like PCI DSS where they remain applicable; organizations must consider both legal requirements and applicable industry standards, which may apply concurrently.
Question 7
Hint
Distinguish which obligations are legally or contractually binding from which frameworks, certifications, or attestations are options for implementing or demonstrating controls.
Answer A. The first step is to determine which laws and contracts actually apply and the scope of those obligations, given the facts, CloudCo will likely be subject to HIPAA business‑associate obligations for ePHI and to PCI DSS for payment card processing. Frameworks, certifications, and attestations (for example, NIST CSF, NIST SP 800‑53, ISO 27001, SOC 2) are tools to organize and demonstrate controls but do not themselves create legal or contractual requirements. Therefore management should map binding obligations to an appropriate framework, perform a gap assessment, and prioritize remediation.
Why not B: This is tempting because SP 800‑53 is comprehensive and may strengthen security, but an individual customer's question does not make SP 800‑53 legally required. Implementing the entire federal control catalog without scoping can be unnecessary or misaligned with CloudCo's actual legal and contractual obligations.
Why not C: ISO 27001 can provide a structured ISMS and market signal, but certification to a voluntary standard does not automatically satisfy the specific scoping, control, and evidence requirements of HIPAA or PCI DSS.
Why not D: SOC 2 Type II attestation can build customer trust about controls against selected criteria, but it does not replace the need to identify and implement controls required by law or contract and does not itself determine legal scope.
Question 8
Hint
Ask whether the same test scope, evidence content, and frequency can automatically satisfy every mapped requirement.
Answer C. Cross-mapping is an efficiency tool: one control and its evidence can support multiple mapped requirements. However, HIPAA and PCI DSS impose distinct applicability, acceptance criteria, evidence types, and sometimes testing frequencies, so the organization must verify that the control's design and the specific test performed meet each requirement's criteria.
Why not A: Tempting because a single test can yield evidence relevant to multiple mappings; incorrect because a passing test only proves compliance for a requirement if the test's scope, evidence content, and timing satisfy that requirement, a one-size-fits-all test often will not.
Why not B: Tempting to those who view NIST CSF as comprehensive; incorrect because NIST CSF is a voluntary, high-level framework that helps prioritize risk but does not replace or automatically satisfy the specific, enforceable obligations and evidence expectations of HIPAA or PCI DSS.
Why not D: Tempting because the standards differ in emphasis; incorrect because a well-designed control can support multiple mapped requirements if the organization ensures the control's design and testing meet each requirement's criteria, separate implementations are not inherently required.
Question 9
Hint
First decide whether Blue Mesa falls within HIPAA's scope as a business associate, then evaluate whether a voluntary framework can replace a legal/regulatory obligation or only help support it.
Answer A. As a business associate handling ePHI, Blue Mesa is directly subject to the HIPAA Security Rule. ISO 27001 can be a useful framework for structuring controls and evidence, but it is a voluntary standard and does not replace HIPAA's legal requirements (for example, performing a security risk analysis and implementing required safeguards). Blue Mesa must ensure its program maps to and satisfies HIPAA-specific obligations.
Why not B: This is tempting because HIPAA is commonly associated with covered entities such as providers and plans. However, business associates that create, receive, maintain, or transmit ePHI on behalf of covered entities are themselves subject to applicable HIPAA Security Rule requirements.
Why not C: This distractor tempts by combining two true but separate facts: BAAs are required and ISO certification supports security. It fails because contractual arrangements and certification do not substitute for meeting specific HIPAA obligations; Blue Mesa must implement and document HIPAA-required risk analyses and safeguards regardless of contracts or certification.
Why not D: This is tempting because ISO 27001 and HIPAA overlap on risk management and controls. However, ISO 27001 is a voluntary international standard and may not address HIPAA-specific implementation specifications or legal requirements; certification alone does not demonstrate full HIPAA compliance.
Common questions
Does adopting NIST CSF make a company HIPAA compliant?
No. NIST CSF can organize the security program, but the company must still evaluate whether its controls meet applicable HIPAA Security Rule requirements.
Does ISO 27001 certification replace PCI DSS compliance?
No. ISO 27001 certification does not by itself satisfy PCI DSS obligations imposed through the company's merchant agreement.
Does a NIST crosswalk prove HIPAA and PCI DSS compliance?
No. A crosswalk connects controls to requirements, but the company must still establish that it meets the applicable HIPAA and PCI DSS requirements.
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
- 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.