The Monitoring page provides a single place to view the status of your security controls.
Prerequisite
Admins, Information Security Leads, DevOps Engineer, Workspace Managers, and Control Managers can access this section within Drata.
Access Monitoring page
Select Monitoring from the left navigation menu to access this page.
At the top of the Monitoring page, you can view the overall summary which includes percentage Of Tests Passed, number of Failed Tests, and number of Passed Tests.
You can also filter your tests based on the test’s result, status, category, type, and other parameters.
“New” Test filter
New tests that Drata released for the first time will be highlighted as “New” for 45 days before the “New” highlight is removed. Use this filter to see what are the newest tests that were released by Drata.
Result filter
The following list describes the filter for test results:
Passed: Drata has captured all necessary data and determined the required conditions are being met.
Failed: Drata has captured all necessary data and determined the required conditions are not being met.
Error: The test ran into an issue that prevented Drata from capturing necessary data, hence a determination cannot be made if the required conditions are being met.
Status filter
The following list describes the filters for test status:
Enabled: The test is enabled and will run daily with autopilot or can be run manually. An enabled test WILL contribute to control readiness if the test is mapped to a control.
Disabled: The test is disabled and will not run with autopilot nor can it be run manually. A disabled test WILL NOT contribute to control readiness even if the test is mapped to a control.
Unused: A connection that is required to run this test is missing, or no policy drafts have been started, thus the test can not be used. Unused tests WILL NOT contribute to control readiness even if the test is mapped to a control.
Category filter
The following list describes the filters for test category:
Device: Filter for tests that monitor device compliance.
Identity Provider: Filter for tests that monitor authentication (access) and authorization compliance requirements like MFA usage.
In Drata: Filter for tests that monitor items within Drata.
Infrastructure: Filter for tests that monitor infrastructure-related compliance requirements like “Load Balancer Used” or “Availability Zone Used.” Tests in this category may also overlap with the “Observability” category.
Observability: Filter for tests that verify for the correct configurations of infrastructure tools. These tests can be powered by infrastructure monitoring systems like Cloud Security Posture Management (CSPM) that look for misconfigurations or potential risks in your infrastructure, vulnerability scanners to detect vulnerabilities, and more.
Policy: Filter for tests that monitor and automatically verifies for the required policy’s existence, review, or acknowledgment. External policy management and HRIS connection types may be used by some of these tests.
Version Control: Filter for tests that monitor codebase-related requirements like the code review process.
Ticketing: Filter for tests that can be powered by a ticketing integration like Jira. Examples include the “Security Issues are Prioritized” test.
Type filter
The following list describes the filters for test type:
Drata: Filter for tests that Drata offers out-of-the-box
Custom (published): Filter for custom tests that are published.
Custom (draft): Filter for custom tests that are drafts
Learn more about custom tests: Create custom tests for Adaptive Automation.
Exclusion filter
Use the “Has exclusions” filter to find tests with findings that were excluded from evaluation and results.
Control filter
Use this filter by searching and selecting controls to see which tests map to those controls.
Framework filter
Use this filter by searching and selecting framework(s) to see which tests correlate to which framework through the test’s > control > requirement > framework mapping.
Tickets filter
Note: Only available if you are using a ticketing connection with write-enabled.
Use this filter to see which tests have “In progress” or “Done” tickets linked to them from your ticketing connection.
Test table overview
The table presents all the tests that automate control monitoring and evidence collection that are available to you. Each row represents a single test while each column represents a specific attribute of that test:
Name: The name of the test
If a test is new, there will be a “New” highlight next to the name.
If a test is a custom test that is a draft, there be a “Draft” highlight next to the name
Result: The latest result of the test from its last run
Findings: The number of failing findings for a test. Note that tests that passed or ran into an error will not have failing findings.
Status: The status of the test represented as a toggle: On if it is enabled, off it is disabled. If the test is actively running, it will display “Testing…” and if it is unused it will display “Unused.”
Category: The category that the test belongs to.
Active connection: The connection(s) that the test is running on and monitoring.
The Fix error button indicates that the test encountered an issue preventing Drata from capturing the necessary data, making it impossible to determine whether the required conditions are met.
The Fix failure button indicates that Drata has captured all necessary data but determined that the required conditions are not being met.
You can click on the button or the row of a test to view its details and result.
Bulk actions
The following bulk actions are available to be applied to selected tests:
Test now: This action will run all the selected tests.
Enable: This action will enable all the selected tests.
Disable: This action will disable all the selected tests.
Download CSV: This action will download all the selected tests into a CSV file. The CSV will include the following test attributes: Name, description, status, result, category, and the ID of the controls that are mapped to this test.
To view and perform bulk actions on tests:
Select the desired tests by using the checkbox on the left-hand side of the table.
Once a test has been selected, the More actions button to perform bulk actions will appear. On the dropdown options, select the bulk action you would like to perform on your selected tests.
NOTE: You can use search or apply filters to get to a subset of tests before selecting and performing bulk actions. If you select tests and then update your search or filter, the tests you selected previously will remain selected.