New in Vanta 9.13.22
This month we’re unveiling two major developments: our Connectors API for integration partners and our Stacksi integration for automated security questionnaires. Other highlights include:
- Improved Groups access and customization
- Import and sync employee groups from Okta
- AWS Organizations and CodeCommit support
- Tests page UI update
- Assign approvers to Policies
- Scope devices using Kandji Blueprints
- Crowdstrike integration
Introducing Vanta’s API for integration partners
To extend the openness and full potential of the Vanta platform, we’re introducing our Connectors API. The Connectors API unlocks the potential for any developer to send pertinent security information to Vanta.
Technology partners can use the Connectors API to build and publish their own integrations on Vanta’s integration network. Partner-built integrations look and operate like native connections, working seamlessly for Vanta users.
In the coming months, we’ll begin rolling out the API to Vanta customers who can use the framework to write their own private connections. Stay tuned!
Automate security questionnaires with Stacksi
Vanta’s Stacksi integration makes it easier than ever to complete security questionnaires. Stacksi uses artificial intelligence and hands-on expert review to complete questionnaires on your behalf. This integration connects Stacksi to your Vanta account to help complete security questionnaires quickly and with 90-95% accuracy.
Improved Groups access and customization
We’ve moved the Groups page to the side nav for faster access. We’ve also given you more options to customize your default group. Rename your default group or add custom tasks to its checklist. Configure your groups and their corresponding checklists exactly as you’d like. Plus, former employees can also be added to groups, so you can keep historical employee records organized.
Import and sync employee groups from Okta
For customers using Okta as their identity provider, you may now import groups directly from Okta into Vanta. Employee groups in Vanta are kept in sync with Okta. If an employee’s status or group membership changes in Okta, Vanta recognizes the change and updates accordingly. With this update, you can continue using Okta as the source of truth for your employees and group membership without duplicative work in Vanta.
AWS Organizations and CodeCommit support
Vanta’s integration with AWS got a big update this month. We understand that managing dozens of individual AWS accounts in Vanta can be a challenge, so we now support AWS Organizations. When you connect AWS to Vanta, you can choose to add a single AWS account or an entire organization. Vanta regularly scans your AWS Organization to detect new or deleted accounts and fetches resources within accounts for display on the Inventory page.
Vanta now supports AWS CodeCommit for code version control account monitoring. After allowing Vanta to fetch your CodeCommit metadata, you’ll find your AWS repositories listed on the Inventory page under Git Repositories. This was a popular request and provides Vanta users with increased awareness over critical items in their tech stack.
Tests page UI update
The Tests page UI has been updated. Now you can view all of your tests at once, sort by owner or status, or view by category. We made this change to make it faster to see tests that need attention as well as who’s responsible for their remediation.
Assign approvers to Policies
Policies can now be assigned approvers. Approvers will receive an email notification when it’s time to review a policy. This update eliminates the need to ask for approval via email or chat and helps your team define clear operating procedures for rolling out policies to your organization.
Scope devices using Kandji Blueprints
Vanta’s Kandji integration now supports Kandji Blueprints. Define whether entire device groups are in scope or not with a click. Gone are the days of managing scope machine by machine. This enhancement to our Kandji integration reduces extra work on the Vanta side, and allows you to continue using Kandji as the source of truth for device group membership.
Vanta now integrates with Crowdstrike. After connecting Crowdstrike with Vanta, visit the Access page to see which users have access to the service. Vanta automatically runs tests to check that offboarded employees no longer have access to Crowdstrike.
Try it out
As always, we welcome your feedback. Let us know what you think by reaching out to your Customer Success Manager. Keep in touch with us 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