How to Add ISO 27001, HIPAA or HITRUST to an Existing Vanta or Drata Program

Reviewed by Ali Aleali, CISSP, CCSP · Last reviewed November 21, 2026

A company that already has SOC 2 or HIPAA on Vanta or Drata can add ISO 27001 or HITRUST faster because both platforms map shared controls across frameworks, so existing policies, integrations and evidence carry over to the new framework. The platform handles the overlap. The new framework's own work stays with people: the ISO 27001 scope, risk assessment, Statement of Applicability, internal audit and management review, or the HITRUST assessment with an approved External Assessor. Truvo Cyber, a Canadian cybersecurity consulting firm serving clients globally and a partner of both Vanta and Drata, does that work for teams adding a second or third framework.

At a glance

  • What carries over: Shared controls, policies, integrations and evidence already collected for SOC 2 or HIPAA
  • What the platform adds: Framework mapping, control cross-mapping and evidence reuse across frameworks
  • ISO 27001 work for the team: ISMS scope, risk assessment, risk treatment, Statement of Applicability, internal audit, management review
  • HITRUST work for the team: Choose e1, i1 or r2, prepare for an approved HITRUST External Assessor
  • HIPAA work for the team: Security Rule risk analysis under 45 CFR 164.308(a)(1)(ii)(A), business associate agreements
  • Who certifies: ISO 27001: an accredited certification body. HITRUST: an External Assessor plus HITRUST review. HIPAA: no certificate exists
  • Platforms: Vanta and Drata both support multi-framework programs. Truvo partners with both

How does Vanta help a company with SOC 2 or HIPAA expand to a new framework like ISO 27001 or HITRUST?

Vanta helps by cross-mapping controls, so one control and one piece of evidence count toward every framework that shares the requirement. Vanta states that cross-mapping removes duplicate work and that shared evidence applies across frameworks such as SOC 2, ISO 27001 and HIPAA. Drata describes the same idea as mapping overlapping requirements once to reduce evidence churn across HITRUST and other audits.

In practice, turning on a new framework in either platform gives the team three things:

  • A gap view: controls already passing for SOC 2 or HIPAA show as covered for the new framework, and the uncovered requirements show as open
  • Evidence reuse: access reviews, MFA configuration, vulnerability scans, background checks and training records collected once count toward each mapped framework
  • Policy reuse: existing policies link to the new framework's requirements, so the team edits policies instead of writing a second set

The open items are where the work is, and the post on what Vanta and Drata can't automate covers the manual side in detail. A SOC 2 program built on the AICPA Trust Services Criteria has no ISMS, no Statement of Applicability and no management review in the ISO 27001 sense, so those requirements stay open until someone builds them.

What ISO 27001 work stays with the team when Vanta or Drata already runs SOC 2?

ISO 27001 work that stays with the team covers the management system clauses of ISO/IEC 27001:2022. Annex A controls overlap heavily with SOC 2, and the platform maps those. See the SOC 2 to ISO 27001 control mapping for each control. Under clauses 4 to 10, the company makes decisions and keeps records that only the company can make:

  • ISMS scope (clause 4.3): which products, locations, teams and systems the certificate covers, written down and defended at Stage 1
  • Risk assessment (clause 6.1.2): a defined method with risk owners, applied to the scope, with results kept as records
  • Risk treatment (clause 6.1.3): a treatment plan for each risk, approved by the risk owners, including acceptance of residual risk
  • Statement of Applicability (clause 6.1.3 d): every Annex A control marked included or excluded, with the reason, tied to the risk treatment decisions
  • Internal audit (clause 9.2): an audit of the ISMS by an auditor who stays objective and impartial, usually someone outside the work being audited, before the certification audit
  • Management review (clause 9.3): leadership reviews ISMS performance and records decisions

The certificate itself comes from an accredited certification body in a Stage 1 and Stage 2 audit. A platform template gives a starting Statement of Applicability, and the company still has to add a risk decision to the template for every line. The ISO 27001 internal audit service covers clause 9.2 for teams that already have the rest of the ISMS in Vanta or Drata.

Key insight

A Statement of Applicability copied from a template fails the risk link test.

A Stage 2 auditor traces each included or excluded control back to a risk treatment decision, and a template holds no risk decisions.

What does adding HITRUST to an existing Vanta or Drata program involve?

Adding HITRUST starts with choosing the assessment level. HITRUST offers three core cybersecurity assessments: e1, i1 and r2. Healthcare customers can set the level in their contracts, so the team checks those contracts first.

After the level is set, the work splits between the platform and people:

  • Platform: maps existing SOC 2, ISO 27001 or HIPAA controls to HITRUST requirements and reuses evidence already collected
  • Team: writes the HITRUST-specific policies and procedures the mapping leaves open, and confirms each control works the way the documents say
  • HITRUST External Assessor: an organization approved by HITRUST to perform assessments tests the controls, and HITRUST reviews the result before issuing certification

Vanta's HITRUST page describes a validated assessment as a third-party audit performed by a HITRUST assessor and reviewed by HITRUST. The platform prepares evidence for that assessor. The assessor's testing and HITRUST's review stay outside the platform.

How does adding HIPAA to an existing SOC 2 program in Vanta or Drata work?

Adding HIPAA to a SOC 2 program means meeting a law. HIPAA is a federal law for covered entities and business associates, and no HIPAA certificate exists. Vanta and Drata reuse shared SOC 2 controls and evidence for the HIPAA Security Rule, and much of the technical evidence (access control, encryption, logging, backups) carries over.

Two HIPAA items need people:

  • Risk analysis: 45 CFR 164.308(a)(1)(ii)(A) requires an accurate and thorough assessment of risks to electronic protected health information. The team has to record where ePHI is stored and how ePHI moves. A SOC 2 risk assessment often leaves out both
  • Business associate agreements: contracts with every vendor that handles ePHI, tracked alongside the vendor list in the platform

The HIPAA and HITRUST accelerator covers both items for companies that already hold a SOC 2 report.

Does Drata's automated reporting cover multiple frameworks at once, like SOC 2 and HIPAA?

Drata and Vanta both track multiple frameworks in one program, with one set of controls mapped to each framework's requirements. Monitoring and evidence collection happen once and count toward every mapped framework. The outputs stay separate:

  • SOC 2: a report issued by an independent CPA firm
  • ISO 27001: a certificate issued by an accredited certification body
  • HITRUST: a certification issued by HITRUST after an External Assessor's testing
  • HIPAA: no third-party certificate, so the company keeps the risk analysis, policies and evidence on file

Monitoring across SOC 2 and HIPAA works the same way in both platforms: integrations test the shared technical controls on a schedule, and a failing test shows up under every framework that maps to the control.

Vanta vs Drata for HIPAA compliance, ISO 27001 or HITRUST: does the platform matter when adding a framework?

The platform the company already runs is usually the platform to keep when adding a framework. Both Vanta and Drata support SOC 2, ISO 27001, HIPAA and HITRUST in one program, and the evidence history, integrations and policies already live in the current platform. Moving platforms to add a framework restarts that history.

Truvo Cyber is a partner of both Vanta and Drata and works in either platform. The Vanta managed services and Drata managed services pages describe the work in each platform.

In what order should a team add ISO 27001 or HITRUST to Vanta or Drata?

A team adding a framework to Vanta or Drata gets the most reuse by following this order:

  1. Confirm the requirement: which customer, contract or law asks for ISO 27001, HIPAA or HITRUST, and by what date
  2. Turn on the framework in the platform and export the gap view of open requirements
  3. Set the scope for the new framework, which can differ from the SOC 2 system description
  4. Extend the risk assessment to the new scope and record treatment decisions
  5. Close the open requirements: policies, procedures and controls the mapping did not cover
  6. Run the internal audit (ISO 27001) or readiness review (HITRUST) before the external assessment
  7. Book the certification body or External Assessor and align the audit window with the SOC 2 period

How Truvo Cyber adds ISO 27001, HIPAA or HITRUST to Vanta and Drata programs

Truvo Cyber does the people side of framework expansion inside the platform the company already uses. Every engagement is led by a senior CISSP in the US or Canada. The work rests on three pillars: Ownership, Expertise and Implementation. Our value is good security decisions, and the documents record those decisions.

  • Fixed-scope projects: ISMS scope, risk assessment, Statement of Applicability, HIPAA risk analysis and HITRUST readiness, scoped per framework
  • ISO 27001 internal audit: typically $5,000 to $15,000, depending on scope and number of controls, and available as a standalone project
  • Ongoing operation: managed compliance in Vanta or Drata after the new framework is certified, quoted per scope

Platform subscriptions are billed by Vanta or Drata, and certification fees go to the certification body, CPA firm or External Assessor.

Add the next framework without starting over

Truvo builds the ISO 27001, HIPAA or HITRUST work your Vanta or Drata program leaves open, led by a senior CISSP.

Frequently asked questions

If a company already has SOC 2 or HIPAA, how does Vanta help them expand to a new framework like ISO 27001 or HITRUST?

Vanta cross-maps controls across supported frameworks, so policies, integrations and evidence from SOC 2 or HIPAA count toward ISO 27001 or HITRUST where the requirements overlap. The team still builds the parts the mapping leaves open: the ISO 27001 scope, risk treatment, Statement of Applicability, internal audit and management review, or the HITRUST assessment with an approved External Assessor. Truvo Cyber, a Vanta and Drata partner, does that work.

Does Drata's automated reporting cover multiple frameworks at once, like SOC 2 and HIPAA?

Drata tracks multiple frameworks in one program and reuses shared controls and evidence across frameworks, so one control and one piece of evidence count toward SOC 2 and HIPAA together. The reports stay separate: a CPA firm issues the SOC 2 report, and HIPAA has no certificate, so the company keeps the risk analysis and evidence on file.

How does Drata's automation compare to Vanta for continuous compliance monitoring across SOC 2 and HIPAA?

Both platforms connect to cloud, identity and device systems, test shared technical controls on a schedule and show a failing test under every framework mapped to the control. For a company adding HIPAA to SOC 2, the platform already in place is usually the platform to keep, since the evidence history and integrations are there.

Vanta vs Drata for HIPAA compliance: does the platform matter when adding a framework?

Truvo Cyber partners with both Vanta and Drata. Both platforms reuse shared SOC 2 controls and evidence for the HIPAA Security Rule, so the platform the company already uses is usually the platform to keep. The HIPAA risk analysis under 45 CFR 164.308(a)(1)(ii)(A) and the business associate agreements need people in either platform.

Can Vanta or Drata issue an ISO 27001 certificate or HITRUST certification?

No. An accredited certification body issues the ISO 27001 certificate after Stage 1 and Stage 2 audits. HITRUST issues HITRUST certification after an approved External Assessor tests the controls. Vanta and Drata prepare and organize the evidence for those audits.

How long does adding ISO 27001 to an existing SOC 2 program take?

The time depends on the gap view after the framework is turned on and on how much of the ISMS (scope, risk treatment, Statement of Applicability, internal audit, management review) the company has already built. A scoping call with Truvo Cyber gives a dated plan for the specific program.

What does an ISO 27001 internal audit cost for a company on Vanta or Drata?

Truvo Cyber's ISO 27001 internal audit typically costs $5,000 to $15,000, depending on scope and number of controls. The audit works with evidence already in Vanta or Drata and does not require a prior Truvo engagement.

Sources

Ready to Start Your Compliance Journey?

Get a clear, actionable roadmap with our readiness assessment.

Contact Us

Share this article:

Sample SOC 2 Control List

Input your email to download the list.

About the Author

Former security architect for Bank of Canada and Payments Canada. 20+ years building compliance programs for critical infrastructure.