|
<Past |
Future> |
| 4.x |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Divest
[3, 5, 6, 7, 8] |
Divest
[3, 5, 6, 7, 8] |
Divest
[3, 5, 6, 7, 8] |
Divest
[3, 5, 8, 9, 10, 11] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
Unapproved |
Unapproved |
| 7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 5, 6, 7, 8] |
Approved w/Constraints
[3, 5, 6, 7, 8] |
Approved w/Constraints
[3, 5, 6, 7, 8] |
Divest
[3, 5, 8, 9, 10, 11] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
| SR8 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 5, 8, 9, 10, 11] |
Approved w/Constraints
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
Divest
[3, 5, 9, 10, 11, 12] |
| SR9 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 5, 9, 10, 11, 12] |
Approved w/Constraints
[3, 5, 9, 10, 11, 12] |
Approved w/Constraints
[3, 5, 9, 10, 11, 12] |
| | | | [1] | Users must ensure that Microsoft .NET Framework and Microsoft Structured Query Language (SQL) Server 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.
Responder Enterprise shall only be implemented as a local deployment until an executive sponsor is identified to employ the solution as a VA enterprise solution.
An Enterprise Risk Analysis (ERA) shall be completed prior to Rauland Enterprise being connected to the VA network. The System Security Support Risk Analysis intake portal can be found here. Each implementation must be validated with an existing approved ERA. Any deviation will require a modification request, to be made through ERA process, to ensure the deployment meets the network security requirements. The user guide for how to submit an ERA request can be found at ERA Joint Users Guide under Risk Analysis Guidance heading. | | | [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] | 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] | 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). | | | [5] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | | [6] | Users must ensure that Microsoft Structured Query Language (SQL) Server 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.
Responder Enterprise shall only be implemented as a local deployment until an executive sponsor is identified to employ the solution as a VA enterprise solution.
An Enterprise Risk Analysis (ERA) shall be completed prior to Rauland Enterprise being connected to the VA network. The System Security Support Risk Analysis intake portal can be found here. Each implementation must be validated with an existing approved ERA. Any deviation will require a modification request, to be made through ERA process, to ensure the deployment meets the network security requirements. The user guide for how to submit an ERA request can be found at ERA Joint Users Guide under Risk Analysis Guidance heading. | | | [7] | 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. | | | [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 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). | | | [9] | Users must ensure that Microsoft Structured Query Language (SQL) 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.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Responder Enterprise shall only be implemented as a local deployment until an executive sponsor is identified to employ the solution as a VA enterprise solution.
An Enterprise Risk Analysis (ERA) shall be completed prior to Rauland Enterprise being connected to the VA network. The System Security Support Risk Analysis intake portal can be found here. Each implementation must be validated with an existing approved ERA. Any deviation will require a modification request, to be made through ERA process, to ensure the deployment meets the network security requirements. The user guide for how to submit an ERA request can be found at ERA Joint Users Guide under Risk Analysis Guidance heading. | | | [10] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [12] | 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. |
|
| Note: |
At the time of writing, version SR9 is the most current version. |
