Skip to main content

​
What this check does

Checks for classification tags on key resources.
This check also runs on 2 other integrations — see Infra entity should be classified for the full list.
Passes when: All critical resources have classification tags.

​
Why this matters

Resource classification helps with compliance and access control.

​
How to fix

Classify infrastructure resources with tags
  1. Sign in to the AWS Console and navigate to Resource Groups & Tag Editor → Tag Editor.
  2. Choose the regions and resource types to cover and click Search resources.
  3. Select the flagged resources and click Manage tags of selected resources.
  4. Add a Classification tag with a value such as Critical, High, Medium, or Low, and apply the tag changes.
  5. In DSALTA, open Data Library → Inventory and confirm each asset now shows a criticality classification.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.