Sample Remediation Workflow
Follow the general guidelines provided in the following steps to analyze and remediate findings.
To remediate a finding:
- In the Tenable One Cloud Exposure Console, click on Findings.
- Apply any relevant filters to narrow the scope of displayed findings. See Navigate the Findings Page) for more information.
- Click on the relevant finding to drill-down and view a full analysis of the finding.
-
Review finding details and other relevant information to get a better understanding of, for example:
- What the root cause of the finding is
- The scope of the finding
- The potential risk it imposes on your environment
- An explanation of the severity of the finding.
-
Navigate to the Remediation area and carefully review the steps listed.
Note: If you work with IaC Security, there may be two tabs in this area, IaC and Console, depending on the finding. The IaC tab provides a code-based remediation via pull request, while the Console tab provides a cloud-based remediation. - If there is a legitimate reason not to remediate the finding right now, you can ignore the finding.
-
If you decide that the finding requires corrective action, do one of the following:
- Manually Remediate Findings by following the steps listed. This may include manually triggering a ticketing action for the finding (for example, creating a Jira issue, so that one of your developers can remediate the finding).
Automatically Remediate Findings using the Remediate
button, if available for the finding.Note: To automatically remediate a finding, you need to either: 1) Grant Tenable management permissions for the relevant cloud account during onboarding, or, 2) Provide Tenable one-time credentials to perform the required remediation steps.
- If you manually remediate the finding, you can mark the finding as closed after you remediate it to remove it from the Open Findings page. When an issue is fixed, Tenable automatically detects and auto-resolves it. Since this automatic identification can take a while, you can choose to close it manually, to remove it from the Open Findings page sooner.