CCI-000132

Enable audit Service

Ensure the audit Subsystem is Installed

Enable auditd Service

Ensure the audit-libs package as a part of audit Subsystem is Installed

Ensure the libaudit1 package as a part of audit Subsystem is Installed

AAA Services configuration audit records must identify where the events occurred.

The Apache web server must produce log records containing sufficient information to establish what type of events occurred.

The ALG must produce audit records containing information to establish where the events occurred.

The Arista router must be configured to produce audit records containing information to establish where the events occurred.

The application server must produce log records containing sufficient information to establish where the events occurred.

The Arista network device must be configured to capture all DOD auditable events.

The application must produce audit records containing enough information to establish which component, feature or function of the application triggered the audit event.

The print-category variable for the configuration of BIND 9.x server logs must be configured to record information indicating which process generated the events.

The Central Log Server must produce audit records containing information to establish where the events occurred.

The DBN-6300 must produce audit records containing information to establish where the events occurred.

The audit log configuration level must be set to request in the Universal Control Plane (UCP) component of Docker Enterprise.

The host operating systems auditing policies for the Docker Engine - Enterprise component of Docker Enterprise must be set.

The DNS server implementation must produce audit records containing information to establish where the events occurred.

The firewall must generate traffic log entries containing information to establish the location on the network where the events occurred.

The FortiGate firewall must generate traffic log entries containing information to establish the network location where the events occurred.

The HP FlexFabric Switch must produce audit records containing information to establish where the events occurred.

The HYCU server must produce audit records containing information to establish when events occurred, where events occurred, the source of the event, the outcome of the event, and identity of any individual or process associated with the event.

The MQ Appliance messaging server must produce log records containing information to establish what type of events occurred.

The WebSphere Liberty Server must log remote session and security activity.

The MQ Appliance network device must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.

The WebSphere Application Server audit event type filters must be configured.

CA VM:Secure product must be installed and operating.

The IDPS must produce audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event.

JBoss must be configured to produce log records that establish which hosted application triggered the events.

The Sentry must produce audit records containing information to establish where the events occurred.

The Juniper router must be configured to produce audit records containing information to establish where the events occurred.

The Mainframe Product must produce audit records containing information to establish where the events occurred.

SQL Server must produce Trace or Audit records containing sufficient information to establish where the events occurred.

The network device must produce audit records containing information to establish where the events occurred.

Nutanix AOS must produce audit records containing information to establish where events occurred.

OHS must have a log format defined for log records that allow the establishment of where within OHS the events occurred.

OHS must have a SSL log format defined for log records that allow the establishment of where within OHS the events occurred.

OHS must have a log file defined for each site/virtual host to capture logs generated that allow the establishment of where within OHS the events occurred.

Oracle WebLogic must produce audit records containing sufficient information to establish where the events occurred.

Prisma Cloud Compute Defender must be deployed to containerization nodes that are to be monitored.

The Riverbed NetProfiler must be configured to automatically generate DOD-required audit records with sufficient information to support incident reporting to a central log server.

The router must be configured to produce audit records containing information to establish where the events occurred.

The SDN controller must be configured to produce audit records containing information to establish where the events occurred.

Innoslate must generate comprehensive audit records.

Symantec ProxySG must produce audit records containing information to establish where the events occurred.

The SMS must produce audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and TPS component which detected the event by sending all audit and system logs to a centralized syslog server.

The UEM Agent must record within each UEM Agent audit record the following information: -date and time of the event -type of event -subject identity -(if relevant) the outcome (success or failure) of the event.

The UEM server must be configured to produce audit records containing information to establish where the events occurred.

The TippingPoint SMS must automatically generate audit records for account changes and actions with containing information needed for analysis of the event that occurred on the SMS and TPS.

The NSX-T Tier-1 Gateway Firewall must generate traffic log entries containing information to establish the details of the event.

The VPN Gateway must generate log records containing information to establish where the events occurred.

Audit records content must contain valid information to allow for proper incident reporting.

The Apache web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events.

Remote hostname must be logged.

HTTP status code must be logged.

The first line of request must be logged.

The macOS system must initiate session audits at system startup, using internal clocks with time stamps for audit records that meet a minimum granularity of one second and can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT), in order to generate audit records containing information to establish what type of events occurred, the identity of any individual or process associated with the event, including individual identities of group account users, establish where the events occurred, source of the event, and outcome of the events including all account enabling actions, full-text recording of privileged commands, and information about the use of encryption for access wireless access to and from the system.

The macOS system must produce audit records containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions.

The macOS system must enable security auditing.

The Ubuntu operating system must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DoD-defined auditable events and actions in near real time.

The Cisco ASA must be configured to produce audit records containing information to establish where the event was detected.

PostgreSQL must produce audit records containing sufficient information to establish where the events occurred.

The Cisco ASA remote access VPN server must be configured to generate log records containing information to establish where the events occurred.

The Cisco router must be configured to produce audit records containing information to establish where the events occurred.

The Cisco ASA must be configured to produce audit records containing information to establish where the events occurred.

The Cisco router must produce audit records containing information to establish where the events occurred.

The Cisco switch must produce audit records containing information to establish where the events occurred.

The Cisco switch must be configured to produce audit records containing information to establish where the events occurred.

The DBMS must produce audit records containing sufficient information to establish where the events occurred.

All audit records must identify where in the container platform the event occurred.

The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish where the events occurred.

The operating system must produce audit records containing information to establish where the events occurred.

SSMC web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events.

AIX must produce audit records containing information to establish where the events occurred.

IBM z/OS Required SMF data record types must be collected.

IBM z/OS must specify SMF data options to assure appropriate activation.

IBM RACF SETROPTS LOGOPTIONS must be properly configured.

IBM z/OS required SMF data record types must be collected.

IBM z/OS must specify SMF data options to ensure appropriate activation.

The ICS must be configured to generate log records containing sufficient information about where, when, identity, source, or outcome of the events.

The Juniper EX switch must be configured to produce audit records containing information to establish where the events occurred.

The ICS must be configured to audit the execution of privileged functions such as accounts additions and changes.

Kubernetes API Server must generate audit records that identify what type of event has occurred, identify the source of the event, contain the event results, identify any users, and identify any containers associated with the event.

MongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.

PowerShell Transcription must be enabled on Windows 10.

OL 8 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.

The Oracle Linux operating system must be configured so that auditing is configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users.

The Automation Controller must generate the appropriate log records.

Rancher RKE2 components must be configured in accordance with the security configuration settings based on DOD security configuration or implementation guidance, including SRGs, STIGs, NSA configuration guides, CTOs, and DTMs.

All audit records must generate the event results within OpenShift.

SUSE operating system audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.

RHEL 9 audit package must be installed.

RHEL 9 audit service must be enabled.

RHEL 9 must label all offloaded audit logs before sending them to the central log server.

Audit records must include where the events occurred.

The VMM must produce audit records containing information to establish where the events occurred.

VAMI must produce log records containing sufficient information to establish what type of events occurred.

Performance Charts must record user access in a format that enables monitoring of remote access.

ESX Agent Manager must record user access in a format that enables monitoring of remote access.

Lookup Service must record user access in a format that enables monitoring of remote access.

The Photon operating system must configure auditd to log to disk.

The vCenter ESX Agent Manager service must produce log records containing sufficient information regarding event details.

VMware Postgres log files must contain required fields.

The Security Token Service must record user access in a format that enables monitoring of remote access.

The vCenter Lookup service must produce log records containing sufficient information regarding event details.

vSphere UI must record user access in a format that enables monitoring of remote access.

The vCenter Perfcharts service must produce log records containing sufficient information regarding event details.

The Photon operating system must enable the auditd service.

The vCenter PostgreSQL service must produce logs containing sufficient information to establish what type of events occurred.

The vCenter STS service must produce log records containing sufficient information regarding event details.

The vCenter UI service must produce log records containing sufficient information regarding event details.

The vCenter VAMI service must produce log records containing sufficient information to establish what type of events occurred.

The web server must produce log records containing sufficient information to establish where within the web server the events occurred.

Ubuntu 22.04 LTS must have the "auditd" package installed.

Ubuntu 22.04 LTS must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions in near real time.

The Enterprise Voice, Video, and Messaging Endpoint must be configured to produce session (call detail) records containing where the connection occurred.

The F5 BIG-IP appliance must generate event log records that can be forwarded to the centralized events log.

The Enterprise Voice, Video, and Messaging Session Manager must produce session (call) records containing where (location) the connection originated.

The F5 BIG-IP appliance must generate traffic log entries containing information to establish the details of the event, including success or failure of the application of the firewall rule.

The F5 BIG-IP appliance must be configured to audit the execution of privileged functions such as accounts additions and changes.

MongoDB must provide audit record generation for DOD-defined auditable events within all DBMS/database components.

The OL 8 audit package must be installed.

SLEM 5 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.

The TPS must provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.

The TippingPoint SMS must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).

TOSS audit records must contain information to establish what type of events occurred, when the events occurred, the source of events, where events occurred, and the outcome of events.

The NSX Distributed Firewall must generate traffic log entries.

The NSX Tier-0 Gateway Firewall must generate traffic log entries.