2.x |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
| | [1] | Per the Initial Product Review, users must abide by the following constraints:
- Box Drive will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Secure Hash Algorithm 1 (SHA-1) has been disallowed by the National Institute of Standards and Technology (NIST) and is listed as unapproved on the VA Technical Reference Model (TRM) v21.2. The 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”.
| | [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 VA Handbook 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [5] | 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. | | [6] | 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). |
|