What's New in Vanta 3.1.22
Maintaining a security program can be an overwhelming endeavor, especially when done without the right tools. Thankfully, one of Vanta's greatest advantages is our best-in-class automation. We make it easy for users to manage and administer their work via smart automations with commonly used tools. In this month’s update, we're highlighting our enhanced integrations with Slack, Okta, and Datadog, which are designed to make your security program more trusted and easier to manage.
We recognize that much of the day-to-day collaboration around security and compliance work occurs outside of Vanta. To better integrate into your team’s existing workflows and tools, we've launched Slack notifications.
Now, immediate alerts, as well as daily or weekly summaries, can be delivered to the Slack channel of your choice. These notifications are further organized by the categories you're used to seeing in Vanta: Employee, Engineering, Policy, Risk.
With this new feature, we're excited to meet customers where they work and to broaden Vanta's automation capabilities.
Okta IdP scoping
For larger companies with hundreds of employees or multiple sub-organizations, compliance scoping can get complex. It’s common for these businesses to need entire employee groups and other resources with IdPs to be marked as out of scope. Yet, managing scope across multiple organizations has traditionally been a manual, time-consuming process. To help, Vanta now leverages Okta’s application assignment functionality to easily determine scope for your people and resources.
This enhanced Okta integration makes it easy to define which employees should be added to Vanta and which should be kept out of scope. By using your IdP as the source of truth for employee scoping, you’ll reclaim the lost time spent managing multiple applications and benefit from a faster, simpler workflow.
Learn more about controlling scope using Okta.
Datadog expanded integration
SOC 2 and ISO 27001 both require server capacity management and threshold monitoring. In addition, this practice is recommended for any security program, no matter the associated framework. To provide even greater server monitoring capabilities, we’re expanding our Datadog integration with over 30 new tests that check AWS, Azure, and GCP for:
• Load balancer health and latency
• CPU utilization
• VM utilization
• Free storage space
• Free memory space
• Read and write capacity
This expanded Datadog integration reflects our commitment to make Vanta the trusted and most holistic view into your organization’s security.
Learn more about connecting Vanta to Datadog. In beta until general availability on 3.4.22
Tell us what you think
As always, we welcome your feedback on these changes. Please let us know what you think by reaching out to your Customer Success Manager. Let’s keep in touch on LinkedIn.
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