21.x |
Approved w/Constraints [1, 3, 6, 7, 8] |
Approved w/Constraints [1, 3, 6, 7, 8] |
Approved w/Constraints [1, 3, 6, 7, 9] |
Approved w/Constraints [1, 3, 6, 7, 9] |
Approved w/Constraints [1, 3, 6, 7, 9] |
Approved w/Constraints [1, 3, 6, 7, 10] |
Approved w/Constraints [1, 3, 6, 7, 10] |
Approved w/Constraints [1, 3, 6, 7, 10] |
Approved w/Constraints [1, 3, 6, 10, 11] |
Approved w/Constraints [6, 10, 11, 12, 13, 14] |
Approved w/Constraints [6, 10, 11, 12, 13, 14] |
Approved w/Constraints [6, 10, 12, 13, 14, 15] |
| | [1] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- AutoVue 3D Professional Advanced should only be used on VA standard
desktops to protect data at rest or in transit. The data transmitted must be
appropriately protected by the underlying infrastructure and AutoVue 3D
Professional Advanced must be configured to ensure encryption is utilized.
- System administrators must ensure that the latest stable version of AutoVue
3D Professional Advanced is used. Additionally, AutoVue 3D Professional
Advanced must be added to the list of applications for continuous monitoring
for published vulnerabilities, updates, and patches.
- Due to potential information security risks, Software as a Service/Platform as a
Service (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.
- Enforce role-based access controls through Active Directory for the creation of
different accounts based on organizational roles.
- The AutoVue 3D Professional Advanced free version should not be used. VA
Handbook 6500 Appendix D, Department of Veteran Affairs National Rules of
Behavior, Section f (3) (page 68. D-10): I will not download software from the
Internet, or other public available sources, offered as free trials, shareware, or
other unlicensed software to a VA-owned system.
| | [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] | 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). | | [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 (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [6] | 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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [8] | 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). | | [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] | 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). | | [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 VA Handbook 6500. | | [12] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
-
AutoVue 3D Professional Advanced will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable.
- System administrators must ensure that the latest stable version of AutoVue 3D Professional Advanced is used. Additionally, AutoVue 3D Professional Advanced must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
-
Due to potential information security risks, Software as a Service/Platform as a Service (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.
-
Enforce role-based access controls through Active Directory for the creation of different accounts based on organizational roles.
-
The AutoVue 3D Professional Advanced free version should not be used. VA Handbook 6500 Appendix D, Department of Veteran Affairs National Rules of Behavior, Section f (3) (page 68. D-10): I will not download software from the Internet, or other public available sources, offered as free trials, shareware, or other unlicensed software to a VA-owned system.
| | [13] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [14] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [15] | 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. |
|