Documentation Index

Fetch the complete documentation index at: https://help.scrut.io/llms.txt

Use this file to discover all available pages before exploring further.

Fix Failing Tests

Prev Next

When a cloud test fails, it moves to the “Fix Required” status. In this guide, we walk you through the complete workflow of addressing test findings and making your cloud infrastructure compliant.

When a test has the “Fix Required” status, it indicates that one or more resources in your cloud environment don’t meet the requirements defined by a specific test. A failed test represents a compliance, security, or configuration issue that needs to be resolved.

Note:

When all resources within a test become compliant, the test automatically transitions to OK status.

What to Do When a Test Fails?

We recommend following this workflow to fix failing tests:

  1. Assign: Start by assigning the test finding to the appropriate team member or resource owner. This establishes accountability and ensures the finding gets proper attention. Alternatively, you can assign flagged resources to specific team members for more granular responsibility.

  2. Remediate: Review the failing resources and take corrective action to bring them into compliance. This may involve configuration changes, policy updates, or infrastructure modifications. Scrut provides in-depth remediation guidance to assist you.

  3. Validate: Confirm if the remediation was successful. Scrut will re-evaluate the resources against the test criteria.

  4. Monitor: Continue monitoring the test to ensure resources remain compliant over time. New resources or configuration changes may cause previously passing tests to fail again.

  5. Alternative Actions: Not all test findings require immediate remediation. You have additional options:

    • Ignore a Test Finding: If a test is not applicable to your environment or you've accepted the risk, you can ignore it. Tests marked as ignored do not impact your compliance calculations.

    • Ignore Resources within a Test: For resources that don't need to comply with a specific test, you can create exceptions by marking them as ignored. Instead of ignoring the entire test, this gives you the flexibility to mark specific resources as ignored for specific tests.

    • Create a Risk: Review the potential impact and create an associated risk.