Compliance Architecture

Designing for PCI DSS, SOC 2, ISO 27001, GDPR/DPDP, HIPAA and DORA: scoping, control mapping, evidence automation and continuous compliance.

Common frameworks

Framework Scope Architecture implications
PCI DSS v4.0.1 Cardholder data Minimize scope (tokenization, hosted payment fields), segmentation, MFA, logging, vulnerability management
SOC 2 (Trust Services Criteria) Service organizations' controls Access control, change management, monitoring, evidence collection
ISO/IEC 27001:2022 Information security management system Risk-based controls (Annex A), policies, continual improvement
GDPR / DPDP Act Personal data Privacy by design, rights handling, residency, DPIAs
HIPAA US health data Access controls, audit, encryption, BAAs with vendors
DORA (EU, applies from Jan 2025) Financial sector ICT resilience ICT risk management, incident reporting, resilience testing, third-party risk
EU AI Act AI systems by risk category Risk management, transparency, human oversight for high-risk AI

Scoping strategy (PCI example)

flowchart LR
  B[Browser] -->|card entered in PSP-hosted iframe| PSP[Payment service provider]
  PSP -->|token| SHOP[Merchant backend<br/>out of card-data scope]
  SHOP --> DB[(Orders DB: tokens only)]
  subgraph CDE [Cardholder data environment: minimized]
    PAYSVC[Payment service<br/>separate account/VPC]
  end
  SHOP --> PAYSVC --> PSP

Continuous compliance

  • Map controls to technical implementations once (control library), reuse across frameworks.
  • Policy as code in cloud (guardrails) and CI (security checks).
  • Automated evidence collection (Drata, Vanta, Secureframe, cloud audit managers) instead of screenshots.
  • Compliance dashboards with control health; findings as tickets with owners.

Interview questions and answers

How do you reduce PCI DSS scope for an e-commerce site?

Never let card data touch your systems: use PSP-hosted payment pages or fields, store only tokens, segment any remaining payment components, and keep the cardholder data environment as small as possible. Scope then reduces to the self-assessment for merchants using outsourced payment pages (e.g. SAQ A), subject to your acquirer's requirements.