| 3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8] |
| | | | [1] | Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, My Structured Query Language (MySQL) Database - Commercial Edition, and Microsoft Internet Information Services (IIS) are 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:
- YAF.NET will require a 3rd party FIPS 140-2 certified solution for any data containing Protected Health Information (PHI) / Personally Identifiable
Information (PII) or VA sensitive information.
- The use of open-source products, lacking any vendor support. Hosting potentially critical VA production systems may pose severe security risks to the
VA. Users must check with their supervisor, ISSO or local OIT representative for permission to download and use this software. The system user or
administrator initiating the YAF.NET process shall have robust Multi-factor Authentication (MFA) credentials that prevent unauthorized or casual access.
- Administrators must ensure that a TRM approved database management system is used and configured to adhere to the VA Baseline Configuration
Standards.
- Administrators must ensure that Microsoft Internet Information Services (IIS) is implemented and configured to adhere to VA Baseline Configuration Standards
and YAF.NET, in no way, modifies the baseline settings.
| | | [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 both VA Handbook 6500 and VA Directive 6500. | | | [3] | 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. | | | [4] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [5] | 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. | | | [6] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details. | | | [7] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | | [8] | 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. |
|
