| 4.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
| | | | [1] | Users must ensure that Google Chrome, Microsoft Edge and Firefox implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because Box Tools v4.x can connect to the Box Cloud for
editing Microsoft Office documents. To mitigate, the ISSO shall educate and
prohibit users from using the integrated cloud service capability until the VA
Cloud Security Requirements have been met and the affected assessment and
authorizations (A&A) package has been appropriately updated
- . A vulnerability exists because Box Tools v4.x installs an outdated version of
RestSharp (version 105.1.0). To mitigate, the vendor must maintain all
components during the entire product lifecycle, including responding to
vulnerabilities discovered in components used in the product. System
administrators shall use the latest version of the products where possible and
monitor both the common vulnerabilities and exposures (CVE) Details and
Office of Information and Technology
FOR INTERNAL USE ONLY
NIST National Vulnerability Database (NVD) websites for any new security
vulnerabilities.
| | | [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] | 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] | 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). | | | [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. |
|