3.x |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
Approved w/Constraints [1, 3, 4, 5, 6] |
| | [1] | 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. | | [2] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [3] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | [4] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [5] | 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 approved and the user should take the proper steps to decline those installations. | | [6] | 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. |
|