<Past |
Future> |
8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.x |
Approved w/Constraints [3, 4, 6] |
Approved w/Constraints [3, 4, 6] |
Divest [3, 4, 7, 8, 9] |
Divest [3, 4, 8, 9, 10, 11] |
Divest [4, 9, 10, 12, 13, 14] |
Divest [4, 9, 10, 12, 13, 14] |
Divest [4, 9, 10, 12, 13, 14] |
Divest [4, 9, 10, 13, 14, 15] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.x |
Unapproved |
Unapproved |
Divest [3, 4, 7, 8, 9] |
Approved w/Constraints [3, 4, 8, 9, 10, 11] |
Approved w/Constraints [4, 9, 10, 12, 13, 14] |
Approved w/Constraints [4, 9, 10, 12, 13, 14] |
Approved w/Constraints [4, 9, 10, 12, 13, 14] |
Approved w/Constraints [4, 9, 10, 13, 14, 15] |
Approved w/Constraints [4, 9, 10, 13, 14, 15] |
Approved w/Constraints [4, 9, 10, 13, 14, 15] |
Approved w/Constraints [4, 9, 10, 13, 14, 15] |
Approved w/Constraints [4, 9, 10, 13, 14, 15] |
| | [1] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | [2] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that an approved version of Microsoft .NET Framework is installed prior to installing a new instance of LinkWare Personal Computer (PC) Cable Test Management Software. If a version of Microsoft .NET Framework is not installed, the technology will automatically install Microsoft .NET Framework 4.5.2, which is unallowed by TRM. | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that an approved version of Microsoft .NET Framework is installed prior to installing a new instance of LinkWare Personal Computer (PC) Cable Test Management Software. If a version of Microsoft .NET Framework is not installed, the technology will automatically install Microsoft .NET Framework 4.5.2, which is unallowed by TRM.
Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft .NET Framework and Microsoft Excel are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. | | [8] | 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. | | [9] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. | | [11] | 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. | | [12] | 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 VA Handbook 6500. | | [13] | 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. | | [14] | 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. | | [15] | 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. |
|
Note: |
At the time of writing, version 11.2 is the most current version, released 10/01/2022. |