ALL RESOURCES
HIPAA
The roles of PCI DSS and HIPAA compliance

The roles of PCI DSS and HIPAA compliance

It’s wise for any business to do an audit of their security system and find out if there are any gaps leaving them vulnerable. This audit should also include determining if there are any security standards you should be compliant with. At first glance, every security standard may look similar, from SOC 2 to PCI, because they’re each designed to safeguard the data you’re taking in. But that doesn’t mean you can substitute one for another.

Let’s talk about two particularly critical security standards or regulations: PCI DSS and HIPAA. How are they similar, how are they different, and why would your organization need compliance for both of them?

Similarities between PCI and HIPAA

HIPAA stands for the Healthcare Insurance Portability and Accountability Act. PCI DSS stands for Payment Card Industry Data Security Standard. PCI and HIPAA have a lot in common, which makes it even more important to understand which one your business may need.

Their general purpose

PCI and HIPAA are both security regulations or standards designed to enhance your security. They both consist of controls and practices you need to implement to become compliant. What makes HIPAA and PCI unique is that they’re specifically built to protect users’ private information rather than all your data.

The parties they protect

One factor that varies among security standards is the party that benefits from them. Some security standards and reports, like SOC 2 and ISO 27001, are designed to protect your organization from a potentially costly data breach.

HIPAA and PCI, on the other hand, are designed for the benefit of your customers, patients, and/or clients. Each standard is designed to make you less vulnerable to data breaches and protect your organization’s clients and reputation.

Differences between PCI and HIPAA

Complying with just PCI or HIPAA will not free you from needing to comply with the other. Let’s take a closer look at what makes each of these regulations stand out.

The information they protect

Both HIPAA and PCI were created to prevent the misuse of very specific types of data. PCI compliance is designed to secure your customers’ payment information like their credit card numbers. HIPAA, on the other hand, is meant to secure people’s private health information.

Organizations that should comply

Not every organization needs to comply with PCI and with HIPAA. In fact, each regulation applies to certain specified types of organizations.

PCI compliance is necessary for any organization that plays any role in a transaction, including processing, storing, or transferring payment information. This includes any ecommerce business as well as payment processing companies, cloud storage companies, and more. Being PCI compliant tells major credit card companies and banks that you’re a reliable organization.

HIPAA compliance, however, applies to select types of organizations that are listed in the legislation as “covered entities.” This includes healthcare providers, health insurance companies, HMOs, and certain other categories.

How they’re enforced

PCI is a standard that was created by and is enforced by the payment industry, including major leaders in the industry like Visa. Those leaders in the industry enforce PCI compliance by charging added fees to businesses that aren’t compliant, and in some cases, they may refuse to do business with you at all.

HIPAA is a legal regulation. It was passed into law in 1996, and it is actively enforced by the Department of Health and Human Safety’s Office of Civil Rights (or OCR). The OCR issues fines for HIPAA violations just as it would issue fines for breaking any other law.

How you verify compliance

The process for becoming compliant with PCI and HIPAA will be different, but so will the process for documenting your compliance.

For PCI compliance, there are specific steps you need to follow to receive a certification once you have met the requirements for compliance. Those steps depend on the number of transactions you handle each year. Most organizations will need to submit a self-assessment questionnaire to document their security controls, a vulnerability scan from an approved vendor, and an attestation of compliance. Large businesses will need an in-depth audit by a third-party auditor instead.

HIPAA is very different because it is a law and it is enforced like one. It is your responsibility to maintain HIPAA compliance and you will receive penalty fines if the OCR discovers that you are not fully compliant.

Why you need PCI and HIPAA compliance together

PCI and HIPAA are both important regulations meant to protect consumers from negligent or malicious organizations. If you process or handle digital transactions in any way, and if you’re categorized as a covered entity in HIPAA, it’s critical that you comply with both of these standards.

But there’s good news: compliance might not be as cumbersome as you expect. Not only is there some overlap between the two, but Vanta’s automated compliance tools can tell you exactly which requirements you’ve already met and which ones you still need to address for each regulation.

Written by
No items found.
Access Review Stage Content / Functionality
Across all stages
  • Easily create and save a new access review at a point in time
  • View detailed audit evidence of historical access reviews
Setup access review procedures
  • Define a global access review procedure that stakeholders can follow, ensuring consistency and mitigation of human error in reviews
  • Set your access review frequency (monthly, quarterly, etc.) and working period/deadlines
Consolidate account access data from systems
  • Integrate systems using dozens of pre-built integrations, or “connectors”. System account and HRIS data is pulled into Vanta.
  • Upcoming integrations include Zoom and Intercom (account access), and Personio (HRIS)
  • Upload access files from non-integrated systems
  • View and select systems in-scope for the review
Review, approve, and deny user access
  • Select the appropriate systems reviewer and due date
  • Get automatic notifications and reminders to systems reviewer of deadlines
  • Automatic flagging of “risky” employee accounts that have been terminated or switched departments
  • Intuitive interface to see all accounts with access, account accept/deny buttons, and notes section
  • Track progress of individual systems access reviews and see accounts that need to be removed or have access modified
  • Bulk sort, filter, and alter accounts based on account roles and employee title
Assign remediation tasks to system owners
  • Built-in remediation workflow for reviewers to request access changes and for admin to view and manage requests
  • Optional task tracker integration to create tickets for any access changes and provide visibility to the status of tickets and remediation
Verify changes to access
  • Focused view of accounts flagged for access changes for easy tracking and management
  • Automated evidence of remediation completion displayed for integrated systems
  • Manual evidence of remediation can be uploaded for non-integrated systems
Report and re-evaluate results
  • Auditor can log into Vanta to see history of all completed access reviews
  • Internals can see status of reviews in progress and also historical review detail

PCI Compliance Selection Guide

Determine Your PCI Compliance Level

If your organization processes, stores, or transmits cardholder data, you must comply with the Payment Card Industry Data Security Standard (PCI DSS), a global mandate created by major credit card companies. Compliance is mandatory for any business that accepts credit card payments.

When establishing strategies for implementing and maintaining PCI compliance, your organization needs to understand what constitutes a Merchant or Service Provider, and whether a Self Assessment Questionnaire (SAQ) or Report on Compliance (ROC) is most applicable to your business.

Answer a few short questions and we’ll help identify your compliance level.

1
2
3
4
!
👍

Does your business offer services to customers who are interested in your level of PCI compliance?

Yes
No

Identify your PCI SAQ or ROC level

The PCI Security Standards Council has established the below criteria for Merchant and Service Provider validation. Use these descriptions to help determine the SAQ or ROC that best applies to your organization.

Good news! Vanta supports all of the following compliance levels:

SAQ A

A SAQ A is required for Merchants that do not require the physical presence of a credit card (like an eCommerce, mail, or telephone purchase). This means that the Merchant’s business has fully outsourced all cardholder data processing to PCI DSS compliant third party Service Providers, with no electronic storage, processing, or transmission of any cardholder data on the Merchant’s system or premises.

Get PCI DSS certified

SAQ A-EP

A SAQ A-EP is similar to a SAQ A, but is a requirement for Merchants that don't receive cardholder data, but control how cardholder data is redirected to a PCI DSS validated third-party payment processor.

Learn more about eCommerce PCI

SAQ D
for service providers

A SAQ D includes over 200 requirements and covers the entirety of PCI DSS compliance. If you are a Service Provider, a SAQ D is the only SAQ you’re eligible to complete.

Use our PCI checklist

ROC
Level 1 for service providers

A Report on Compliance (ROC) is an annual assessment that determines your organization’s ability to protect cardholder data. If you’re a Merchant that processes over six million transactions annually or a Service Provider that processes more than 300,000 transactions annually, your organization is responsible for both a ROC and an Attestation of Compliance (AOC).

Automate your ROC and AOC

Download this checklist for easy reference

Questions?

Learn more about how Vanta can help. You can also find information on PCI compliance levels at the PCI Security Standards Council website or by contacting your payment processing partner.

The compliance news you need. Delivered securely to your inbox.