Home  /  Compliance
Practice

Compliance, without the audit fatigue.

SOC 2 (TSC), ISO/IEC 27001:2022, and PCI DSS 4.0 mapped against a single unified control set — so the work you do for one auditor pays out across all three. We focus on whether the controls actually defend the business, not just whether the binder is thick.

SOC 2 Type 1 & Type 2 ISO/IEC 27001:2022 PCI DSS 4.0 Pre-audit gap assessment Look-back simulation
Layered compliance architecture in blue and lime
Unified compliance strategy

Map once. Comply many.

A representative slice of how the major frameworks overlap when you're looking at them from a control perspective rather than a checklist perspective.

Control mapping and audit traceability grid
Domain SOC 2 (TSC) ISO 27001:2022 (Annex A) PCI DSS 4.0 Representative Evidence
Access Control CC6.1 / CC6.2 A.5.15 / A.8.2 / A.8.3 Req. 7 / 8 IAM roles, MFA enforcement, JML evidence
Physical & Environmental CC6.4 A.7.2 / A.7.4 / A.8.25 Req. 9 Biometrics, mantrap, CCTV, UPS / generator logs
System Operations CC7.1 / CC7.2 A.8.15 / A.8.16 Req. 10 SIEM correlation, 24/7 NOC tickets, log retention
Change Management CC8.1 A.8.32 Req. 6 Pull-request approvals, CAB minutes, rollback plans
Cryptography CC6.7 A.8.24 Req. 3 / 4 HSM/KMS configs, TLS profiles, key rotation logs
Vulnerability Mgmt CC7.1 A.8.8 Req. 11 Scan cadence, ASV reports, remediation SLAs
Incident Response CC7.3 / CC7.4 A.5.24 — A.5.28 Req. 12.10 IR runbooks, tabletop minutes, post-mortems
Vendor / TPRM CC9.2 A.5.19 — A.5.22 Req. 12.8 Vendor inventory, SOC 2s on file, DPAs
Asset Mgmt & Disposal CC6.5 A.5.9 / A.8.10 Req. 9.4 CMDB extracts, certificates of destruction

Illustrative mapping. Final mapping depends on auditor opinion, system boundary, and applicable inclusions / exclusions.

SOC 2 (TSC)

Trust Services Criteria — built on what your customers ask anyway.

SOC 2 reports against the AICPA Trust Services Criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy). It's the de-facto US B2B trust artifact. We help you choose the right TSCs for your story, scope the boundary defensibly, and avoid the classic over-scoping trap that turns a 6-month report into an 18-month one.

  • Readiness assessment against current TSCs & common-criteria points of focus
  • Type 1 vs. Type 2 sequencing — and a realistic look-back calendar
  • Auditor selection support; we don't sell the audit, we sell the readiness
  • Bridge letter strategy and customer-facing trust narrative

What we deliver

A SOC 2 readiness package that makes the auditor's job small.

  • System Description draft (the most-skipped, most-painful artifact)
  • Control matrix with evidence owners and cadence
  • Policy stack reviewed for "say what you do, do what you say"
  • Mock-audit walkthroughs with each control owner
  • Risk register, vendor list, and IR runbook in audit-ready form

ISO 27001:2022 — what changed

The 2022 revision restructured Annex A from 14 categories into 4 themes (Organizational, People, Physical, Technological), trimmed to 93 controls, and added 11 new ones. The transition window from 27001:2013 closed in October 2025, so 2022-only is the only option going forward.

  • New controls of note: threat intelligence, ICT readiness for BC, data masking, secure coding, web filtering, cloud services security
  • Statement of Applicability rewritten with new control IDs and explicit mapping
  • Risk assessment refreshed against the 2022 control set
ISO/IEC 27001:2022

An ISMS that an executive can actually narrate.

Most ISO certifications fail their first surveillance audit because the ISMS exists on paper but not in the company's habits. We build (or retrofit) yours so leadership reviews, internal audits, risk reviews, and control owners all reinforce each other on a real cadence — not a calendar fire-drill.

  • Gap analysis against Annex A 2022 with prioritized remediation
  • SoA, risk treatment plan, and management review pack
  • Internal audit program and corrective-action workflow
  • Stage 1 / Stage 2 dress rehearsal with the certification body's lens
PCI DSS 4.0

4.0 is here, and "customized approach" rewards mature programs.

PCI DSS 4.0.1 is now mandatory for all assessments, and the future-dated "best practice" requirements have transitioned to in-effect. The biggest shift isn't a single requirement — it's that 4.0 lets mature programs use a Customized Approach with documented Targeted Risk Analyses (TRAs), instead of brute-force defined-approach checkboxes.

  • Scope reduction strategy — segmentation, tokenization, P2PE, SAQ eligibility
  • Targeted Risk Analysis templates for customized-approach controls
  • Authenticated scanning and ASV coordination
  • Self-assessment (SAQ) selection and merchant-level confirmation

Common 4.0 pitfalls we catch early

  • Phishing-resistant MFA expectations being missed for admin access
  • Inventory of bespoke and custom software (R6.3.2) treated as an afterthought
  • E-commerce script integrity (R6.4.3, R11.6.1) not actually instrumented
  • Targeted Risk Analyses written but never reviewed at the cadence they specify
  • Cryptographic inventories that ignore where keys actually live (HSM vs. workstation .pem files)
Engagement model

30-day strategic compliance assessment.

Designed to surface material issues before the official look-back window opens — not after.

Phase 1 — Scope finalization & access

Week 1. Stakeholder alignment, prior audit reports, system boundary, applicable framework version, and explicit inclusions / exclusions documented. Everything starts here.

Phase 2 — Workpaper review, SME interviews, gap matrix

Weeks 2–3. We work the actual evidence, not the policy library. SME interviews with control owners, evidence sampling, and a gap matrix mapped to your frameworks of record.

Phase 3 — Field assessment & report

Week 4. Tactical site / system assessment focused on the highest-risk controls. Deliverable: unified control map + red-flag report with ranked remediation paths and owners.

Not a substitute for a formal audit with random sampling and evidence generation. The intent is overall completeness, stability, and audit-readiness — surface issues now, while you can still fix them.

Next step

What does your audit calendar look like?

Tell us your reporting period and target frameworks. We'll tell you what's realistic, what's risky, and where the cheap wins are hiding.

Talk through your roadmap