What's New in Vanta 6.15.22
Here at Vanta, we’re starting the summer with a collection of newly shipped features designed to help keep your organization secure and cool under audit. In this month’s roundup we’re excited to cover our latest product offering, Vanta Trust Reports, along with:
- Enhanced support for scoping by identity provider
- Manual deactivation of employee accounts
- Templates for non-technical evidence collection
- Custom evidence easy add & export
- AWS DocumentDB and GCP Artifact Registry support
Introducing Vanta Trust Reports
For any company, but especially startups, the need to demonstrate security comes early and often. Starting with prospects at presales and continuing with customers at renewal, proving your organization’s security can be difficult and time consuming. We launched Vanta Trust Reports to make it easy for your business to demonstrate its commitment to security, build trust with prospects, and ultimately, win more business.
With Vanta Trust Reports, you can showcase Vanta’s first-party data in an easy-to-understand dashboard, alongside commonly requested security documents, certifications, and reports. A Vanta Trust Report is your company’s external-facing single source of truth for its security and compliance posture.
Read our announcement on Vanta Trust Reports.
Create your Trust Report.
Scoping by Identify Provider: OneLogin, Office, Okta, and Google
For larger companies with hundreds of employees or several sub-organizations, defining who falls within the scope of an audit can be complex. Groups within the same company can hold vastly different levels of access to critical business systems. In some cases, access can be so compartmentalized that it doesn’t make sense to include certain employees or groups within scope of an audit.
Managing this level of scope complexity within Vanta can be tedious when done on a person-by-person basis. That’s why we’ve expanded our scoping by identify provider (IdP) to include OneLogin and Office, in addition to existing support for Google Workspace and Okta. Scoping by IdP makes it easy to define which employees or user groups should be monitored by Vanta and which should be regarded as out of scope.
Manual deactivation of employee accounts
It’s common for an organization to maintain employee accounts, such as an identity provider, beyond offboarding to retain access to institutional knowledge or important linked services. For example, a former employee’s email account may still be used to access cloud storage or a project management tool in the interim of complete account migration. Situations like these make sense in practice, but can cause friction when offboarding an employee in Vanta.
That’s why we’ve introduced a new feature that allows Vanta admins to manually mark any account associated with an offboarded employee as deactivated. This feature helps admins continue through the steps of employee offboarding without becoming blocked by a service that is knowingly still active. There’s also a useful ‘reset offboarding button in case an account has been marked as deactivated by mistake.
Find this new feature within the Offboarding menu on the People page.
Faster path to audit
Templates for non-technical evidence
Vanta automates up to 90% of the evidence collection work needed to prove compliance for leading security certifications using automated technical tests. But there are other requirements, such as establishing an anonymous whistleblower channel or maintaining incident reports, that cannot be automated with technical integrations.
We recognize that it can be difficult for a non-compliance expert to know how to best document evidence for manual tests. We also heard from customers that a simple example or template of how others have approached non-technical tests goes a long way in providing guidance. We listened to your feedback and now include helpful templates for nearly all non-technical tests.
These non-technical evidence templates can be found linked within their test description on the Documents tab, and we’ll continue to introduce new templates in the coming weeks.
Visit the Documents tab to get started with manual evidence templates.
Custom evidence easy add & export
Vanta’s default collection of tests will get many customers past the finish line for an audit, but there are times when additional documentation may be requested by an auditor to validate that controls are being properly met. For example, an auditor may wish to see a screenshot of your company’s MDM configuration settings in addition to Vanta’s automated evidence to support that a MDM is being used.
To make working with custom evidence in Vanta even easier, auditors can now request additional evidence directly from the Documents tab. This new feature enables auditors to quickly request evidence without spending time navigating between test sub-menus. Custom evidence is still tied to specific standards and controls, and is located under the custom evidence category upon creation.
Additionally, custom evidence can now be easily exported with the click of a button. We recognize that you or your auditor may need access to all of your custom evidence as a single download, and we’ve it easy to export this data directly from the Documents tab.
AWS DocumentDB support
Vanta now supports AWS DocumentDB as a new resource for NoSQL Databases. We’re rolling out new tests that check your AWS DocumentDB instance for encryption at rest, enabled backups, and additional tests pulled in from AWS Cloud Watch and Datadog for CPU usage monitoring and read/write capacity.
View your AWS DocumentDB instance by visiting the Inventory page.
GCP Artifact Registry for vulnerability scanning
In response to Google’s deprecation of its Container Registry service, Vanta now supports GCP Artifact Registry for vulnerability scanning. The new GCP Artifact Registry integration works identically to the Container Registry integration and can be enabled with guidance from this help article.
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