| V-81193 | | The WebSphere Application Server maximum in-memory session count must be set according to application requirements. | Application management includes the ability to control the number of sessions that utilize an application by all accounts and/or account types. Limiti... |
| V-81195 | | The WebSphere Application Server admin console session timeout must be configured. | An attacker can take advantage of user sessions that are left open, thus bypassing the user authentication process.
To thwart the vulnerability of op... |
| V-81197 | | The WebSphere Application Server automatic repository checkpoints must be enabled to track configuration changes. | Without enabling repository checkpoints, you will not be able to determine the history of changes to WebSphere configuration files, and who made those... |
| V-81203 | | The WebSphere Application Server security auditing must be enabled. | Security auditing will not be performed unless the audit security subsystem has been enabled. Global security must be enabled for the security audit s... |
| V-81205 | | The WebSphere Application Server groups in the user registry mapped to WebSphere auditor roles must be configured in accordance with the security plan. | Logging must be utilized in order to track system activity, assist in diagnosing system issues, and provide evidence needed for forensic investigation... |
| V-81207 | | The WebSphere Application Server users in the WebSphere auditor role must be configured in accordance with the System Security Plan. | Logging must be utilized in order to track system activity, assist in diagnosing system issues, and provide evidence needed for forensic investigation... |
| V-81209 | | The WebSphere Application Server audit event type filters must be configured. | Logging must be utilized in order to track system activity, assist in diagnosing system issues, and provide evidence needed for forensic investigation... |
| V-81211 | | The WebSphere Application Server audit service provider must be enabled. | Logging must be utilized in order to track system activity, assist in diagnosing system issues, and provide evidence needed for forensic investigation... |
| V-81213 | | The WebSphere Application Server users in a local user registry group must be authorized for that group. | Application servers provide remote access capability and must be able to enforce remote access policy requirements or work in conjunction with enterpr... |
| V-81215 | | The WebSphere Application Server Quality of Protection (QoP) must be set to use TLSv1.2 or higher. | Quality of Protection specifies the security level, ciphers, and mutual authentication settings for the Secure Socket Layer (SSL/TLS) configuration.... |
| V-81221 | | The WebSphere Application Server security cookies must be set to HTTPOnly. | Web applications use cookies to track users across requests. These cookies, while typically not sensitive in themselves, connect you to your existing ... |
| V-81227 | | The WebSphere Application Server users in the admin role must be authorized. | Strong access controls are critical to securing the application server. Access control policies (e.g., identity-based policies, role-based policies, a... |
| V-81229 | | The WebSphere Application Server LDAP groups must be authorized for the WebSphere role. | Strong access controls are critical to securing the application server. Access control policies (e.g., identity-based policies, role-based policies, a... |
| V-81231 | | The WebSphere Application Server users in a LDAP user registry group must be authorized for that group. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary... |
| V-81233 | | The WebSphere Application Server management interface must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. | Application servers are required to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system management inter... |
| V-81235 | | The WebSphere Application Server management interface must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. | To establish acceptance of system usage policy, a click-through banner at the application server management interface logon is required. The banner sh... |
| V-81239 | | The WebSphere Application Server must allocate JVM log record storage capacity in accordance with organization-defined log record storage requirements. | JVM logs are logs used to store application and runtime related events, rather than audit related events. They are mainly used to diagnose application... |
| V-81241 | | The WebSphere Application Server must allocate audit log record storage capacity in accordance with organization-defined log record storage requirements. | The proper management of log records not only dictates proper archiving processes and procedures be established, it also requires allocating enough st... |
| V-81243 | | The WebSphere Application Server must provide an immediate real-time alert to authorized users of all log failure events requiring real-time alerts. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process logs as required. Log processing failures includ... |
| V-81247 | | The WebSphere Application Server audit subsystem failure action must be set to Log warning. | Logs are essential to monitor the health of the system, investigate changes that occurred to the system, or investigate a security incident. When log ... |
| V-81255 | | The WebSphere Application Server must protect log information from unauthorized modification. | WebSphere uses role-based access controls to restrict access to log data. To take advantage of this capability, WebSphere administrators must identify... |
| V-81257 | | The WebSphere Application Server must protect log information from unauthorized deletion. | WebSphere uses role based access controls to restrict access to log data. To take advantage of this capability, WebSphere administrators must identify... |
| V-81259 | | The WebSphere Application Server wsadmin file must be protected from unauthorized access. | Protecting log data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and appli... |
| V-81261 | | The WebSphere Application Server wsadmin file must be protected from unauthorized modification. | Protecting log data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and appli... |
| V-81263 | | The WebSphere Application Server wsadmin file must be protected from unauthorized deletion. | Protecting log data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and appli... |
| V-81265 | | The WebSphere Application Server must be configured to encrypt log information. | Protection of log records is of critical importance. Encrypting log records provides a level of protection that does not rely on host-based protection... |
| V-81267 | | The WebSphere Application Server must be configured to sign log information. | Protection of log records is of critical importance. Encrypting log records provides a level of protection that does not rely on host-based protection... |
| V-81269 | | The WebSphere Application Server process must not be started from the command line with the -password option. | The use of the -password option to launch a WebSphere process from the command line can result in a security exposure. Password information may become... |
| V-81271 | | The WebSphere Application Server files must be owned by the non-root WebSphere user ID. | Having files owned by the root or administrator user is an indication that the WebSphere processes are being run with escalated privileges. Running as... |
| V-81277 | | The WebSphere Application Server must be run as a non-admin user. | Running WebSphere as an admin user gives attackers immediate admin privileges in the event the WebSphere processes are compromised.
Best practice is... |
| V-81279 | | The WebSphere Application Server must disable JSP class reloading. | Application servers provide a myriad of differing processes, features, and functionalities. Some of these processes may be deemed to be unnecessary or... |
| V-81293 | | The WebSphere Application Server must prohibit or restrict the use of nonsecure ports, protocols, modules, and/or services as defined in the PPSM CAL and vulnerability assessments. | Some networking protocols may not meet organizational security requirements to protect data and components.
Application servers natively host a numbe... |
| V-81299 | | The WebSphere Application Server LDAP user registry must be used. | To assure accountability and prevent unauthorized access, application server users must be uniquely identified and authenticated. This is typically ac... |
| V-81305 | | The WebSphere Application Server local file-based user registry must not be used. | WebSphere does not provide direct audit of changes to the built-in file registry. The built-in file registry must not be used to support user logon ac... |
| V-81311 | | The WebSphere Application Server multifactor authentication for network access to privileged accounts must be used. | Multifactor authentication creates a layered defense and makes it more difficult for an unauthorized person to access the application server. If one f... |
| V-81325 | | The WebSphere Application Server must provide security extensions to extend the SOAP protocol and provide secure authentication when accessing sensitive data. | Application servers may provide a web services capability that could be leveraged to allow remote access to sensitive application data. A web service ... |
| V-81329 | | The WebSphere Application Server must provide security extensions to extend the SOAP protocol and provide secure authentication when accessing sensitive data. | Application servers may provide a web services capability that could be leveraged to allow remote access to sensitive application data. A web service,... |
| V-81333 | | The WebSphere Application Server must authenticate all network-connected endpoint devices before establishing any connection. | Device authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type a... |
| V-81341 | | The WebSphere Application Server must authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. | Device authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type a... |
| V-81351 | | The WebSphere Application Server must prohibit the use of cached authenticators after an organization-defined time period. | When the application server is using PKI authentication, a local revocation cache must be stored for instances when the revocation cannot be authentic... |
| V-81361 | | The WebSphere Application Server must use signer for DoD-issued certificates. | The cornerstone of PKI is the private key used to encrypt or digitally sign information. The key by itself is a cryptographic value that does not cont... |
| V-81365 | | The WebSphere Application Server must utilize FIPS 140-2-approved encryption modules when authenticating users and processes. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon... |
| V-81367 | | The WebSphere Application Server must accept Personal Identity Verification (PIV) credentials from other federal agencies to access the management interface. | Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting ... |
| V-81369 | | The WebSphere Application Server must use DoD-approved Signer Certificates. | Class 3 PKI certificates are used for servers and software signing rather than for identifying individuals. Class 4 certificates are used for business... |
| V-81371 | | The WebSphere Application Servers must not be in the DMZ. | The application server consists of the management interface and hosted applications. By separating the management interface from hosted applications, ... |
| V-81373 | | The WebSphere Application Server DoD root CAs must be in the trust store. | This control focuses on communications protection at the session, versus packet level.
At the application layer, session IDs are tokens generated by ... |
| V-81375 | | The WebSphere Application Server personal certificates in all keystores must be issued by an approved DoD CA. | Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD syst... |
| V-81385 | | The WebSphere Application Server high availability applications must be installed on a cluster. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-81389 | | The WebSphere Application Server thread pool size must be defined according to application load requirements. | A thread pool enables components of the application server to reuse threads, which eliminates the need to create new threads at run time. Creating new... |
| V-81391 | | The WebSphere Application Server must remove all export ciphers to protect the confidentiality and integrity of transmitted information. | Export grade encryption suites are not strong and do not meet DoD requirements. The encryption for the session becomes easy for the attacker to break.... |
| V-81393 | | The WebSphere Application Server distribution and consistency services (DCS) transport links must be encrypted. | A Core Group (HA Domain) is a component of the high availability manager function. It can contain stand-alone servers, cluster members, node agents, a... |
| V-81395 | | The WebSphere Application Server plugin must be configured to use HTTPS only. | The Web server plug-in transmits information from the Web server to the Web container over HTTP by default. Extra steps must be taken to protect the t... |
| V-81397 | | The WebSphere Application Server must remove organization-defined software components after updated versions have been installed. | By default, when updating WebSphere application server, the older version of binaries are saved in case a "roll back" is necessary. Not keeping the ol... |
| V-81399 | | The WebSphere Application Server must apply the latest security fixes. | Security vulnerabilities are often addressed by testing and applying the latest security patches and fix packs. Latest fixpacks can be found at: http:... |
| V-81401 | | The WebSphere Application Server must install security-relevant software updates within the time period directed by an authoritative source (e.g., IAVMs, CTOs, DTMs, and STIGs). | Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovere... |
| V-81237 | | The WebSphere Application Server must generate log records when successful/unsuccessful attempts to access subject privileges occur. | Accessing a subject's privileges can be used to elevate a lower-privileged subject's privileges temporarily in order to cause harm to the application ... |
| V-81245 | | The WebSphere Application Server must alert the SA and ISSO, at a minimum, in the event of a log processing failure. | Logs are essential to monitor the health of the system, investigate changes that occurred to the system, or investigate a security incident. When log ... |
| V-81249 | | The WebSphere Application Server must shut down by default upon log failure (unless availability is an overriding concern). | It is critical that, when a system is at risk of failing to process logs, it detects and takes action to mitigate the failure. Log processing failures... |
| V-81251 | | The WebSphere Application Server high availability applications must be configured to fail over to another system in the event of log subsystem failure. | This requirement is dependent upon system MAC and availability. If the system MAC and availability do not specify redundancy requirements, this requir... |
| V-81253 | | The WebSphere Application Server must be configured to protect log information from any type of unauthorized read access. | WebSphere uses role-based access controls to restrict access to log data. To take advantage of this capability, WebSphere administrators must identify... |
| V-81273 | | The WebSphere Application Server sample applications must be removed. | WebSphere samples are not intended for use in a production environment. Do not run them there, as they create significant security risks. In particula... |
| V-81275 | | The WebSphere Application Server must remove JREs left by web server and plug-in installers for web servers and plugins running in the DMZ. | When you install IBM HTTP Server, the installer leaves behind a JRE. Remove this JRE, as it provides functions that are not needed by the Web server o... |
| V-81377 | | The WebSphere Application Server must be configured to perform complete application deployments when using A/B clusters. | Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information syste... |
| V-81379 | | The WebSphere Application servers with an RMF categorization of high must be in a high-availability (HA) cluster. | This requirement is dependent upon system MAC and confidentiality. If the system MAC and confidentiality levels do not specify redundancy requirements... |
| V-81381 | | The WebSphere Application Server must not generate LTPA keys automatically. | Automated LTPA key generation can create unplanned outages. Plan to change your LTPA keys during a scheduled outage. Distribute the new keys to all no... |
| V-81383 | | The WebSphere Application Server must periodically regenerate LTPA keys. | The encryption of authentication information that is exchanged between servers involves the Lightweight Third-Party Authentication (LTPA) mechanism. L... |
| V-81387 | | The WebSphere Application Server memory session settings must be defined according to application load requirements. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-81199 | | The WebSphere Application Server administrative security must be enabled. | In previous releases of WebSphere® Application Server, when a user enabled global security, both administrative and application security were enabled.... |
| V-81201 | | The WebSphere Application Server bus security must be enabled. | A service integration bus is a group of one or more application servers or server clusters in a WebSphere® Application Server cell that cooperate to p... |
| V-81217 | | The WebSphere Application Server global application security must be enabled. | Application security enables security for the applications in your environment. This setting provides application isolation and meets security require... |
| V-81219 | | The WebSphere Application Server Single Sign On (SSO) must have SSL enabled for Web and SIP Security. | Remote management access is accomplished by leveraging common communication protocols and establishing a remote connection to the application server v... |
| V-81223 | | The WebSphere Application Server Java 2 security must be enabled. | Java 2 security provides a policy-based fine grained access control mechanism that increases overall system integrity by checking for permissions befo... |
| V-81225 | | The WebSphere Application Server Java 2 security must not be bypassed. | WebSphere provides a passive filter mechanism that will allow administrators to set Java 2 security in the admin console as enabled while still allowi... |
| V-81343 | | The WebSphere Application Server application security must be enabled for each security domain except for publicly available applications specified in the System Security Plan. | By default, all administrative and user applications in WebSphere® Application Server use the global security configuration. For example, a user regis... |
| V-81347 | | The WebSphere Application Server secure LDAP (LDAPS) must be used for authentication. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.
Application servers... |
| V-81357 | | The WebSphere Application Server default keystore passwords must be changed. | The cornerstone of the PKI is the private key used to encrypt or digitally sign information.
If the private key is stolen, this will lead to the com... |
