Vanta
See who Vanta says is overdue on security training, policy acceptance or device monitoring, leavers whose offboarding is not finished, vendors by risk and review status, apps Vanta discovered people using that nobody has reviewed, failing compliance tests, monitored computers failing encryption or screen lock, the systems connected to Vanta, and Vanta's event log.
Questions you can answer 18
Each one is a saved query that ships with ConfigView, reading your Vanta data on your own server. Ask it in plain English, SQL, Slack or the API.
- Which employees have not installed the Vanta agent?
- Which laptops are not encrypted?
- Which computers are failing screen lock or antivirus checks?
- What shadow IT apps has Vanta found?
- Which apps are people signing in to that we have not reviewed?
- Who is using unapproved AI tools?
- Which Vanta tests are failing right now?
- Which compliance tests have overdue remediation?
- Who owns the failing Vanta tests?
- Which leavers are not fully offboarded in Vanta?
- Do any former employees still have accounts or a laptop?
- Who left but still signs in to Vanta?
- Who is overdue on security awareness training?
- Which employees have not accepted our security policies?
- Who is blocking our SOC 2 personnel tests in Vanta?
- Which high-risk vendors are overdue for a security review?
- Which vendors do we sign in to without MFA?
- Show our vendors by risk level
No Vanta questions match that yet. Try a shorter word.
What ConfigView collects from Vanta 10
-
Discovered Vendor Accounts
Who uses each discovered app: the person (or computer and its owner) behind every account Vanta found, with the app's review state.
-
Discovered Vendors
Apps Vanta found people using - from Okta, Google Workspace, Microsoft 365, Jamf or Vendr sign-ins - that are not in the vendor inventory, with how many accounts each has and whether it is waiting for review, ignored or rejected.
-
Event Log
Vanta's event log - who changed what in Vanta (people offboarded, tests deactivated, vendors added, policies approved, integrations connected) - kept as a permanent archive in ConfigView.
-
Groups
Personnel groups in Vanta, made by hand or imported from the identity provider: name, source, how many people are in each and its point of contact.
-
Connected Integrations
Systems connected to Vanta (identity provider, cloud, code, HR, device management) with each connection, whether Vanta has disabled it and the error it gave.
-
Monitored Computers
Computers watched by the Vanta agent or a Vanta-built MDM integration: owner, serial, operating system, last check-in, and pass/fail for screen lock, disk encryption, password manager and antivirus.
-
People
Everyone Vanta tracks as personnel: employment status, start and end dates, leave, groups, and where each security task stands - training, policy acceptance, device monitoring, background check and offboarding tasks.
-
Tests
Vanta's automated compliance tests: status (passing, needs attention, deactivated), category, the integrations each one checks, how many items fail it, when remediation is due and who owns it.
-
Vanta Users
People who can sign in to Vanta itself: name, email and whether the login is active.
-
Vendors
The vendor inventory: category, status, inherent and residual risk, how people sign in (SSO, Okta, Google, password) and whether MFA is required, owners, contract dates and value, security review dates and the latest decision.