| | | | [1] | Per the Initial Product Review, users must abide by the following constraints:
- Administrators must decide on how to handle failure cases in the context of the TLS session. It is highly recommended that the VA implement a “hard fail” strategy in which users fail a connection when they can’t check the revocation status of a certificate or all the intermediate certificates used to verify the certificate.
- The VA should closely monitor the vendor’s website to keep pace with the frequent critical updates, patches, and version changes.
- ADSS OCSP Server should be configured to run in FIPS mode or leverage third-party encryption if sensitive VA information is to be stored and/or transmitted. Care should be taken to ensure that all underlying components being used are FIPS 140-2 certified.
- The VA Technical Reference Model (TRM) approved platforms and databases must be used unless a waiver is signed by the Demand Management Office and based upon a recommendation from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology.
- 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.
- Only authorized, properly identified and authenticated users should be allowed to use Ascertia OCSP Crusher. Also, user’s activities should be well monitored and logged in accordance with the VA Enterprise Configuration Policy.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Oracle Database, Microsoft .NET Framework, PostgreSQL, Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle. | | | [2] | 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). | | | [3] | 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. | | | [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] | Per the Initial Product Review, users must abide by the following constraints:
- Administrators must decide on how to handle failure cases in the context of the TLS session. It is highly recommended that the VA implement a “hard fail” strategy in which users fail a connection when they can’t check the revocation status of a certificate or all the intermediate certificates used to verify the certificate.
- The VA should closely monitor the vendor’s website to keep pace with the frequent critical updates, patches, and version changes.
- ADSS OCSP Server should be configured to run in FIPS mode or leverage third-party encryption if sensitive VA information is to be stored and/or transmitted. Care should be taken to ensure that all underlying components being used are FIPS 140-2 certified.
- The VA Technical Reference Model (TRM) approved platforms and databases must be used unless a waiver is signed by the Demand Management Office and based upon a recommendation from the Strategic Technology Alignment Team (STAT) has been granted to the project team or organization that wishes to use the technology.
- 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.
- Only authorized, properly identified and authenticated users should be allowed to use Ascertia OCSP Crusher. Also, user’s activities should be well monitored and logged in accordance with the VA Enterprise Configuration Policy.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Oracle Database, Microsoft .NET Framework, PostgreSQL, Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM approved version of a Java Runtime Environment. | | | [6] | 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. | | | [7] | 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). | | | [8] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [10] | Per the Initial Product Review, users must abide by the following constraints:
- Administrators must decide on how to handle failure cases in the context of the TLS session. It is highly recommended that the VA implement a “hard fail” strategy in which users fail a connection when they can’t check the revocation status of a certificate or all the intermediate certificates used to verify the certificate.
- The VA should closely monitor the vendor’s website to keep pace with the frequent critical updates, patches, and version changes.
- ADSS OCSP Server should be configured to run in FIPS mode or leverage third-party encryption if sensitive VA information is to be stored and/or transmitted. Care should be taken to ensure that all underlying components being used are FIPS 140-2 certified.
- The VA Technical Reference Model (TRM) approved platforms and databases must be used. VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO, ISO and SS for pre-existing systems to enter a high or higher POA&M for the “TRM Unapproved technology”
- 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.
- Only authorized, properly identified and authenticated users should be allowed to use Ascertia OCSP Crusher. Also, user’s activities should be well monitored and logged in accordance with the VA Enterprise Configuration Policy.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Oracle Database, Microsoft .NET Framework, PostgreSQL, Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM approved version of a Java Runtime Environment.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. | | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [12] | 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. | | | [13] | 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. | | | [14] | 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
