Automated Smart Management Workshop: Remediate Vulnerability


This use-case will demonstrate how to:



1. Prepare to Remediate a Vulnerability

Now that you have some familiarity with the Insights Services let’s go correct an issue. In this example it will be a specific vulnerability




NOTE In order to correct this vulnerability a reboot is required. If you desire to reboot later, select “turn off autoreboot”



At this point a playbook that has been created is available in the Remediations section of Insights. Let’s go there next:

NOTE That the playbook you created in the step above is available.

NOTE In this example we will execute the Remediation through the Ansible Automation Platform

2. Execute a Remediation Using AAP

login screen

The Remediation playbooks from Insights are consumed by AAP through the use of a specific type of Project. We set this project up for you during the Setup / Insights job run. Let’s sync this project with Insights to pull down the latest playbooks.

Before doing the sync let’s look at the Insights Credential that was also setup during the Setup / Insights job run. This credential is used to login to your account on the Red Hat Portal. For this use case it is specifically used to connect an AAP Project with the Insights Remediation Service.



Next let’s sync the Project and create the Job Template

NOTE That the last job status says “Successful” because the project was sync’d when we created the playbook during the Setup / Insights workflow template job run.

Let’s create a Job Template that uses this playbook.

NOTE The diagram below depicts the job template that should be created.


Now let’s execute this job template to remediate the vulnerability


NOTE In the screenshot above observe that the vulnerable package(s) was updated, system was rebooted and the insights-client was run again.

Let’s go validate that the Remediation playbook eliminated the vulnerability.

3. Verify Remediation on Red Hat Insights

Login to using portal account credentials

First verify that the Remediation was run.


Now let’s go look at the CVE to verify that is no longer an impacted system.


This completes this exercise.