<Past |
Future> |
2.0 |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.1.x |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.5 |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.6 |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.7 |
Unapproved |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.8 |
Unapproved |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.9 |
Unapproved |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [6, 8, 9, 10, 11] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Unapproved |
Unapproved |
3.11 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Approved w/Constraints [6, 8, 9, 10, 11] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Approved w/Constraints [8, 9, 10, 13, 14] |
4.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Unapproved |
4.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Divest [8, 9, 10, 13, 14] |
4.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 8, 9, 10, 12, 13] |
Divest [1, 8, 9, 10, 12, 13] |
Approved w/Constraints [1, 8, 9, 10, 13, 14] |
4.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 8, 9, 10, 13, 14] |
4.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.13.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.15.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] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). | | [3] | 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. | | [4] | 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. | | [5] | 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). | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [7] | 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). | | [8] | 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. | | [9] | 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. | | [10] | 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. | | [11] | 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). | | [12] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) 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.
Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, this technology is only approved for Development and Test systems usage. Production system use of this technology is considered TRM unapproved must have an approved TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s). See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx | | [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 (SPF) 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.
Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) 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.
Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, only Version 3.11 is approved for production use at this time and the referenced VA Security Baseline for version 3.11 must be followed.
Version 4.4 and 4.5 and newer versions of this technology are only approved for Development and Test systems usage at this time. Production system use of Version 4.x of this technology is considered TRM unapproved must have an approved TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s) for Version 4. See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx |
|
Note: |
At the time of writing, version 4.15 is the most current version released. A baseline configuration of this technology was developed by the BCM team. At the time of writing, the baseline version is 4.x. |