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-222508r508029_rule
V-222508
SRG-APP-000290
APSC-DV-001360
CAT II
10
Cryptographically hash the audit tool files used by the application. Store and protect the generated hash values for future reference.
Review the system documentation and interview the application administrator for details regarding application architecture, audit methods, and provided audit tools.
Identify the location of the application audit tools.
Separate audit tools will be file-oriented in nature, e.g., the application includes a separate executable file or library that when invoked allows users to view and manipulate logs.
If the application does not provide a separate tool in the form of a file which provides an ability to view and manipulate application log data, query data, or generate reports, this requirement is not applicable.
If the system hosting the application has a separate file monitoring utility installed that is configured to identify changes to audit tools and alarm on changes to audit tools, this is not applicable.
Ask application administrator to demonstrate the cryptographic hashing mechanisms used to create the one way hashes that can be used to validate the integrity of audit tools.
For example, "shasum /path/to/file > checksum.filename".
Ask the application administrator to provide the list of checksum values and the associated file names of the audit tools.
If a cryptographic checksum or hash value of the audit tool file is not created for future reference, this is a finding.
V-222508
False
APSC-DV-001360
Review the system documentation and interview the application administrator for details regarding application architecture, audit methods, and provided audit tools.
Identify the location of the application audit tools.
Separate audit tools will be file-oriented in nature, e.g., the application includes a separate executable file or library that when invoked allows users to view and manipulate logs.
If the application does not provide a separate tool in the form of a file which provides an ability to view and manipulate application log data, query data, or generate reports, this requirement is not applicable.
If the system hosting the application has a separate file monitoring utility installed that is configured to identify changes to audit tools and alarm on changes to audit tools, this is not applicable.
Ask application administrator to demonstrate the cryptographic hashing mechanisms used to create the one way hashes that can be used to validate the integrity of audit tools.
For example, "shasum /path/to/file > checksum.filename".
Ask the application administrator to provide the list of checksum values and the associated file names of the audit tools.
If a cryptographic checksum or hash value of the audit tool file is not created for future reference, this is a finding.
M
4093