Skip to content

Latest commit

 

History

History
61 lines (44 loc) · 4.43 KB

File metadata and controls

61 lines (44 loc) · 4.43 KB

Lab 1: Provisioning a security compliant host

Goal of Lab 1

The goal of this lab is to create a security compliant host at provisioning time in Red Hat Virtualization at the push of a button using Red Hat CloudForms and Ansible Automation. Specifically, in this lab exercise, you will use Red Hat CloudForms and Ansible Automation inside CloudForms for your custom provisioning automation workflow.

Introduction

Red Hat CloudForms provides users the ability to create self-service catalogs. Through the use of catalogs, Red Hat CloudForms provides support for executing free form automation as a service and also allow for multi-tiered service provisioning to deploy layered workloads across hybrid environments. You can create customized dialogs that will give consumers of the services the ability to input just a few parameters and provision the entire service. In addition to using the native ruby language, free form automation workflows using the service catalog of Red Hat CloudForms can call Ansible Tower job templates or Ansible playbooks directly from Red Hat CloudForms.

In this lab exercise, we will execute a custom provisioning service in the Red Hat CloudForms service catalog. From here, we will run customized Ansible provisioning playbooks to provision a Red Hat Enterprise Linux 7.5 host on Red Hat Virtualization that is locked down to a specific SCAP Profile chosen by the user from the Red Hat CloudForms service dialog. Red Hat Enterprise Linux 7.5 ships with Ansible SCAP remediation playbooks for various SCAP Profiles. In this lab exercise, these Ansible playbooks are presented to the user as SCAP Profiles to choose from to lock down the newly provisioned Red Hat Enterprise Linux 7.5 host against the chosen SCAP profile.

As a result, users can easily provision a security compliant host using any of the provided SCAP security profiles in Red Hat Enterprise Linux 7.5. Users also have the ability to use custom security profiles to lock down a provisioned system against your specific security controls. You can easily create custom modified security profiles using SCAP workbench (which is also provided as part of Red Hat Enterprise Linux).

Lab 1.1 Provisioning a security compliant host at the push of a button using Red Hat CloudForms and Ansible Automation

  1. On the CloudForms appliance (cfme-GUID.rhpds.opentlc.com) log in with admin as the user name and r3dh4t1! as the password (if not already logged in).

  2. Navigate to Services → Catalogs.

    200

  3. Order the RHEL 7.5 on RHV service.

    900

  4. Name the VM lab1-vm1, choose the default IP Address 192.168.1.110 , and choose the ssg-rhel7-role-standard SCAP Profile from the drop down. Click on Submit. This will provision a Red Hat Enterprise Linux 7.5 VM in Red Hat Virtualization that is locked down to the ssg-rhel7-role-standard SCAP Profile.

    Warning
    Provisioning and scanning can take up to 10 minutes.

    600

  5. From the Service Requests page, click on the Refresh button at the top until the service request shows Approved. Note that this default approval workflow can be customized.

    600

  6. Navigate to Services → My Services.

    400

  7. Click on the RHEL 7.5 on RHV service and then click on the Provisioning tab to view the Ansible output.

    600

  8. Press the refresh button periodically to refresh the Ansible output.

    Note
    After clicking on refresh you will need to click on the Provisioning tab to view the Ansible output. You can disregard FAILED - RETRYING messages in the output as this is normal.

    400

  9. Review the Ansible provisioning playbook output by scrolling all the way down. Notice that the SCAP remediation has ran and the PLAY RECAP shows no failures.

    400

  10. Go back to the top of the screen and click on the Details tab. Then click on your newly provisioned lab1-vm1 VM.

    400

  11. Notice that the lab1-vm1 VM provisioned successfully and now has a hostname and the IP address you assigned it during provisioning.

    500