0.x |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved 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 ensure that Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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] | 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. | | [4] | 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. | | [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 ensure that Google Chrome, and Firefox are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize X.509 Public Key Infrastructure (PKI) Certificate Management Protocols, as it, at the time of writing, requires a POA&M.
Per the Initial Product Review, users must abide by the following constraints:
- OpenSC will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Personal Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information.
- Ensure that OpenSC is always updated to the latest version. Given that many vulnerabilities like those related to Application Protocol Data Unit handling and data management are addressed in newer releases, regular patching is essential.
- Regularly audit the use of OpenSC and its cryptographic modules. Engage in penetration testing and code reviews to find security flaws, particularly those related to data handling and cryptographic operations.
- Users should check with their supervisor, 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 approved and the user should take the proper steps to decline those installations.
|
|