| 5.x |
Approved w/Constraints
[1, 2, 3, 4, 6] |
Approved w/Constraints
[1, 2, 3, 4, 6] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Divest
[3, 4, 9, 10, 11, 12] |
Divest
[3, 4, 9, 10, 11, 12] |
Divest
[3, 4, 9, 10, 12, 13] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 4, 10, 12, 13, 14] |
Approved w/Constraints
[3, 4, 10, 12, 13, 14] |
Approved w/Constraints
[3, 4, 10, 12, 14, 15] |
Approved w/Constraints
[3, 4, 10, 12, 14, 15] |
Approved w/Constraints
[3, 4, 10, 12, 14, 15] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure Redis Enterprise aligns with the VA-approved configuration baseline for version 5.x referenced in the Reference tab of this entry.
Per the Initial Product Review, users must abide by the following constraints:
- Use a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications developed using Redis Enterprise Software (RS).
- Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
- The database server and its components must adhere to VA Baseline Configuration Standards. In addition, the following security measures will help ensure the data is secured and protected:
- Ensure connections between On-Line Data Base components (e.g., clients, application server, data store) are encrypted using Transport Layer Security (TLS), rather than Secure Sockets Layer (SSL);
- Employ security authorization controls, least privileges and separation of duties to prevent unauthorized access to VA sensitive data;
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database system.
- An approved VA Security Configuration Baseline must be created and ratified before Redis Enterprise Software is used in VA. It is worth noting that DISA STIGS, CIS Benchmarks, or other NIST validated guidelines do not exist at this time for Redis Enterprise Software.
| | | [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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [6] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure Redis Enterprise aligns with the VA-approved configuration baseline for version 5.x referenced in the Reference tab of this entry.
Per the Initial Product Review, users must abide by the following constraints:
- Use a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications developed using Redis Enterprise Software (RS).
- Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
- The database server and its components must adhere to VA Baseline Configuration Standards. In addition, the following security measures will help ensure the data is secured and protected:
- Ensure connections between On-Line Data Base components (e.g., clients, application server, data store) are encrypted using Transport Layer Security (TLS), rather than Secure Sockets Layer (SSL);
- Employ security authorization controls, least privileges and separation of duties to prevent unauthorized access to VA sensitive data;
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database system.
- An approved VA Security Configuration Baseline must be created and ratified before Redis Enterprise Software is used in VA. It is worth noting that DISA STIGS, CIS Benchmarks, or other NIST validated guidelines do not exist at this time for Redis Enterprise Software.
| | | [8] | 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). | | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure Redis Enterprise aligns with the VA-approved configuration baseline for version 5.x referenced in the Reference tab of this entry.
Per the Initial Product Review, users must abide by the following constraints:
- Use a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications developed using Redis Enterprise Software (RS).
- Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
- The database server and its components must adhere to VA Baseline Configuration Standards. In addition, the following security measures will help ensure the data is secured and protected:
- Ensure connections between On-Line Data Base components (e.g., clients, application server, data store) are encrypted using Transport Layer Security (TLS), rather than Secure Sockets Layer (SSL);
- Employ security authorization controls, least privileges and separation of duties to prevent unauthorized access to VA sensitive data;
- Deploy a VA-approved web application firewall (WAF) and database firewall to add layers of security to the database system.
- An approved VA Security Configuration Baseline must be created and ratified before Redis Enterprise Software is used in VA. It is worth noting that DISA STIGS, CIS Benchmarks, or other NIST validated guidelines do not exist at this time for Redis Enterprise Software.
- Note: Log all computer-readable data extracts from databases holding sensitive information and verify each extract as stated in VA Handbook 6500.
| | | [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] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [12] | 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). | | | [13] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [14] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure Redis Enterprise aligns with the VA-approved configuration baseline for version 6.x referenced in the Reference tab of this entry.
Per the Initial Product Review, users must abide by the following constraints:
- Redis Enterprise Software (RS) will require a 3rd party FIPS 140-2 certified
solution for any data containing PHI/PII or VA sensitive information).
- Due to potential information security risks, SaaS/PaaS solutions must complete
the Veterans-Focused Integration Process Request (VIPR) process where a
collaborative effort between Demand Management (DM), Enterprise Program
Management Office Information Assurance (EPMO IA), Project Special Forces
(PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer
(CTO), and stakeholders determines the SaaS/PaaS category during the
Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are
routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical
oversight, acquisition, production, and sustainment provided by PSF.
- The database server and its components must adhere to VA Baseline
Configuration Standards.
| | | [15] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
