<Past |
Future> |
5.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.2.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2007.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2008.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2008.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2009.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2010.1 (est) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2011.1.2 |
Divest [3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2012.1 |
Approved w/Constraints [3, 5, 7, 8] |
Divest [3, 5, 8, 9] |
Divest [3, 5, 8, 9] |
Divest [5, 9, 10, 11] |
Divest [5, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2012.2 |
Approved w/Constraints [3, 5, 7, 8] |
Divest [3, 5, 8, 9] |
Divest [3, 5, 8, 9] |
Divest [5, 9, 10, 11] |
Divest [5, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2014.1.3 |
Approved w/Constraints [3, 5, 7, 8] |
Approved w/Constraints [3, 5, 8, 9] |
Approved w/Constraints [3, 5, 8, 9] |
Approved w/Constraints [5, 9, 10, 11] |
Approved w/Constraints [5, 10, 11, 12] |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
2015.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2016.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2016.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2017.1.x |
Unapproved |
Approved w/Constraints [1, 3, 5, 8, 9] |
Approved w/Constraints [1, 3, 5, 8, 9] |
Approved w/Constraints [1, 5, 9, 10, 11] |
Approved w/Constraints [1, 5, 10, 11, 12] |
Approved w/Constraints [1, 5, 10, 11, 13] |
Approved w/Constraints [1, 5, 10, 11, 13] |
Approved w/Constraints [1, 5, 10, 11, 13] |
Approved w/Constraints [1, 5, 10, 11, 14] |
Approved w/Constraints [1, 5, 10, 11, 14] |
Approved w/Constraints [1, 5, 10, 11, 14] |
Approved w/Constraints [1, 5, 10, 11, 14] |
2017.2.x (Client) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 13] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
Approved w/Constraints [5, 10, 11, 14] |
2018.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [2] | This technology has one or more known Common Vulnerability Exposure (CVE). CVE-2007-4427, CVE-2007-0437, CVE-2004-2683, CVE-2004-2684, CVE-2003-1333, CVE-2003-0497, and CVE-2003-0498. | | [3] | 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). | | [4] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [5] | 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. | | [6] | AERB approval is required before acquiring any DBMS licenses.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies (Microsoft SQL Server and Oracle DB). Customers should get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
All systems/instances including Client, VRO, Shadow systems, are required to be at the same version of Cache. The approved version is Cache 2014.1.3 Ad Hoc 14809.
AudioCare Systems servers interface with VA-VistA and run Cache 2012.1.
Existing development and code use is running Cache 2012.2 in support of VistA Evolution and Kiosk within the VA.
Cache 2014.1.3 is the version that is currently being released for VistA and supported in VA Medical Centers.
Cache 2015.1 is the latest version released 11 February 2015 and planning for this release is currently underway for evaluation of functionality at Pilot Sites.
This technology has one or more known Common Vulnerability Exposure (CVE). CVE-2007-4427, CVE-2007-0437, CVE-2004-2683, CVE-2004-2684, CVE-2003-1333, CVE-2003-0497, and CVE-2003-0498. | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Architecture and Engineering Review Board (AERB) approval is required before acquiring any Database Management System (DBMS) licenses.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies (Microsoft SQL Server and Oracle DB). Customers must get their licenses through these channels, not via independent, uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx.
Cache 2014.1.3 Ad Hoc 14809 is the current approved version for VA - VistA and supported for VA Medical Centers.
All systems/instances which include: Database, Client-Application, VRO, Shadow systems, are required to be at the same version of Cache. | | [8] | 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. | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Architecture and Engineering Review Board (AERB) approval is required before acquiring any Database Management System (DBMS) licenses.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies, Cach` is included in ELAs. Customers are required to obtain valid licenses through these channels and not via independent and/or uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline and host Servers are defined and maintained by the Health Systems (Health Systems Platform & Health Systems Engineering & Design) organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Cache 2014.1.3 Ad Hoc 14809 (14809:Jul15SV1rev2,16191,16474,16562,16591) is the approved version that is currently being released for VistA and supported in VA Medical Centers. All systems/instances which include: Database, Client-Application, VistA Read Only, Shadow systems, are required to be at the same version of Cache. | | [10] | 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). | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Architecture and Engineering Review Board (AERB) approval is required before acquiring any Database Management System (DBMS) licenses.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies, Cache is included in ELAs. Customers are required to obtain valid licenses through these channels and not via independent and/or uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline and host Servers are defined and maintained by the Health Systems (Health Systems Platform & Health Systems Engineering & Design) organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx.
Cache 2014.1.3 Ad Hoc 14809 (14809:Jul15SV1rev2,16191,16474,16562,16591, Feb17SV,17540) is the approved version that is currently being released for VistA and supported in VA Medical Centers. All systems/instances which include: Database, Client-Application, VistA Read Only, Shadow systems, are required to be at the same version of Cache. | | [13] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Architecture and Engineering Review Board (AERB) approval is required before acquiring any Database Management System (DBMS) licenses.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies, Cache is included in ELAs. Customers are required to obtain valid licenses through these channels and not via independent and/or uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline and host Servers are defined and maintained by the Health Systems (Health Systems Platform & Health Systems Engineering & Design) organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx.
Cache 2014.1.3 Ad Hoc 14809 (14809:Jul15SV1rev2,16191,16474,16562,16591, Feb17SV,17540) is the approved version that is currently being released for VistA and supported in VA Medical Centers. All systems/instances which include: Database, Client-Application, VistA-Read Only, Shadow systems, are required to be at the same version of Cache.
Cache 2017.2.1 is NOT to be installed on any VA VistA Production or related servers/Cache instances (i.e. VistA-Read Only, Shadows, etc.). Cache 2017.2.1 is ONLY approved for the Client-Application (Cache for Windows) instance. | | [14] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
VA has Enterprise License Agreements (ELAs) in place for preferred DBMS technologies, Cache is included in ELAs. Customers are required to obtain valid licenses through these channels and not via independent and/or uncoordinated small procurements. Detailed information can be found at the following location: http://vaww.eie.va.gov/TIPO/default.aspx.
Configuration and deployment standards for Cache Baseline and host Servers are defined and maintained by the Health Systems (Health Systems Platform & Health Systems Engineering & Design) organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx.
Cache 2014.1.3 Ad Hoc 14809 (14809:Jul15SV1rev2,16191,16474,16562,16591, Feb17SV,17540) is the approved version that is currently being released for VistA and supported in VA Medical Centers. All systems/instances which include: Database, Client-Application, VistA-Read Only, Shadow systems, are required to be at the same version of Cache.
Cache 2017.2.1 is NOT to be installed on any VA VistA Production or related servers/Cache instances (i.e. VistA-Read Only, Shadows, etc.). Cache 2017.2.1 is ONLY approved for the Client-Application (Cache for Windows) instance. |
|
Note: |
At the time of writing, version 2018.1.7 is the most current version, but has no VA baseline. The current Baselined version of Cache for VistA is 2017.1.3 Ad Hoc 19647. |