| 1.4.x |
Approved w/Constraints
[1, 2, 3, 4] |
Approved w/Constraints
[1, 2, 3, 4] |
Approved w/Constraints
[1, 2, 3, 4] |
Approved w/Constraints
[1, 3, 4, 5] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
Approved w/Constraints
[1, 3, 5, 6] |
| | | | [1] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Per the [Initial Product Review/Security Assessment Review], users must abide by the following constraints:
- Due to the sensitive VA data that is being collected and processed, Vertiv Environet Alert will require a 3rd party FIPS 140-2 certified solution for encryption.
- The system user or administrator initiating the software should use robust authentication credentials to prevent unauthorized access. Such robustness must include two-factor authentication (2FA) as a minimum, Role-Based Access Control (RBAC) along with periodic and heightened awareness training to ensure administrator capabilities. The products password protection must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5). Ensure that all VA password requirements are met regardinglength and complexity. VA Knowledge Service Control IA-5: Authenticator
Management requires a case sensitive 14-character password comprised of upper-case letters, lower case letters, numbers, and special characters, including at least one of each category. VA defines and enforces at least 50% of characters in the password must be changed when new passwords are created.
- The system user or administrator should configure and use secure port 443.
- The product installation defaults to the root of the operating system drive. The acceptable location is “c:\Program Files\”. Installing it in the default “c:\” is considered High risk vulnerability and should be changed during the installation process.
- Any VA sensitive data that are collected and stored in a database must be secured in accordance with VA Handbook 6500.
| | | [2] | 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [3] | 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. | | | [4] | 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 System Security Officer (ISSO) 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). | | | [5] | 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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [6] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 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 or its successor 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 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device 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 System Security Officer (ISSO) 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). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. |
|
