| | | | [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. | | | [15] | Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 2017.1.3 Ad Hoc 19647 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.
Per the Initial Product Review, users must abide by the following constraints:
- Database management systems used in VA will be encrypted using FIPS 140-2 (or its successor) validated encryption as stated in section SC-28: Protection of Information at Rest of the VA 6500 Handbook. 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 as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS).`
- Security controls/requirements for external information systems that process, store, or transmit VA sensitive information should be documented in a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement) in accordance to VA Directive 6513, Secure External Connections, and VA Handbook 6500.6. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandate.
- System owners and database administrators must disable the predefined user accounts that are not needed for operation. Predefined user accounts that are required must utilize credentials that meet the VA requirements as stated in control IA-5: Authenticator Management, AC-3: Access Enforcement and AC-6: Least Privilege. Use VA-approved directory services such as Active Directory (AD) for authentication and authorization.
- The database administrator must refer to the VA Baseline Configuration Standard for Caché for guidance when implementing Caché database within the VA environment. The database server and its associated components must adhere to VA hardening standards. In addition, the following security measures will help ensure the data is secured and protected.
- Leverage two-factor authentication provided by the product or VA-approved 2FA solution;
- Ensure connections between the web browser and web server are encrypted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database
- Perform end-to-end security testing of Caché and all its components to ensure security holes are addressed prior to implementation
- Continuous vulnerability scanning, monitoring and auditing of the database system and associated components.
| | | [16] | 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. | | | [17] | 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). | | | [18] | Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 2017.1.3 Ad Hoc 19647 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.
Per the Initial Product Review, users must abide by the following constraints:
- Database management systems used in VA will be encrypted using FIPS 140-2 (or its successor) validated encryption as stated in section SC-28: Protection of Information at Rest of the VA 6500 Handbook. 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 as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS).`
- Security controls/requirements for external information systems that process, store, or transmit VA sensitive information should be documented in a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement) in accordance to VA Directive 6513, Secure External Connections, and VA Handbook 6500.6. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandate.
- System owners and database administrators must disable the predefined user accounts that are not needed for operation. Predefined user accounts that are required must utilize credentials that meet the VA requirements as stated in control IA-5: Authenticator Management, AC-3: Access Enforcement and AC-6: Least Privilege. Use VA-approved directory services such as Active Directory (AD) for authentication and authorization.
- The database administrator must refer to the VA Baseline Configuration Standard for Caché for guidance when implementing Caché database within the VA environment. The database server and its associated components must adhere to VA hardening standards. In addition, the following security measures will help ensure the data is secured and protected.
- Leverage two-factor authentication provided by the product or VA-approved 2FA solution;
- Ensure connections between the web browser and web server are encrypted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database
- Perform end-to-end security testing of Caché and all its components to ensure security holes are addressed prior to implementation
- Continuous vulnerability scanning, monitoring and auditing of the database system and associated components.
| | | [19] | Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 2017.1.3 Ad Hoc 19647 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.
Per the Initial Product Review, users must abide by the following constraints:
- Database management systems used in VA will be encrypted using FIPS 140-2 (or its successor) validated encryption as stated in section SC-28: Protection of Information at Rest of the VA 6500 Handbook. 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 as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS).`
- Security controls/requirements for external information systems that process, store, or transmit VA sensitive information should be documented in a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement) in accordance to VA Directive 6513, Secure External Connections, and VA Handbook 6500.6. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandate.
- System owners and database administrators must disable the predefined user accounts that are not needed for operation. Predefined user accounts that are required must utilize credentials that meet the VA requirements as stated in control IA-5: Authenticator Management, AC-3: Access Enforcement and AC-6: Least Privilege. Use VA-approved directory services such as Active Directory (AD) for authentication and authorization.
- The database administrator must refer to the VA Baseline Configuration Standard for Caché for guidance when implementing Caché database within the VA environment. The database server and its associated components must adhere to VA hardening standards. In addition, the following security measures will help ensure the data is secured and protected.
- Leverage two-factor authentication provided by the product or VA-approved 2FA solution;
- Ensure connections between the web browser and web server are encrypted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database
- Perform end-to-end security testing of Caché and all its components to ensure security holes are addressed prior to implementation
- Continuous vulnerability scanning, monitoring and auditing of the database system and associated components.
| | | [20] | Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 2017.1.3 Ad Hoc 19647 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.
Per the Initial Product Review, users must abide by the following constraints:
- Database management systems used in VA will be encrypted using FIPS 140-2 (or its successor) certified encryption as stated in section SC-28: Protection of Information at Rest of the VA 6500 Handbook. 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 as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled `FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS).`
- Security controls/requirements for external information systems that process, store, or transmit VA sensitive information should be documented in a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement) in accordance to VA Directive 6513, Secure External Connections, and VA Handbook 6500.6. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandate.
- System owners and database administrators must disable the predefined user accounts that are not needed for operation. Predefined user accounts that are required must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5). Ensure that all VA password requirements are met regarding length and complexity. VA Knowledge Service Control IA-5: Authenticator Management requires a case sensitive 14-character password comprised of upper-case letters, lower case letters, numbers, and special characters, including at least one of each category. VA defines and enforces at least 50% of characters in the password must be changed when new passwords are created.
- The database administrator must refer to the VA Baseline Configuration Standard for Caché for guidance when implementing Caché database within the VA environment. The database server and its associated components must adhere to VA hardening standards. In addition, the following security measures will help ensure the data is secured and protected.
- Leverage two-factor authentication provided by the product or VA approved 2FA solution;
- Ensure connections between the web browser and web server are encrypted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database
- Perform end-to-end security testing of Caché and all its components to ensure security holes are addressed prior to implementation
- Continuous vulnerability scanning, monitoring, and auditing of the database system and associated components
- Systems owners and Administrators should ensure the latest version of this product is installed and must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
| | | [21] | 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. | | | [22] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | | [23] | 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 System Security Officer (ISSO) 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). | | | [24] | 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.
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 System Security Officer (ISSO) 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).
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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.
Users must ensure that Apache Hypertext Transfer Protocol (HTTP) Server and Microsoft Internet Information Services (IIS) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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 2017.1.3 Ad Hoc 19647 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.
Per the Initial Product Review, users must abide by the following constraints:
Database management systems used in VA will be encrypted using FIPS 140-2 (or its successor) certified encryption as stated in section SC-28: Protection of Information at Rest of the VA 6500 Handbook. 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 as stated in the May 5, 2015 memo from the VA Deputy Assistant Secretary for Information Security titled ‘FIPS 140-2 Validated Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS).’
Security controls/requirements for external information systems that process, store, or transmit VA sensitive information should be documented in a VA approved MOU/ISA, VA contract or other VA approved agreement (e.g., Data Use Agreement) in accordance to VA Directive 6513, Secure External Connections, and VA Handbook 6500.6. In addition, all external network connections must traverse through the VA Trusted Internet Connection (TIC) gateway to comply with critical OMB mandate.
System owners and database administrators must disable the predefined user accounts that are not needed for operation. Predefined user accounts that are required must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5). Ensure that all VA password requirements are met regarding length and complexity. VA Knowledge Service Control IA-5: Authenticator Management requires a case sensitive 14-character password comprised of upper-case letters, lower case letters, numbers, and special characters, including at least one of each category. VA defines and enforces at least 50% of characters in the password must be changed when new passwords are created.
The database administrator must refer to the VA Baseline Configuration Standard for Cache for guidance when implementing Cache database within the VA environment. The database server and its associated components must adhere to VA hardening standards. In addition, the following security measures will help ensure the data is secured and protected.
Leverage two-factor authentication provided by the product or VA approved 2FA solution;
Ensure connections between the web browser and web server are encrypted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database
Perform end-to-end security testing of Cache and all its components to ensure security holes are addressed prior to implementation
Continuous vulnerability scanning, monitoring, and auditing of the database system and associated components
Systems owners and Administrators should ensure the latest version of this product is installed and must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. | | | [25] | 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. | | | [26] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 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 or its successor 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 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device 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 System Security Officer (ISSO) 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). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. |
|
