| 1.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9] |
| | | | [1] | Users must ensure that VMware vSphere is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Secure Sockets Layer (SSL), as determined during the time of this writing, an unauthorized technology in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Azure Connected Machine Agent (azcmagent) supports FIPS compliance, but
compliance is primarily achieved by configuring the guest operating system
(OS) to operate in FIPS mode. The agent itself relies on the underlying OS`s
FIPS-validated cryptographic modules for all secure operations.
- Due to potential information security risks, SaaS/PaaS solutions must complete
the Business Integration and Outcomes Service (BIOS) process where a
collaborative effort between Demand Management (DM), Enterprise Program
Management Office Information Assurance (EPMO IA), Digital Transformation
Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology
Officer (CTO), and stakeholders determines the SaaS/PaaS category during the
Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed
to EPMO IA for Analysis and Approval to Operate (ATO) with technical
oversight, acquisition, production, and sustainment provided by DTC.
- This product should be used with a VA-approved container platform that has a
developed and approved baseline configuration with specific hardening
guidance regarding the secure implementation of azcmagent. Please reference
the TRM for the approved solution and the Baseline Configuration
Management website for more information.
- System owners should use the latest version of this product and monitor both
the CVE Details and NIST National Vulnerability Database websites for any new
security vulnerabilities.
- OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply
Chain through Secure Software Development Practices,” and OMB
Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’
ability to use software that is not developed using secure practices. The
attestation form will allow software producers to confirm that they follow those
practices.
VA Supply Chain Risk Management (SR) Policy and VA Handbook 6500.6,
Contract Security, Appendix C states that the contractor (including producers
and resellers) shall comply with Office of Management and Budget (OMB) M-22-18 and M-23-16 when using third-party software on VA information systems
or otherwise affecting the VA information. This includes new software
purchases and software renewals for software developed or modified by major
version change after the issuance date of M-22-18 (September 14, 2022).
| | | [2] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [3] | 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. | | | [4] | 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. | | | [5] | 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. | | | [6] | 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 authorized and the user should take the proper steps to decline those installations. | | | [7] | 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. | | | [8] | 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. | | | [9] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. |
|
