STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Red Hat Ansible Automation Controller Application Server Security Technical Implementation Guide

Archived

Version

V1R2

Release Date

Oct 25, 2023

SCAP Benchmark ID

S-7e2afba3dc46a26c5de4512be00fc25c1456712c

Total Checks

16

Tags

application
CAT I: 1CAT II: 15CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (16)

V-256896MEDIUMAutomation Controller must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types.V-256897MEDIUMAutomation Controller must use encryption strength in accordance with the categorization of the management data during remote access management sessions.V-256898HIGHAutomation Controller must implement cryptography mechanisms to protect the integrity of information.V-256899MEDIUMThe Automation Controller management interface must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system.V-256900MEDIUMAutomation Controller must use external log providers that can collect user activity logs in independent, protected repositories to prevent modification or repudiation.V-256901MEDIUMAutomation Controller must allocate log record storage capacity and shut down by default upon log failure (unless availability is an overriding concern).V-256902MEDIUMAutomation Controller must be configured to fail over to another system in the event of log subsystem failure.V-256903MEDIUMAutomation Controller's log files must be accessible by explicitly defined privilege.V-256904MEDIUMAutomation Controller must be capable of reverting to the last known good configuration in the event of failed installations and upgrades.V-256905MEDIUMAutomation Controller must be configured to use an enterprise user management system.V-256906MEDIUMAutomation Controller must be configured to authenticate users individually, prior to using a group authenticator.V-256907MEDIUMAutomation Controller must utilize encryption when using LDAP for authentication.V-256908MEDIUMAutomation Controller must use cryptographic mechanisms to protect the integrity of log tools.V-256909MEDIUMAutomation Controller must compare internal application server clocks at least every 24 hours with an authoritative time source.V-256910MEDIUMAutomation Controller must only allow the use of DOD PKI-established certificate authorities for verification of the establishment of protected sessions.V-256911MEDIUMAutomation Controller must install security-relevant software updates within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).