Rule ID
SV-259231r960939_rule
Version
V2R1
CCIs
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system, and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools. Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, they could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.
Verify User ownership, Group ownership, and permissions on the "edb_audit" directory: > ls -ld <path-to-data-directory>/edb_audit If the User owner is not "enterprisedb", this is a finding. If the Group owner is not "enterprisedb", this is a finding. If the directory is more permissive than 700, this is a finding. The default path for the edb_audit directory is /var/lib/edb/as<version>/data (PGDATA), but this will vary according to local circumstances.
Run these commands as the "root" user (or user with sudo privileges) from the EDB Postgres Advanced Server data (PGDATA) directory: > chown enterprisedb edb_audit > chgrp enterprisedb edb_audit > chmod 700 edb_audit The default path for the edb_audit directory is /var/lib/edb/as<version>/data (PGDATA), but this will vary according to local circumstances.