| 4.x.x |
Approved w/Constraints
[2, 6, 9, 10, 11, 12] |
Approved w/Constraints
[2, 6, 9, 10, 11, 12] |
Approved w/Constraints
[2, 6, 9, 10, 11, 12] |
Approved w/Constraints
[2, 6, 9, 10, 11, 12] |
Approved w/Constraints
[2, 9, 10, 13, 14, 15] |
Approved w/Constraints
[2, 9, 10, 13, 14, 15] |
Approved w/Constraints
[2, 9, 10, 13, 14, 16] |
Approved w/Constraints
[2, 9, 10, 13, 14, 16] |
Approved w/Constraints
[2, 9, 10, 13, 14, 16] |
Approved w/Constraints
[2, 9, 10, 13, 14, 17] |
Approved w/Constraints
[2, 9, 13, 14, 17, 18] |
Approved w/Constraints
[2, 9, 13, 14, 17, 18] |
| | | | [1] | Per the Initial Product Review:
It is advised that if this device is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. The Spring Security module should be employed when developing applications with the Spring Batch development tool.
2. Care should be taken to ensure that applications developed with the Spring Batch development tool have the proper security built in.
3. All applicable controls stipulated in VA Handbook 6500 must be applied to applications developed for use within the VA. | | | [2] | 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. | | | [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] | Spring Framework relies on Maven for project building and integration, and the VA-approved technology for building and continuous integration is Rational Build Forge (RBF). Projects using the technology must customize their build process to address the Maven dependency.
Per the Initial Product Review: It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
The Spring Security module must be employed when developing applications with the Spring Batch development tool. | | | [5] | Spring Framework relies on Maven for project building and integration, and the VA-approved technology for building and continuous integration is Rational Build Forge (RBF). Projects using the technology must customize their build process to address the Maven dependency.
Per the Initial Product Review: It is advised that if this product is used with the Department of Veterans Affairs (VA) that the following constraints be applied:
The Spring Security module must be employed when developing applications with the Spring Batch development application. | | | [6] | 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). | | | [7] | 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). | | | [8] | Spring Framework relies on Maven for project building and integration, and the VA-approved technology for building and continuous integration is Rational Build Forge (RBF). Projects using the technology must customize their build process to address the Maven dependency.
Per the Initial Product Review (IPR): It is advised that if this product is used with the Department of Veterans Affairs (VA) that the following constraints be applied:
The Spring Security module must be employed when developing applications with the Spring Batch development application. | | | [9] | 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. | | | [10] | This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Spring Framework relies on Maven for project building and integration, and the VA-approved technology for building and continuous integration is Rational Build Forge (RBF). Projects using the technology must customize their build process to address the Maven dependency.
Per the Initial Product Review, users must abide by the following constraints:
- The Spring Security module should be employed when developing applications with the Spring Batch development tool.
- All applicable controls stipulated in VA Handbook 6500 must be applied to applications developed using the Spring Batch development tool for use within the VA.
- Spring Batch is in a divest status on the One-VA TRM, as system scans show that this technology is no longer in use within VA`s network. Other solutions should be considered.
| | | [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] | 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). | | | [13] | 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). | | | [14] | 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. | | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [16] | 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). | | | [17] | 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). | | | [18] | This technology must use the latest version of Java Development Kit (JDK) - Oracle.
This technology is under review to use these dependencies due to Docker Engine Enterprise are only approved for Development and Test systems usage in the TRM.
Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Spring Framework relies on Maven for project building and integration, and the VA-approved technology for building and continuous integration is Rational Build Forge (RBF). Projects using the technology must customize their build process to address the Maven dependency.
Per the Initial Product Review, users must abide by the following constraints:
- The Spring Security module should be employed when developing applications with the Spring Batch development tool.
- All applicable controls stipulated in VA Handbook 6500 must be applied to applications developed using the Spring Batch development tool for use within the VA.
- 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.
|
|
