| 3.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 16, 17, 18, 19] |
| 3.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[7, 8, 10, 11, 12] |
Approved w/Constraints
[7, 8, 11, 12, 13] |
Approved w/Constraints
[7, 8, 11, 12, 13] |
Approved w/Constraints
[7, 8, 12, 13, 14] |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 15, 16, 17, 18] |
Approved w/Constraints
[12, 13, 16, 17, 18, 19] |
| | | | [1] | 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. | | | [2] | 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). | | | [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] | Users must ensure that Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. | | | [5] | 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 ISO can advise on the ESCCB review process. | | | [6] | Only the current VA TRM-approved version(s) and install package(s) for PAR Excellence provided on the user`s VA computer may be used with applications and websites that support the VA-approved baseline configuration of PAR Excellence.
Users must ensure that Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines.
Per the Initial Product Review, users must abide by the following constraints:
- 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 where applicable.
- Current VA implementation documentation states PAR Excellence uses a Microsoft SQL database which should be hardened and configured using VA approved baselines.
- VA should determine if a baseline is required for these devices, as they come from the vendor preconfigured. If VA specific configuration changes are required, to meet baseline, it must be determined if the device, as well as the
vendor, will support such changes without voiding warranty and support.
- System owners should identify and document the components using wireless technology, what type of technology and if FIPS 140-2 encryption is being utilized if applicable.
| | | [7] | 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). | | | [8] | 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 ISO can advise on the ESCCB review process. | | | [9] | 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). | | | [10] | 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). | | | [11] | Only the current VA TRM-approved version(s) and install package(s) for PAR Excellence provided on the user`s VA computer may be used with applications and websites that support the VA-approved baseline configuration of PAR Excellence.
Users must ensure that Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), Microsoft .NET Framework, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Per the Initial Product Review, users must abide by the following constraints:
- 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 where applicable.
- Current VA implementation documentation states PAR Excellence uses a Microsoft SQL database which should be hardened and configured using VA approved baselines.
- VA should determine if a baseline is required for these devices, as they come from the vendor preconfigured. If VA specific configuration changes are required, to meet baseline, it must be determined if the device, as well as the vendor, will support such changes without voiding warranty and support.
- System owners should identify and document the components using wireless technology, what type of technology and if FIPS 140-2 encryption is being utilized if applicable.
| | | [12] | 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. | | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [14] | Only the current VA TRM-approved version(s) and install package(s) for PAR Excellence provided on the user`s VA computer may be used with applications and websites that support the VA-approved baseline configuration of PAR Excellence.
Users must ensure that, Microsoft Internet Information Services (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End-of-Life status. See Category Tab for details. Other approved internet browsers are available. See Category Tab for details.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Per the Initial Product Review, users must abide by the following constraints:
- 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 where applicable.
- Current VA implementation documentation states PAR Excellence uses a Microsoft SQL database which should be hardened and configured using VA approved baselines.
- The product or technology must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. The TRM Decision Matrix displays the current and future VA IT position regarding different releases of a technology. The consumer of this information has the responsibility to consult the organizations responsible for the development, preproduction and/or production environments to ensure that the target version of the technology will be supported. Any major/minor version, that is not listed in the TRM Decision Matrix, is considered unapproved for use.
- It is a requirement that VA sensitive data be properly protected in accordance with VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standards (FIPS) 140-2.
- Deployments of the PAR Excellence system must follow the VA PAR Excellence Interim Implementation Standard.
- VA should determine if a baseline is required for these devices, as they come from the vendor preconfigured. If VA specific configuration changes are required, to meet baseline, it must be determined if the device, as well as the vendor, will support such changes without voiding warranty and support.
- System owners should identify and document the components using wireless technology, what type of technology and if FIPS 140-2 encryption is being utilized if applicable.
| | | [15] | Only the current VA TRM-approved version(s) and install package(s) for PAR Excellence provided on the user`s VA computer may be used with applications and websites that support the VA-approved baseline configuration of PAR Excellence.
Users must ensure that, Microsoft Internet Information Services (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End-of-Life status. See Category Tab for details. Other approved internet browsers are available. See Category Tab for details.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Per the Initial Product Review, users must abide by the following constraints:
-
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), Digital Transformation Center (DTC), 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 or 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 DTC.
-
Current VA implementation documentation states PAR Excellence uses a Microsoft SQL database which should be hardened and configured using VA approved baselines.
-
Deployments of the PAR Excellence system must follow the VA PAR Excellence Interim Implementation Standard.
| | | [16] | 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. | | | [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 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). | | | [18] | 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. | | | [19] | Only the current VA TRM-approved version(s) and install package(s) for PAR Excellence provided on the user`s VA computer may be used with applications and websites that support the VA-approved baseline configuration of PAR Excellence.
Users must ensure that, Firefox, Google Chrome, Microsoft Internet Information Services (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End-of-Life status. See Category Tab for details. Other approved internet browsers are available. See Category Tab for details.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Per the Initial Product Review, users must abide by the following constraints:
- 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), Digital Transformation Center (DTC), 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 or 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 DTC.
- Current VA implementation documentation states PAR Excellence uses a Microsoft SQL database which should be hardened and configured using VA approved baselines.
- Deployments of the PAR Excellence system must follow the VA PAR Excellence Interim Implementation Standard.
|
|
