An IT compliance administrator at a healthcare technology organization is configuring an integrated cloud application. The system manages patient clinical records, processes patient credit card co-payments, and handles registration details for European Union (EU) residents enrolled in international medical trials.
Which of the following regulatory compliance controls MUST the administrator implement to simultaneously satisfy PCI-DSS and GDPR requirements? (Select TWO.)
- Isolate the billing sub-network to prevent the post-authorization storage of Sensitive Authentication Data (SAD), such as CVV2/CVC security codes.Answer
- Implement technical mechanisms that allow EU trial participants to request data portability and provide explicit consent before processing their personal records.Answer
- CStore encrypted credit card CVV2 security codes within the primary health records database for recurring co-pays, provided AES-256 encryption is applied at rest.
- DEnforce HIPAA Privacy Rule procedures to govern payment card processing for all patient transactions, replacing PCI-DSS requirements in medical settings.
Answer
The administrator must isolate the billing processing environment to prevent post-authorization storage of Sensitive Authentication Data (CVV2/CVC) in accordance with PCI-DSS, and implement consent and data portability mechanisms for EU trial participants as required by GDPR.
Adhering to regulatory requirements across multi-functional applications requires respecting the boundaries of each framework. PCI-DSS mandates that Sensitive Authentication Data (CVV2/CVC codes) must never be stored after payment authorization. Simultaneously, GDPR mandates explicit consent and structural mechanisms supporting rights like data portability for EU residents' personal data.
Step-by-Step Solution
Key Concept
Multi-Framework Regulatory Compliance (PCI-DSS & GDPR)