1.x |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints [1, 2, 3, 4, 5, 6] |
| | [1] | Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
The Federal Processing Standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology must not be used to handle any data containing PHI/PII or VA sensitive information, unless FIPS 140-2 encryption can be enabled, or a 3rd party FIPS 140-2 certified solution [is or can be] deployed to protect it.
Per the Security Assessment Review, users must abide by the following constraints:
- VA utilizes the risk-based decision process defined in the VA Plan of Action and Milestone (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 Information System Security Officer (ISSO) and System Stewards
for pre-existing systems to enter a high or higher POA&M for the “TRM Unapproved technology”.
- To mitigate, the vendor must maintain all third-party components during the entire product lifecycle, including responding to
vulnerabilities discovered in third-party components used in the product.
- Administrators should remain aware of the default path install and change to authorized VA standard (if able).
- Use of mobile code should comply with the requirements of the Application Security and Development.
| | [2] | 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. | | [3] | 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). | | [4] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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] | 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. |
|