💡 Still using the classic Drata experience? Refer to How to Disable a Test for the original UI.
Overview
Disabling a test stops it from running and prevents its results from affecting control readiness. This is useful when a test is not relevant to how your organization implements a control or when monitoring is handled by another tool or process.
When you disable a test, you must provide a business rationale. This helps maintain audit transparency and makes it easier to review or re-enable the test later if requirements change.
When to disable a test
Disable a test when:
The test does not apply to your environment
The control is implemented or monitored outside of Drata
The test should not run or generate alerts
The test does not reflect how compliance is managed in your organization
If the test is relevant but only certain items should be ignored, consider using exclusions instead of disabling the test.
Prerequisites
Permissions: Only users with write access to Monitoring can disable tests. Eligible roles typically include: Administrators, Workspace Managers, Information Security Leads, and Control Managers.
Disable a test
Go to Monitoring.
If the test is currently running, select the ellipsis (…) and stop the test run. This only stops the current run so the test can be disabled.
In the table, change the test Status from Enabled to Disabled.
Enter a business rationale explaining why the test is being disabled.
Save your changes.
Once disabled, the test:
Stops running
No longer affects control or framework readiness
Remains visible for reference and audit review
Re-enable a disabled test
You can re-enable a test at any time if it becomes relevant again.
Go to Monitoring.
Change the test Status back to Enabled.
Save your changes.
The test will resume running and contribute to readiness going forward.