7.9.x |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Authorized w/ Constraints [1, 2, 3] |
Authorized w/ Constraints [1, 2, 3] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
Authorized w/ Constraints [2, 3, 4, 5] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
EASendMail is not Federal Information Processing Standards (FIPS) 140-2 certified. This technology will require third party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must ensure that Microsoft Edge, Microsoft .NET Framework, Microsoft Internet Information Services, and Microsoft Outlook are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology should not use Microsoft .NET Compact Framework as it is unapproved for use at this time. | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Microsoft .NET Compact Framework, as it, at the time of writing, requires a POA&M.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M.
Users must ensure that Microsoft Edge, Microsoft Internet Information Services, and Microsoft Outlook are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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. |
|