Back to Services
Compliance & GRC

Audit-Ready.
Risk-Informed.

Gap analysis, technical control testing and audit-ready evidence packs for SOC 2, ISO 27001:2022, PCI DSS v4.0, HIPAA, GDPR, India's DPDP Act 2023 and the RBI cyber security framework — delivered by people who have lived through these audits on both sides of the table.

7+ frameworks
SOC 2 · ISO · PCI · DPDP
Same VAPT engineers
test the technical controls
Evidence pack
auditor-ready, not reconstructed
Assessor liaison
through fieldwork close

Service overview

Compliance work is two jobs. The first is the mechanical exercise of mapping your existing controls against a published framework, identifying the gaps, and producing the policies, procedures and evidence pack the auditor expects. The second is the harder one — making sure the controls actually work in production rather than only on paper. AxVeil delivers both, with the technical-control testing handled by the same engineers who run our VAPT and red team practice.

Frameworks share a structural skeleton (governance, asset management, access control, vulnerability management, logging, incident response, third-party risk, cryptography, change management) but diverge in the detail. SOC 2 keys off the AICPA Trust Services Criteria; ISO 27001:2022 anchors on a documented ISMS; PCI DSS v4.0 prescribes engineering-level requirements at the cardholder-data environment boundary; HIPAA splits Privacy, Security and Breach Notification rules; GDPR and the DPDP Act 2023 govern lawful processing of personal data; the RBI direction set is prescriptive about board reporting and incident-notification timelines. We treat each one on its own terms rather than collapsing them into a single internal control catalogue and hoping for the best.

Engagements run on a single thread of evidence. Every control we test, every gap we open, every remediation we close is logged in a versioned register that both your team and the assessor can see. The IBM Cost of a Data Breach Report 2024 attributes the largest single cost-reduction effect (USD 1.88M average) to mature use of security AI and automation across detection and response — most of which is unlocked by the same controls a SOC 2 or ISO 27001 audit asks you to evidence. The compliance pack is a by-product of doing security properly, not an alternative to it.

Frameworks we cover

SOC 2 Type 1 and Type 2 AICPA Trust Services Criteria

SOC 2 reports test a service organisation's controls against five Trust Services Criteria — Security (mandatory), Availability, Processing Integrity, Confidentiality and Privacy. AxVeil readiness work begins with the AICPA TSC mapping (currently the 2017 criteria with 2022 points of focus), then walks each common-criteria control (CC1 governance through CC9 risk mitigation) into your existing tooling: identity provider, MDM, EDR, SIEM, ticketing, code-review and change-management systems.

Type 1 is a point-in-time design opinion; Type 2 covers a 6–12 month observation window and requires continuous evidence. We build the evidence-collection plumbing so that quarterly access reviews, change tickets, vulnerability scans and incident records flow into a single reviewable folder rather than being reconstructed under deadline pressure. The formal attestation is signed by a licensed CPA firm — we work alongside one you nominate, or introduce one we have collaborated with.

Reference: aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc.

ISO/IEC 27001:2022 93 Annex A controls

ISO 27001:2022 is the international standard for an Information Security Management System. The 2022 revision restructured Annex A from 114 controls in 14 domains to 93 controls grouped into four themes (organisational, people, physical, technological) and introduced 11 new controls including A.5.7 (threat intelligence), A.5.23 (information security for use of cloud services), A.8.9 (configuration management) and A.8.28 (secure coding).

Our ISO work delivers the Statement of Applicability, risk-treatment plan, ISMS scope statement, mandatory documented procedures (Clauses 4–10) and the evidence pack a Stage 1 / Stage 2 certification audit will request. Where you are transitioning from the 2013 version we map every existing control across to its 2022 successor and identify the genuinely new obligations rather than restating what you already have.

Reference: iso.org/standard/27001.

PCI DSS v4.0 Card-data environment

PCI DSS v4.0 superseded v3.2.1 in March 2024, with the future-dated requirements becoming mandatory on 31 March 2025. Notable changes include 6.4.3 (inventory and authorisation of payment-page scripts), 8.3.6 (minimum 12-character passwords or strong MFA), 11.4.7 (segmentation testing on a 12-month cycle for service providers, 24-month for merchants), 11.6.1 (change-and-tamper detection on payment pages) and the requirement for targeted risk analyses across multiple requirement families.

AxVeil delivers SAQ readiness for merchants, ROC readiness for service providers, segmentation testing, ASV-equivalent quarterly external scans and the annual internal penetration test the standard requires. Where a QSA is engaged we coordinate directly during fieldwork.

Reference: pcisecuritystandards.org/document_library.

HIPAA US healthcare PHI

The HIPAA Security Rule (45 CFR Part 164 Subpart C) prescribes administrative, physical and technical safeguards for electronic protected health information. AxVeil maps your stack against the addressable and required implementation specifications, conducts the Security Risk Analysis the rule mandates (and which OCR settlement actions consistently cite as the missing artefact), and produces the policies and procedures expected of covered entities and business associates.

We pair the documentation work with technical-control testing — access control, audit logging, integrity, transmission security, encryption — and a Breach Notification Rule incident-response playbook tuned to the 60-day notification window.

Reference: hhs.gov/hipaa/for-professionals/security.

GDPR EU Regulation 2016/679

The General Data Protection Regulation governs the processing of personal data of EU and EEA data subjects regardless of where the processor is based. Our GDPR work covers Article 30 records of processing, lawful-basis analysis, Data Protection Impact Assessments under Article 35, Data Processing Agreements with sub-processors, the Article 33 / 34 breach-notification mechanics (72-hour supervisory authority window) and Article 32 security-of-processing obligations.

We do not give legal advice — we partner with privacy counsel of your choice for the legal-interpretation work, and deliver the technical and operational artefacts that counsel and your supervisory authority will ask to see.

Reference: gdpr-info.eu.

India DPDP Act 2023 Digital Personal Data Protection Act

The DPDP Act received presidential assent in August 2023 and the operative DPDP Rules followed in 2025. The Act introduces data fiduciary / data principal terminology, consent-manager architecture, cross-border transfer controls, the Data Protection Board of India, Significant Data Fiduciary obligations, and material penalties (up to INR 250 crore per breach).

AxVeil delivers a personal-data inventory, a consent-architecture review, a cross-border transfer-mechanism mapping, a breach-notification playbook tuned to the Act's timelines, and the technical controls (encryption, access control, retention) that the rules expect. Where you also process EU personal data we map controls dual-track so one evidence pack serves both regimes.

Reference: meity.gov.in/data-protection-framework.

RBI cyber security framework Indian regulated entities

The Reserve Bank of India has published a layered direction set covering cyber security: the 2016 cyber-security framework master circular for scheduled commercial banks, the 2023 IT-governance master direction (DoS.CO.CSITEG/SEC.7/31.01.015/2023-24), and the 2024 cyber-resilience and digital-payment-security controls direction for non-bank payment-system operators. Each carries prescriptive obligations: annual VAPT, board-level cyber-security committee reporting, baseline cyber-security and resilience controls, and incident-reporting timelines.

Our work pairs gap-analysis and policy uplift with the annual VAPT and the board-format reporting the RBI inspection team will request. Aligned with the CERT-In 2022 directions on six-hour incident reporting, the cyber-incident response procedures we hand back are written to the timeline the regulator expects.

Reference: rbi.org.in/Scripts/NotificationUser.aspx.

Methodology

Five phases applied to every framework. Phases 2 and 3 are framework-specific; phases 1, 4 and 5 are common.

01
Scoping & framework alignment
Define the audit boundary (legal entity, system boundary, data types in scope), confirm the framework version (e.g. ISO 27001:2022 not 2013, PCI DSS v4.0 not v3.2.1), agree the report consumer (CPA firm, certification body, QSA, regulator).
02
Gap analysis & risk treatment
Walk every control in the framework against your current state. Issues categorised as policy-level, process-level or technical-level. Risk-treatment plan agreed with named owners and target dates.
03
Remediation & evidence build
Policy and procedure drafting, technical-control implementation support, evidence-collection plumbing (so quarterly access reviews and change-tickets flow automatically into the audit folder rather than being reconstructed under deadline pressure).
04
Technical control testing
Same engineers who run our VAPT practice exercise the controls in production: vulnerability management, logging coverage, identity controls, encryption-at-rest and in-transit, segmentation, backup integrity. Findings written into the evidence pack with CVSS where applicable.
05
Assessor / auditor liaison & retest
Walk the assessor through the evidence pack, manage fieldwork queries, close any late-stage findings, and provide a free retest of any technical issues raised during the audit. Letter of Attestation issued where applicable.

Deliverables

Gap analysis report
PDF, typically 40–80 pages. Control-by-control state of play, severity-rated gaps, risk register, remediation roadmap with named owners, target dates and effort estimates.
Policy & procedure pack
Drafted to the framework: information security policy, access-control policy, change-management procedure, incident-response plan, business-continuity plan, supplier risk procedure, secure development policy, cryptographic controls policy. Versioned in the format your DMS expects.
Technical control test results
Same finding format as a VAPT report: CVSS-rated, reproducible, with remediation steps. Mapped to the source control reference (e.g. SOC 2 CC7.1, ISO 27001 A.8.8, PCI DSS 11.4.x).
Evidence pack
A structured folder layout (one per control area) populated with the artefacts the assessor will request — screenshots, log extracts, ticket links, training records, signed acknowledgements. Pre-mapped to the assessor's evidence request list.
Board-level dashboard
Quarterly compliance posture summary, suitable for the audit committee. Tracks open findings, control coverage, residual risk and remediation velocity over time.
Assessor liaison & retest
Joint working-paper review with the CPA / certification body / QSA, defence of in-scope decisions, and one free retest of any technical findings raised during fieldwork.

Standards mapped

AICPA SOC 2 (2017 TSC)ISO/IEC 27001:2022ISO/IEC 27002:2022PCI DSS v4.0HIPAA Security Rule (45 CFR 164)GDPR (EU 2016/679)DPDP Act 2023 (India)RBI cyber security frameworkCERT-In incident-reporting directions (2022)NIST CSF 2.0NIST SP 800-53 Rev. 5

Engagement timeline

Calendar weeks for a typical SOC 2 Type 1 readiness from a low baseline. ISO 27001 first-time certification adds 4–8 weeks for ISMS documentation. SOC 2 Type 2 then requires the agreed observation window (commonly 6 months) before fieldwork.

Week 0Scoping, framework version confirmation, assessor introduction
Week 1-3Gap analysis against the full control set, risk register, remediation roadmap
Week 4-10Policy / procedure drafting, evidence-plumbing build, control-implementation support
Week 8-12Technical control testing (vulnerability management, identity, logging, segmentation)
Week 12-14Internal audit / readiness review, evidence-pack finalisation
Week 14-16Assessor fieldwork, working-paper queries, late finding closure

Frequently asked questions

Are you a licensed CPA firm that can sign a SOC 2 report?+

AxVeil is a security firm, not a CPA firm. The AICPA reserves the issuance of the formal SOC 2 attestation report for licensed CPAs. We partner with CPA firms to deliver the technical-control testing, evidence collection, control mapping and readiness work that the CPA relies on; we then sit alongside the CPA through fieldwork. If you do not have a CPA partner we will introduce two we have worked with previously.

Difference between SOC 2 Type 1 and Type 2?+

Type 1 is a point-in-time opinion: are the controls designed appropriately, and are they in place on a specified date? It typically takes 6–10 weeks once readiness is complete. Type 2 is an opinion over an observation period — most commonly 6 to 12 months — that the controls operated effectively across that window. Type 2 requires continuous evidence (ticket trails, log retention, access reviews) that AxVeil helps you set up during readiness.

How does ISO 27001:2022 differ from the 2013 version we are already certified against?+

ISO 27001:2022 restructures Annex A from 114 controls in 14 domains down to 93 controls in 4 themes (organisational, people, physical, technological), introduces 11 new controls (notably A.5.7 threat intelligence, A.5.23 information security for use of cloud services, A.8.9 configuration management, A.8.28 secure coding) and tightens documentation around the ISMS. Existing certificate holders had a transition window closing in October 2025; new certifications now issue against the 2022 standard.

Do you cover the new PCI DSS v4.0 requirements that became mandatory in 2025?+

Yes. The future-dated PCI DSS v4.0 requirements that moved from best practice to mandatory on 31 March 2025 — including 6.4.3 (payment-page script management), 8.3.6 (12-character passwords / strong MFA), 11.4.7 (segmentation testing) and the targeted-risk analyses across requirements 5, 7, 8, 10 and 12 — are covered in our v4.0 readiness and assessment work.

Where does India's DPDP Act 2023 sit relative to GDPR?+

The Digital Personal Data Protection Act 2023 borrows the structural skeleton of GDPR (data fiduciary / data principal terminology, consent obligations, breach notification, cross-border transfer rules) but diverges meaningfully on lawful bases (no legitimate-interest equivalent), consent-manager architecture, the role of the Data Protection Board, and significant data fiduciary obligations. We map controls dual-track so a single evidence pack covers both regimes where possible.

Can you align with the CERT-In and RBI requirements that apply to Indian regulated entities?+

Yes. The RBI cyber security framework (the 2016 master direction for banks, plus the 2023 IT-governance master direction, plus the 2024 cyber-resilience direction for non-bank PSOs) carries specific annual VAPT, board reporting and incident-notification obligations. Our compliance work pairs the gap-analysis and policy uplift with VAPT and board-level reporting in the prescribed format. The CERT-In 2022 directions on incident reporting (six-hour timeline) are folded into the incident-response procedures we hand back.

Map your audit path

Send the framework, the report consumer (CPA firm, certification body, QSA, regulator) and your target audit date. We respond with a fixed-fee proposal, a redacted evidence pack from a comparable engagement, and an introduction to an assessor if you need one.

Request a readiness call →