Skip to main content

Excluding a Specific Resource from a Test

Keep a test running for everything else while excluding the one resource you've decided not to hold to that check — without removing it from your compliance scope.

Written by Upendra Varma

Sometimes a test is right for almost everything it checks, but not for one specific resource. A test like "Buckets should not be public" might be correct for every bucket except one you've deliberately made public for a business reason. A test like "Database backups are enabled" might not matter for an internal, disposable database that isn't worth the operational overhead of backups.

Rather than turning off the whole test — which stops it checking anything — ComplyJet lets you exclude just that one resource. The test keeps running and evaluating everything else as normal.

Where to find this

Open any test from the Tests page, and go to its Evidence tab. Every resource the test evaluates is listed under an Active / Deactivated toggle — Active is what's currently being evaluated by this test.

Excluding a resource

  1. On the Active tab, select the checkbox next to the resource (or resources) you want to exclude. You can select more than one at a time.

  2. A toolbar appears showing how many resources are selected. Click Deactivate.

The resource moves to the Deactivated tab.

What this does — and doesn't do

  • This test stops evaluating that resource. It no longer affects this test's pass/fail status.

  • The resource itself stays fully in your compliance scope — it still shows up under Infrastructure Resources, Code Repositories, or wherever else it belongs, and it's still visible to your auditor from a resources perspective.

  • The exclusion is scoped to this one test only. If the same resource is also checked by a different test, it will still show up — and still need handling — there.

Reactivating a resource

To bring a resource back under this test's evaluation, go to the Deactivated tab, select its checkbox, and click Reactivate. It moves back to Active and the test resumes evaluating it on the next run.

Related

Did this answer your question?