> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zero-x.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# 1.5 CloudAutofix

title: Cloud Autofix
description: Identify, review, simulate, execute, and monitor automated remediation actions for cloud security findings.

***

## Overview

**Cloud Autofix** helps users identify and remediate supported cloud security findings directly from Zero-X Cloud.

Instead of manually opening the cloud provider console and changing the configuration, Cloud Autofix provides a guided workflow to review the finding, simulate the proposed change, execute the remediation, and monitor the result.

The typical workflow is:

# How to Use Cloud Autofix

## Step 1: Open Cloud Autofix

1. Sign in to **Zero-X Cloud**.
2. Open the **Cloud Autofix** module.
3. The **Fix Available Findings** tab is displayed.
4. Review the available findings.

***

## Step 2: Locate the Finding

Use the available filters to find the security issue you want to remediate.

Available filters may include:

* Filter by Date
* Categories
* Accounts
* Cloud Resource
* Severity
* Resource Types
* Compliance
* Region

You can also use:

* **Search** to find a specific finding or resource.
* **Columns** to customize the displayed columns.
* **Saved Views** to save frequently used filter configurations.
* **Grouping** to organize findings.

***

## Step 3: Review the Finding

Before executing any remediation:

1. Review the finding description.
2. Verify the affected resource.
3. Check the cloud provider.
4. Check the resource type.
5. Review the risk score.
6. Review the severity.
7. Confirm that the finding is appropriate for remediation.

***

# Step 4: Open AutoFix

1. Locate the required finding.
2. Click **AutoFix**.

The **Remediate Finding** page opens.

The page provides information about the target resource and the remediation actions available for that finding.

***

# Remediate Finding

The Remediate Finding screen contains three main sections:

### Target Resource

This section identifies the resource that will be affected.

It can display:

* Resource ID or resource name
* Finding description
* Severity
* Cloud provider
* Resource type

**Details**

* Severity: High
* Cloud Provider: AWS
* Resource Type: EBS Volume

> **Always verify the target resource before executing a remediation.**

***

# Available Actions

Depending on the finding, Cloud Autofix may provide the following actions:

1. **Run Dry Run**
2. **Execute Remediation**
3. **Execute Rollback**

***

# Run Dry Run

## What is a Dry Run?

A **Dry Run** simulates the remediation without applying the change to the live cloud resource.

It allows you to review the expected action before making an actual change.

### Steps

1. Open the required finding.
2. Click **AutoFix**.
3. Review the **Remediate Finding** page.
4. Click **Run Dry Run**.
5. Wait for the simulation to complete.
6. Review the Dry Run result.
7. Verify that the proposed change is expected.

### Important

A successful Dry Run indicates that the remediation can be simulated successfully. It does **not** mean that the live resource has already been changed.

***

# Execute Remediation

## What is Execute Remediation?

**Execute Remediation** applies the supported security fix directly to the target cloud resource.

This action can make a live change.

### Before executing

Verify:

* Correct finding
* Correct target resource
* Correct cloud account
* Correct region
* Correct resource type
* Expected remediation action
* Dry Run result, where available

### Steps

1. Open the required finding.
2. Click **AutoFix**.
3. Review the target resource.
4. Run the **Dry Run** when available.
5. Review the Dry Run result.
6. Select **Execute Remediation**.
7. Review the confirmation information.
8. Confirm the remediation.
9. Wait for the execution result.
10. Review the execution logs.

After the remediation is successfully executed, Zero-X verifies the finding according to its scanning and remediation workflow.

> **Warning:** Execute Remediation can modify a live cloud resource. Make sure the proposed change is approved before execution.

***

# Execute Rollback

## What is Rollback?

**Execute Rollback** is used to reverse a supported infrastructure change created by a previous remediation.

Rollback availability depends on the remediation type.

### Steps

1. Open the relevant remediation workflow.
2. Select **Execute Rollback**.
3. Review the rollback information.
4. Confirm the rollback.
5. Wait for the rollback execution to complete.
6. Review the execution logs.
7. Verify the resource and finding status.

> **Note:** Not every remediation supports rollback.

***

# Remediation Execution Logs

The **Remediation Execution Logs** tab provides a history of remediation operations.

Use the logs to review:

* Remediation action
* Target resource
* Execution status
* Execution time
* Execution result
* Error information
* Rollback activity
* Previous remediation attempts

### Troubleshooting a Failed Remediation

If a remediation fails:

1. Open **Remediation Execution Logs**.
2. Locate the failed execution.
3. Review the error details.
4. Verify the cloud account connection.
5. Verify the required permissions.
6. Confirm that the resource still exists.
7. Run a Dry Run again, if available.
8. Retry the remediation after resolving the underlying issue.

***

# Finding Details

The **Details** option provides additional information about the finding and affected resource.

Review the details before executing a remediation, especially for:

* Critical findings
* Production resources
* Network-related findings
* Encryption findings
* Shared cloud resources
* Resources with dependencies

***

# Playbook

The **Playbook** option provides remediation guidance associated with the finding.

Use the Playbook to understand:

* Why the finding was generated
* What security configuration needs to be changed
* What remediation action is proposed
* What impact the change may have

***

### Remediation Process

1. Open **Cloud Autofix**.
2. Go to **Fix Available Findings**.
3. Locate the EBS encryption finding.
4. Click **AutoFix**.
5. Verify the target resource.
6. Click **Run Dry Run**.
7. Review the simulation result.
8. If the proposed change is acceptable, click **Execute Remediation**.
9. Confirm the action.
10. Monitor the execution.
11. Open **Remediation Execution Logs**.
12. Verify that the finding is resolved.

If the remediation needs to be reverted and rollback is supported:

1. Open the remediation workflow.
2. Click **Execute Rollback**.
3. Confirm the rollback.
4. Review the execution logs.
5. Verify the resource state.

***

# Finding Status After Remediation

After remediation, the finding may move through different states depending on the execution and verification process.

| Status | Description |
| - | - |
| **Failed** | The remediation could not be completed. |
| **Resolved** | The security issue has been verified as resolved. |
| **Auto-Resolved** | Zero-X detected that the underlying security issue is no longer present. |

***

## Dry Run Fails

Check the following:

1. Cloud account connectivity.
2. Required permissions.
3. Target resource availability.
4. Cloud region.
5. Remediation execution logs.

***

## Remediation Fails

Follow these steps:

1. Open **Remediation Execution Logs**.
2. Review the error message.
3. Verify cloud permissions.
4. Verify that the target resource still exists.
5. Check the cloud account connection.
6. Run the Dry Run again.
7. Retry the remediation after resolving the issue.

***

## Finding Is Still Visible After Remediation

A finding may remain visible until Zero-X verifies the updated cloud configuration.

Check:

* Remediation execution status.
* Finding details.
* Latest scan result.
* Remediation execution logs.

If the issue still exists after the next scan, investigate the resource configuration and remediation result.

***

### During Remediation

* Execute remediation only on the intended resource.
* Review the confirmation information.
* Monitor execution status.
* Keep track of important remediation operations.

### After Remediation

* Verify the remediation result.
* Review execution logs.
* Verify the finding status.
* Check the cloud resource configuration when necessary.
* Confirm the finding does not reappear after the next scan.

***

# Security Considerations

Cloud Autofix can make changes to connected cloud environments.

Before executing a remediation:

* Confirm the target resource.
* Understand the expected change.
* Review the Dry Run result.
* Verify the required cloud permissions.
* Follow your organization's change-management process.
* Use additional caution for production resources.

***

# Quick Reference

| Action | Purpose | Changes Live Resource |
| - | - | - |
| **AutoFix** | Opens the remediation workflow | No |
| **Run Dry Run** | Simulates the remediation | No |
| **Execute Remediation** | Applies the security fix | **Yes** |
| **Execute Rollback** | Reverts a supported remediation | **Yes** |
| **Details** | Shows additional finding information | No |
| **Playbook** | Provides remediation guidance | No |
| **Tour** | Explains the Autofix workflow | No |
| **Logs** | Shows remediation execution history | No |

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.