| 9.0.x |
Approved w/Constraints
[4, 5, 7] |
Approved w/Constraints
[4, 5, 7] |
Approved w/Constraints
[4, 5, 7] |
Approved w/Constraints
[5, 7, 8] |
Approved w/Constraints
[5, 7, 8, 9] |
Approved w/Constraints
[5, 7, 8, 9] |
Approved w/Constraints
[5, 7, 8, 9, 10] |
Approved w/Constraints
[5, 7, 8, 9, 10] |
Approved w/Constraints
[5, 7, 8, 9, 10] |
Approved w/Constraints
[5, 7, 8, 9, 10] |
Approved w/Constraints
[7, 8, 9, 10, 11] |
Approved w/Constraints
[7, 8, 9, 10, 11] |
| | | | [1] | Technology may be used only if configured to operate in FIPS 140-2 Mode by establishing the SSLFIPSEnable directive as specified in the IBM HTTP Server, Version 6 User`s Guide. | | | [2] | Product must be operated with FIPS 140-2 mode enabled. Product must be patched to mitigate known and future security vulnerabilities. | | | [3] | Product must be operated with FIPS 140-2 mode enabled. Product must be patched to mitigate known and future security vulnerabilities.
Per VA Internal Product Review (IPR) of v8.5, hardening of the HTTP Server will be required before it can be deployed in the VA Production Environment. After hardening, the application should be tested within a VA owned lab environment to ensure that it complies with the organization`s functional and security requirements. | | | [4] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [5] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | | [6] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | | [7] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations. | | | [8] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [9] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [10] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [11] | Per the Initial Product Review (IPR), the following constraints must be applied.
-Federal Information Processing Standards (FIPS) 140-2 mode must be enabled.
-Hardening of the HTTP Server may be required before it can be deployed in the VA Production Environment. After hardening, the application must be tested within a Department of Veterans Affairs (VA) owned lab environment to ensure that it complies with the organization`s functional and security requirements.
-The application must be actively managed to ensure that it remains patched and is as secure as possible. It is recommended that a management scheme similar to the one employed to manage Apache web servers be leveraged for IBM HTTP Server |
|
