Drift Cause

Drift Cause connects codified infrastructure with out-of-code audit logs, providing detailed insights that enable teams to:

• Identify who made the change, when, and how
• Understand the specific event or action responsible for the drift (e.g., CLI command or manual UI update)
• Investigate, resolve, and prevent drift more efficiently

With Drift Cause, teams can analyze the root cause of drifts, address issues efficiently, and implement safeguards to prevent future occurrences

In order to utilize Drift Cause to analyze Drift Cause, please follow these steps:

1. Enter the latest Drift : If a drift has been detected in your environment, a banner will direct you to enter the latest Drift.

   

2. Analyze a Resource's Drift Cause : In the drift's resources list, when hovering over the wanted resource, press the Analyze Drift Cause button.

   

3. Analyze the Drift's Cause : In the analyze table you will be able to view events' data relating to selected resources - Event Date, Event Resource, Event Name, and the user who took the action.

   

4. View More Data of the Event : For each event, there's a link that will give you more information directly from the Cloud Provider.

   

📘

Setting up Drift Causes

• Cloud Compass Setup
  • In order to use Drift Cause, you first must set up Cloud Compass in your organization.
    For more information please refer to the documenation.
• Required Setup Permissions
  • To analyze a drift's cause, the user must have the permission View Drift Cause

🚧

Provider Support

Drift Cause currently only supports AWS

🚧

Reasons Drift Cause is not available

There are several reasons why the Analyze Drift Cause Button won't be available -

• A lack of the resource's Id, that can happen for a number of reasons
  • An old agent is being used
  • The drift reason is a resource being manually deleted
• Unsupported Provider, as detailed above
• A user is missing the View Drift Cause permission