| 12.5 |
Approved w/Constraints
[3, 9, 13, 14] |
Approved w/Constraints
[3, 9, 13, 14] |
Approved w/Constraints
[3, 9, 13, 14] |
Approved w/Constraints
[13, 15, 16, 17] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
Approved w/Constraints
[15, 16, 17, 18] |
| | | | [1] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [2] | Acronis Backup potentially uses userid and password for authentication. Acronis must be configured for Integrated Windows Authentication using VA`s active directory.
Each of the agents must be validated utilizing complete regression tests on each of the systems the agent would reside upon. | | | [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] | 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. | | | [5] | 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). | | | [6] | Per the Initial Product Review, users must abide by the designated constraints:
Acronis Backup potentially uses userID and password for authentication. Acronis must be configured for Integrated Windows Authentication using VA`s active directory.
Each of the agents must be validated utilizing complete regression tests on each of the systems the agent would reside upon.
Unassigned port numbers must not be used.
Due to the lack of accreditation of the Acronis Data Centers only the on-premise solution must be considered for use by VA.
The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | | [7] | Per the Initial Product Review, users must abide by the designated constraints:
Acronis Backup potentially uses userID and password for authentication. Acronis must be configured for Integrated Windows Authentication using VA`s active directory.
Each of the agents must validated and complete regression tests on each of the systems the agent would reside.
The cloud version of Acronis Backup is not part of the VAEC or in a FedRAMP certified data center. Due to the lack of accreditation of the Acronis Data Centers only the on-premise solution should be considered for use by VA.
The communication between the Client, the Management Server, the Agents and the Storage Node may encounter unexpected results using ports allocated for other applications or that are currently unassigned. | | | [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] | Per the Initial Product Review, users must abide by the designated constraints:
Acronis Backup potentially uses userID and password for authentication. Acronis must be configured for Integrated Windows Authentication using VA`s active directory.
Each of the agents must validated and complete regression tests on each of the systems the agent would reside.
The cloud version of Acronis Cyber Backup is not part of the VAEC or in a FedRAMP certified data center. Due to the lack of accreditation of the Acronis Data Centers, only the on-premise solution should be considered for use by 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.
The communication between the Client, the Management Server, the Agents and the Storage Node may encounter unexpected results using ports allocated for other applications or that are currently unassigned.
System owners should use the latest build 16386 of version 12.5 of this
software and monitor for any new vulnerabilities that may arise. | | | [10] | 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. | | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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] | 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. | | | [15] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Microsoft SharePoint Server, as it is unapproved for use on the TRM.
Users must not utilize Hyper-V Server (Stand-alone Edition), as it is unapproved for use on the TRM.
Users must not utilize Red Hat Enterprise Virtualization (Servers), as it is unapproved for use on the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Acronis Cyber Backup shall be configured to meet minimum password-based authentication standards per VA Knowledge Service Control IA-5(1).
- Each of the agents must validated and complete regression tests on each of the systems the agent would reside.
- Due to the lack of accreditation of the Acronis Data Centers, only the on premise solution should be considered for use by 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), 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.
- System owners should use the latest build 16545 of version 12.5 of this software and monitor for any new vulnerabilities that may arise.
| | | [16] | 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. | | | [17] | 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. | | | [18] | 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). |
|
