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.
Related Article: Exclusions vs Disabling a Test