Case 0AFB7B · GRC · L3 Applied
Test Once, Comply Many
- 01 Context
- 02 Mechanism
- 03 Lessons
What a strong answer covers
Try it out loud first. Then check yourself:
- Problem: ISO 27001, SOC 2, PCI DSS and DPDP overlap heavily; testing each separately means duplicate audits and evidence.
- A common control framework defines each control once, e.g. quarterly privileged access review, and maps it to every requirement.
- Pick a spine such as NIST SP 800-53, CIS Controls or the Secure Controls Framework; published crosswalks speed the mapping.
- Collect evidence once per control, ideally automated from systems of record, and reuse it across every audit.
- Pitfalls: mappings are rarely 1:1, scopes differ (PCI CDE vs ISMS), and a control can match the wording but miss the intent.
If the interviewer pushes back
- A new framework lands, e.g. a customer demands NIST CSF 2.0 alignment. Walk through onboarding it into your control set.
- How do you stop automated evidence collection from becoming a green dashboard that hides failing controls?