6.2.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 3, 4, 5, 6, 7] |
Divest [1, 3, 4, 5, 6, 7] |
Divest [1, 3, 4, 5, 6, 7] |
Divest [1, 3, 4, 5, 6, 7] |
6.4.x |
Unapproved |
Unapproved |
Unapproved |
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] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5, 6, 7] |
Approved w/Constraints [1, 3, 4, 5, 6, 7] |
Approved w/Constraints [1, 3, 4, 5, 6, 7] |
Approved w/Constraints [1, 3, 4, 5, 6, 7] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | Users should check with their supervisor, Information Security Office (ISO) 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. | | [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] | 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. | | [6] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [7] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. |
|