| 3.x |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
Unauthorized, Conditions Required[a] |
| 5.x |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
| | | | [1] | Users must not utilize the ZIP file format, as it is unapproved for use on the TRM.
Users must not utilize the Dropbox, as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- Long Path Tool (v5.5.0.0) will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Personal
Health Information (PHI) / Personably Identifiable Information (PII) or VA sensitive information.
- Administrators must ensure only authorized versions of .NET are installed.
- 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 A&A package has been appropriately updated.
- Administrators must ensure only tested and authorized versions of Long Path Tool are installed.
- Administrators must ensure only tested and authorized versions of Microsoft .NET are installed.
| | | [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] | 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. | | | [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. | | | [6] | Users must not utilize the ZIP file format, as it is unapproved for use on the TRM.
Users must not utilize the Dropbox, as it is unapproved for use on the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because Long Path Tool (v5.5.0.0) is not Federal
Information Processing Standards (FIPS) 140-2 (or its successor) certified. To
mitigate, Long Path Tool (v5.5.0.0) will require a 3rd party FIPS 140-2 (or its
successor) certified solution for any data containing Personal Health
Information (PHI) / Personably Identifiable Information (PII) or VA sensitive
information.
- A vulnerability exists because Long Path Tool (v5.5.0.0) requires the
installation of Microsoft .NET 3.5 (includes .NET 2.0 & 3.0). To mitigate,
Administrators must ensure only approved versions of .NET are installed.
- A vulnerability exists because Long Path Tool (v5.5.0.0) offers commercial
cloud services. 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 A&A package has been
appropriately updated.
- A vulnerability exists because Long Path Tool (v5.5.0.0) provides an option to
“update to the latest version” from the help menu. To mitigate, Administrators
must ensure only tested and approved versions of Long Path Tool are
installed.
- A vulnerability exists because Long Path Tool (v5.5.0.0) installs older and
UNAPPROVED versions of Microsoft .NET framework (2.0 and 3.0). To
mitigate, Administrators must ensure only tested and approved versions of
Microsoft .NET are installed.
|
|