You've been asked to present your SOC 2
The first time a prospect brings up security, you might feel like a deer in the headlights. You may even get asked about SOC 2 report by name. If it hasn’t happened yet, you should anticipate questions about security and compliance soon. In this post we’ll help you get a head start on next steps once you’ve been asked for your SOC 2. We’ll get into what the SOC 2 is all about, reasons to get SOC 2, and how a security attestation can help your company close more deals.
The more you grow
As your company grows, you’ll find that prospect and customer requests for security protocols and documentation are growing too. If you gather or store customer data at any scale, data security should be front-of-mind and on your to-do list. In today’s competitive business climate — in which data breaches are unfortunately common, even as they are increasingly unacceptable — cybersecurity is of peak importance. Companies of all sizes seek clear evidence that vendor and partner security systems meet commonly accepted standards, and you can differentiate your business by leading with strong security and compliance practices.
If you’re an early-stage startup you may think you’ve got some time before you need to align with industry security standards, or you might think you’re prepared to cobble together one-off security solutions as you go. If this sounds familiar, it’s worth considering an alternative approach: the sooner your company is able to build security and compliance into its operations, the easier it will be to implement practices company-wide that will grow with you. Working proactively to achieve a strong security posture will not only make your organization more secure — it will position you for smooth and successful sales conversations, and the growth you’re looking for.
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.
Does your business offer services to customers who are interested in your level of PCI compliance?
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:
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
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
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
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