<Past |
Future> |
2.2.x |
Divest [3, 6, 7, 8] |
Divest [3, 6, 7, 8, 9] |
Divest [3, 6, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.4.x |
Approved w/Constraints [3, 6, 7, 8] |
Divest [3, 6, 7, 8, 9] |
Divest [3, 6, 7, 8, 9] |
Divest [3, 6, 7, 8, 9] |
Divest [8, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.5.x |
Approved w/Constraints [3, 6, 7, 8] |
Divest [3, 6, 7, 8, 9] |
Divest [3, 6, 7, 8, 9] |
Divest [3, 6, 7, 8, 9] |
Divest [8, 9, 10, 11, 12] |
Divest [8, 9, 10, 11, 12] |
Divest [8, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.6.x |
Unapproved |
Approved w/Constraints [3, 6, 7, 8, 9] |
Approved w/Constraints [3, 6, 7, 8, 9] |
Approved w/Constraints [3, 6, 7, 8, 9] |
Approved w/Constraints [8, 9, 10, 11, 12] |
Divest [8, 9, 10, 11, 12] |
Divest [8, 9, 10, 11, 12] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 14, 15] |
Unapproved |
2.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 9, 10, 11, 12] |
Approved w/Constraints [8, 9, 10, 11, 12] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 14, 15] |
Divest [8, 10, 11, 12, 14, 15] |
2.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 9, 10, 11, 12] |
Approved w/Constraints [8, 9, 10, 11, 12] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 14, 15] |
Divest [8, 10, 11, 12, 14, 15] |
2.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 10, 11, 12, 13, 14] |
Approved w/Constraints [8, 10, 11, 12, 13, 14] |
Approved w/Constraints [8, 10, 11, 12, 13, 14] |
Divest [8, 10, 11, 12, 14, 15] |
Divest [8, 10, 11, 12, 14, 15] |
2.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 10, 11, 12, 14, 15] |
Approved w/Constraints [8, 10, 11, 12, 14, 15] |
| | [1] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. 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 and ensure privacy of information compliance protections are in place. | | [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] | 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. | | [4] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. 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 and ensure privacy of information compliance protections are in place. | | [5] | Bio-Rad provdes remote access to the client`s environment via WebEx or Citrix GoToAssist (Citrix online). Remote access must be initiated and controlled by the end-user at all times. | | [6] | 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. | | [7] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [8] | 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. | | [9] | Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), Microsoft Internet Explorer (IE), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [10] | 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. | | [11] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [12] | 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. | | [13] | Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), Microsoft Internet Explorer (IE), Google Chrome, and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. | | [14] | 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. | | [15] | Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Services (IIS), Google Chrome, and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. |
|
Note: |
At the time of writing, version 2.10.1.000 is the most current version. |