The application server must log the enforcement actions used to restrict access associated with changes to the application server.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-204797 | SRG-APP-000381 | SRG-APP-000381-AS-000089 | SV-204797r981687_rule | 2025-02-11 | 4 |
| Description |
|---|
| Without logging the enforcement of access restrictions against changes to the application server configuration, it will be difficult to identify attempted attacks, and a log trail will not be available for forensic investigation for after-the-fact actions. Configuration changes may occur to any of the modules within the application server through the management interface, but logging of actions to the configuration of a module outside the application server is not logged. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Log items may consist of lists of actions blocked by access restrictions or changes identified after the fact. |
| ℹ️ Check |
|---|
| Check the application server documentation and logs to determine if enforcement actions used to restrict access associated with changes to the application server are logged. If these actions are not logged, this is a finding. |
| ✔️ Fix |
|---|
| Configure the application server to log the enforcement actions used to restrict access associated with changes to the application server. |