| 5.x |
Approved w/Constraints
[3, 5, 6] |
Approved w/Constraints
[3, 5, 6] |
Approved w/Constraints
[3, 5, 6] |
Approved w/Constraints
[3, 5, 6] |
Approved w/Constraints
[5, 7, 8] |
Approved w/Constraints
[7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[7, 8, 9, 10, 11, 12] |
Approved w/Constraints
[8, 9, 10, 11, 12, 13] |
Approved w/Constraints
[8, 9, 10, 12, 13, 14] |
Approved w/Constraints
[8, 9, 10, 12, 13, 14] |
Approved w/Constraints
[8, 9, 10, 12, 13, 14] |
Approved w/Constraints
[8, 9, 10, 12, 13, 14] |
| | | | [1] | LDD database server and its components must adhere to VA Baseline Configuration Standards. MS SQL Server must be used unless a waiver, is signed by the Demand Management Office and based upon a recommendation from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology
LDD should not be used for any data containing PHI/PII, sensitive information because it lacks FIPS 140-2 certified encryption. Thus, ensure use of a FIPS 140-2 validated cryptographic module leveraged off of systems interfacing with LDD. 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 specified in VA Handbook 6500 SC 28: Protection of Information at Rest, system owners must ensure that FIPS 140-2 compliant encryption is employed at all times.
The system user or administrator initiating the LDD process should have robust authentication credentials that prevent unauthorized or casual access. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [3] | 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 approved and the user should take the proper steps to decline those installations. | | | [4] | LDD database server and its components must adhere to VA Baseline Configuration Standards. MS SQL Server must be used unless a waiver, is signed by the Demand Management Office and based upon a recommendation from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology
LDD should not be used for any data containing PHI/PII, sensitive information because it lacks FIPS 140-2 certified encryption. Thus, ensure use of a FIPS 140-2 validated cryptographic module leveraged off of systems interfacing with LDD. 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 specified in VA Handbook 6500 SC 28: Protection of Information at Rest, system owners must ensure that FIPS 140-2 compliant encryption is employed at all times.
The system user or administrator initiating the LDD process should have robust authentication credentials that prevent unauthorized or casual access. | | | [5] | LDD database server and its components must adhere to VA Baseline Configuration Standards. MS SQL Server must be used unless a waiver, is signed by the Demand Management Office and based upon a recommendation from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology
LDD should not be used for any data containing PHI/PII, sensitive information because it lacks FIPS 140-2 certified encryption. Thus, ensure use of a FIPS 140-2 validated cryptographic module leveraged off of systems interfacing with LDD. 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 specified in VA Handbook 6500 SC 28: Protection of Information at Rest, system owners must ensure that FIPS 140-2 compliant encryption is employed at all times.
The system user or administrator initiating the LDD process should have robust authentication credentials that prevent unauthorized or casual access.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Google Chrome, and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [6] | 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. | | | [7] | 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. | | | [8] | Users should check with their supervisor, Information System Security Officer (ISSO) 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 approved and the user should take the proper steps to decline those installations. | | | [9] | This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- LDD database server and its components must adhere to VA Baseline Configuration Standards. Only VA approved database technologies are permitted for use. VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO, ISO and SS for pre-existing systems to enter a high or higher POA&M for the “TRM Unapproved technology`.
- Ensure use of a FIPS 140-2 certified cryptographic solution is in place when applicable.
- The system user or administrator initiating the LDD process should have robust authentication credentials that prevent unauthorized or casual access.
| | | [10] | 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. | | | [11] | 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). | | | [12] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | | [13] | 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. | | | [14] | 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. |
|
