ALL RESOURCES
Compliance frameworks
Security vs. compliance: What’s the difference?

Security vs. compliance: What’s the difference?

For many businesses, security and compliance are inextricably linked, and for good reason. Without security, it is impossible to demonstrate compliance, and without compliance, there is no objective proof of security. 

The challenge is to create an effective security program while simultaneously achieving compliance. The better your organization understands this relationship, the easier it becomes to support both initiatives and move forward as a business. Let’s dive in. 

What is security and why is it important? 

Security refers to the ability to protect your organization from internal and external risks. The methods used to secure your company are known as called controls. These are the physical, administrative, and technical measures used to mitigate malicious and accidental threats. Most security initiatives fall into two categories: cybersecurity and information security.

Cybersecurity 

Cybersecurity is the practice of protecting digital data, networks, and devices from criminal intervention. Hackers, viruses, phishing, and breaches are the primary threats. This kind of security is especially concerned with electronic technology that connects to the internet. Examples of cybersecurity measures include: 

  • Installing a firewall
  • Using a Virtual Private Network (VPN)
  • Encrypting data
  • Authorization of access

Information security (infosec)

Information security is the practice of protecting any kind of data an organization handles, whether it’s stored, used, or dispersed. In contrast to cybersecurity, infosec caters to all kinds of data, not just digital. Customer behavior data, internal employee info, third-party data, payment information, and health information are examples of protected info. Common infosec practices measures include: 

  • Installing an Information Security Management System (ISMS)
  • Centralizing and assigning data ownership
  • Defining security practices and protocols in code
  • Keeping internal systems and policies updated

Cybersecurity and information security come together to fortify confidentiality, integrity, and accessibility. Without these security measures in place, it’s not possible to achieve compliance standards. More importantly, your company will be exposed to numerous threats, risks, and attacks. 

What is compliance and why is it important? 

Compliance is the practice of proving your security methods and controls are effective. Organizations usually have to adhere to compliance regulations because of legal mandates or requests from a third-party client or vendor. The California Consumer Privacy Act (CCPA) is an example of a state-mandated compliance, while SOC 2 is a form of compliance that organizations adhere to in order to prove security measures are in place. 

It’s important to consider the kind of industries or geographic locations your company plans to conduct business. Healthcare entities may require you to obtain a HIPAA certification. If you anticipate doing business with citizens in the European Union, you’ll have to comply with GDPR

You may already be in a state of compliance, however; many certifications or standards will require a third-party audit to produce an objective report on your behalf. Whether the incentive to comply is mandatory or conditional, compliance plays a significant role in the growth, safety, and reputation of your business. 

Bridging the gap between security vs. compliance 

Creating a strong security program in addition to demonstrating compliance can be a complex process. Where should a company start first? Which controls are most important? Which employee should lead the charge on security vs. compliance? Every business will have different challenges, but here are a few tips to help you connect the dots between security and compliance. 

Develop a keen sense of security awareness
Before building an effective security program that will meet compliance standards, it’s best to understand how to respond to security threats. Security is a company-wide responsibility. The more aware each employee is about security, the more comprehensive your efforts will be.

Adopt the right perspective
It can be discouraging to go through the compliance process for the first time, especially if you know you have a strong security posture. Even if you don’t check every box right now, going through the audit process will mitigate indecision and give you clear action items.

Conduct a risk assessment
Once your security controls are in place, a risk assessment will help you find out if there are any gaps or missing elements. Performing a risk assessment prior to a compliance audit can save you time and money. An assessment will help you identify the likelihood of risk frequency, rank risk scenarios, and locate any weaknesses across your security program. 

Learn more about security and compliance 

Vanta’s 6 principles for pragmatic startup security
Create a culture of security from the start
10 steps to effective compliance risk management

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.