⚠️ Select your experience

The steps depend on your interface version. Select a link to skip to the instructions for your version.

Customers who joined Drata on or after Feb 24, 2026 are automatically on the New Experience.

Instructions for the New Experience ⬇️

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.

Instructions for the Classic Experience ⬇️

Disabling tests within Drata and providing a business rationale

Here's why

You have the ability to disable tests within Drata if the test itself is not applicable or if your organization is using something else to monitor or implement the control. This can be reverted at any time should there be a need to re-enable the test. Additionally, it can resolve errors where tests marked as "Out of Scope" still trigger compliance alerts, ensuring a more accurate monitoring experience.

Before diving in

Only Account Administrators, Workspace Managers, and TechGov roles have the ability to disable tests within Drata.

Here's how

Go to your Drata's Monitoring page. Alternatively, users can access the Test Management Screen within the Drata UI for a comprehensive view of monitoring tests.
Using the Search Bar, look up the test that you need to disable (In this example, we are disabling the test for 'Engineering Job Description').
Select the test you want to disable to open up the Test Details drawer.
Change the Test Status from Enabled to Disabled.
Fill in the Business Rationale for disabling the control. This can help remind you the reason why you disabled this test, especially if you have disabled multiple tests. It is also recommended to periodically review your disabled tests to ensure they remain relevant to your compliance requirements. Documenting the rationale also assists in troubleshooting persistent monitoring issues caused by disassociated or "Out of Scope" tests.

NOTE: You can directly go to the associated test from the Controls view by scrolling down in the control drawer and clicking the View Test Page. To ensure efficient navigation, make it a habit to periodically review the Monitoring tab for newly triggered errors or "Out of Scope" tests.