Security Review

You should already have the MCP Server Terminal open from the previous module.
If it isn’t already running, in the MCP terminal window, start a Goose session by running:

This will start the Goose session

Start with asking Goose to give you a report on the security posture.
In this prompt you’ll ask all three MCP servers to contribute to the report to help you understand at a high level where things stand at this moment.

The output should show you key findings including the number of systems, a summary of operating system versions, any high risk Common Vulnerabilities and Exposures (CVEs), any advisor recommendations.
It should also include top actions that you should take immediately to help address these issues.

Since you specified a report in your prompt, it should be in a format that you could copy and paste into an email or ticketing system to help you justify any maintenance windows that you might need to schedule for this work.

Now you should really delve into Vulnerabilities.

Lets get a high level overview of CVEs first, then work on a remediation plan.

This will give you a total count of CVEs to address across all of your systems.
Then it should give you the top 5 most important with a summary of each. It may even recommend a timeline for fixes.

If it can create a timeline to fix the top 5 CVEs, maybe it can help create a plan to get the whole environment into shape.

Some of these systems aren’t in your environment, so you should do like you did in the last module and focus on frontend and backend systems separately while calling your guid - {guid}.

Start with the frontend systems:

After you finish reviewing the results, repeat with the backend systems.

This helps you see target output from the backend servers connected to your Satellite.
Since they were made from the same base image, the information should be similar, but it may be affected by the Satellite content views as to what fixes are available.

Now, you should see about creating a report that is informed by all of the various MCP servers that you have access to.
To help focus it, let’s get even more specific on the systems and tools used.

This summary should include a summary of what needs to be changed to secure the system, how long it might take for the resolution, benefits of the change, and a recommended action plan.

Infinicorp is NOT currently scanning these systems for regulatory compliance policies like CIS Level 1 Server.
We have a goal to get there by the end of next year for all systems managed by Infinicorp, but we are just starting to figure out how to make that happen.

These MCP servers might be able to help.

Start by asking the MCP servers what you already know - are they being scanned for CIS Level 1 Server?

Reviewing the output you should see that the MCP servers conclude that your systems are not currently CIS Level 1 Server compliant.

It may share a couple ideas on how you can get there, but let’s ask for a specific plan.

Let’s separate this out by your tools again, using Red Hat Lightspeed for the front end and Red Hat Satellite for the backend.

Let’s start with the front end systems:

The output will inform you as to steps to use the compliance service on the Hybrid Cloud Console to create a compliance policy, tailor it, and then scan the system.
Once scanned, there are steps you’ll need to take to remediate any issues that the compliance service finds.

Since the tools are different for the backend, let’s run a prompt on how to use Satellite for compliance scanning:

Much like the previous prompt, the results will tell you how to use Satellite to perform a scan.

The lab environment has limited context available.
To help make sure that you have as consistent of a lab experience as possible, you will exit Goose at the end of each module and restart it in the next module.
In the Goose session enter:

And hit enter.
This will end the Goose session and return you to the terminal prompt.