Checklist Summary:

The Red Hat Ansible Automation Controller Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DOD) information systems. This document is meant for use in conjunction with other STIGs, such as the Red Hat Enterprise Linux 8.x STIG or other appropriate operating system STIGs, Postgres DB, AAA, Central Logging, Enclave, Network Infrastructure, and appropriate application SRGs and/or STIGs. This STIG applies to the automation controller component of the Red Hat product Ansible Automation Platform version 2.2. It assumes this product is installed and configured in accordance with the documented installation instructions provided by Red Hat. This STIG also assumes delegation of certain security control implementation to external, integrated enterprise systems including a central identity and access management system, central logging management system, a database, and others as noted below.

Checklist Role:

• Desktop or Mobile Client

Known Issues:

Not provided.

Target Audience:

Parties within the DOD and federal government’s computing environments can obtain the applicable STIG from the DOD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DOD Certificates can obtain the STIG from https://public.cyber.mil/.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

This document is provided under the authority of DODI 8500.01.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DOD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level because some settings may not be configurable in environments outside the DOD architecture

Product Support:

Not provided.

Point of Contact:

disa.stig_spt@mail.mil

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

NEW checklist - 4/13/23
Updated title - 10/26/23

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 10/26/2023