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

Log records can be generated from various components within the web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific web server functionalities may be logged as well. The web server must allow the definition of what events are to be logged. As conditions change, the number and types of events to be logged may change, and the web server must be able to facilitate these changes.

The minimum list of logged events should be those pertaining to system startup and shutdown, system access, and system authentication events. If these events are not logged at a minimum, any type of forensic investigation would be missing pertinent information needed to replay what occurred.

Satisfies: SRG-APP-000089-WSR-000047, SRG-APP-000093-WSR-000053, SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000098-WSR-000059, SRG-APP-000099-WSR-000061, SRG-APP-000092-WSR-000055

Verify that SSMC generates log records for system access by doing the following:

1. Log on to SSH as ssmcadmin. Press "X" to escape to general bash shell.

2. Execute the following commands:

a. $ sudo /ssmc/bin/config_security.sh -o tcp_access_log -a status TCP access logging is enabled

If the command output does not read "TCP access logging is enabled", this is a finding.

b. $ sudo /ssmc/bin/config_security.sh -o http_access_log -f -a status HTTP access logging is enabled

If the command output does not read "HTTP access logging is enabled", this is a finding.

Configure SSMC to generate log records for system access by doing the following:

1. Log on to SSH as ssmcadmin. Press "X" to escape to general bash shell.

2. Execute the following commands:

$ sudo /ssmc/bin/config_security.sh -f -o  tcp_access_log -a enable

$ sudo /ssmc/bin/config_security.sh -f -o  http_access_log -f -a enable