STIGQter: STIG Summary: Application Security and Development Security Technical Implementation Guide Version: 5 Release: 1 Benchmark Date: 23 Oct 2020: STIGQter: STIG Summary: Application Security and Development Security Technical Implementation Guide Version: 5 Release: 1 Benchmark Date: 23 Oct 2020:SV-222500r508029_rule
V-222500
SRG-APP-000118
APSC-DV-001280
CAT II
10
Configure the application to protect audit data from unauthorized access. Limit users to roles that are assigned the rights to view, edit or copy audit data, and establish permissions that control access to the audit logs and audit configuration settings.
Review the system documentation and interview the application administrator for details regarding application architecture and logging configuration.
Identify the application components and the logs associated with the components.
Identify the roles and users allowed to access audit information and the circumstances in which they are allowed to read or otherwise access the data.
Identify the methods used to manage audit records and audit components. Typical methods are file system-based, via an application user interface via database access or a combination thereof.
For file system access: Review file system permissions to ensure the audit logs and the application audit components such as executable files and libraries are protected by adequate file permission restrictions.
Permissions must be configured to limit access to only those who have been identified and whose access has been approved.
If file permissions are configured to allow unapproved access, this is a finding.
For application-oriented and database access: Identify the application module that provides access to audit settings and audit data. Attempt to access audit configuration features and logs by using a regular non-privileged application or database user account.
If a non-privileged user account is allowed to access the audit data or the audit configuration settings, this is a finding.
V-222500
False
APSC-DV-001280
Review the system documentation and interview the application administrator for details regarding application architecture and logging configuration.
Identify the application components and the logs associated with the components.
Identify the roles and users allowed to access audit information and the circumstances in which they are allowed to read or otherwise access the data.
Identify the methods used to manage audit records and audit components. Typical methods are file system-based, via an application user interface via database access or a combination thereof.
For file system access: Review file system permissions to ensure the audit logs and the application audit components such as executable files and libraries are protected by adequate file permission restrictions.
Permissions must be configured to limit access to only those who have been identified and whose access has been approved.
If file permissions are configured to allow unapproved access, this is a finding.
For application-oriented and database access: Identify the application module that provides access to audit settings and audit data. Attempt to access audit configuration features and logs by using a regular non-privileged application or database user account.
If a non-privileged user account is allowed to access the audit data or the audit configuration settings, this is a finding.
M
4093