Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The WebSphere Liberty Server must be configured to encrypt log information.
Description
Discussion Text
Protection of log records is of critical importance. Encrypting log records provides a level of protection that does not rely on host-based protections that can be accidentally misconfigured, such as file system permissions. Cryptographic mechanisms are the industry-established standard used to protect the integrity of log data. An example of a cryptographic mechanism is the computation and application of a cryptographic-signed hash using asymmetric cryptography.
- The security feature (appSecurity-2.0) must be defined in order to configure a user registry for the servlet to authenticate against.
- The audit feature (audit-1.0) must be defined in order to generate audit records.
- The servlet feature (servlet-3.1) must be defined to be able to deploy a web application.
- The ejb feature (ejbLite-3.1) must be defined to be able to deploy an ejb application.
- The ssl feature (ssl-1.0) must be defined to be able to generate and use certificates to sign and encrypt logs.
- The ldap feature (ldapRegistry-3.0) must be defined in order to configure an enterprise-level user registry to authenticate users against.
When the audit-1.0 feature is defined, all supported audit events will be captured and logged to an audit.log located under ${server.config.dir}/logs.
The audit log that is currently being logged to is called audit.log. When an audit log fills to a configured maximum capacity, it is archived with a timestamp with the naming convention audit_<timestamp>.log and new records are written to audit.log.
The audit logs are found under the ${server.config.dir}/logs directory and are named audit.log for the most recent, and audit_<timestamp>.log for any archived logs.
One keystore needs to be created (ikeyman as part of the JDK may be used) and a personal certificate created. This certificate is used to encrypt the logs. The audit configuration needs to define the location of this keystore, its password, and the alias of the certificate used to encrypt the logs. As an example:
<keyStore
id="auditEncKeyStore"
password="Liberty"
location="${server.config.dir}/resources/security/AuditEncryptionKeyStore.jks"
type="JKS" />
<keyStore
id="auditSignKeyStore"
password="{xor}EzY9Oi0rJg=="
location="${server.config.dir}/resources/security/AuditSigningKeyStore2.jks"
type="JKS" />
<auditFileHandler
encrypt="true"
encryptAlias="auditencryption"
encryptKeyStoreRef="auditEncKeyStore"
</auditFileHandler>
Satisfies: SRG-APP-000126-AS-000085, SRG-APP-000118-AS-000078, SRG-APP-000267-AS-000170
- The security feature (appSecurity-2.0) must be defined in order to configure a user registry for the servlet to authenticate against.
- The audit feature (audit-1.0) must be defined in order to generate audit records.
- The servlet feature (servlet-3.1) must be defined to be able to deploy a web application.
- The ejb feature (ejbLite-3.1) must be defined to be able to deploy an ejb application.
- The ssl feature (ssl-1.0) must be defined to be able to generate and use certificates to sign and encrypt logs.
- The ldap feature (ldapRegistry-3.0) must be defined in order to configure an enterprise-level user registry to authenticate users against.
When the audit-1.0 feature is defined, all supported audit events will be captured and logged to an audit.log located under ${server.config.dir}/logs.
The audit log that is currently being logged to is called audit.log. When an audit log fills to a configured maximum capacity, it is archived with a timestamp with the naming convention audit_<timestamp>.log and new records are written to audit.log.
The audit logs are found under the ${server.config.dir}/logs directory and are named audit.log for the most recent, and audit_<timestamp>.log for any archived logs.
One keystore needs to be created (ikeyman as part of the JDK may be used) and a personal certificate created. This certificate is used to encrypt the logs. The audit configuration needs to define the location of this keystore, its password, and the alias of the certificate used to encrypt the logs. As an example:
<keyStore
id="auditEncKeyStore"
password="Liberty"
location="${server.config.dir}/resources/security/AuditEncryptionKeyStore.jks"
type="JKS" />
<keyStore
id="auditSignKeyStore"
password="{xor}EzY9Oi0rJg=="
location="${server.config.dir}/resources/security/AuditSigningKeyStore2.jks"
type="JKS" />
<auditFileHandler
encrypt="true"
encryptAlias="auditencryption"
encryptKeyStoreRef="auditEncKeyStore"
</auditFileHandler>
Satisfies: SRG-APP-000126-AS-000085, SRG-APP-000118-AS-000078, SRG-APP-000267-AS-000170
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.