Acronis Cyber Backup

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Acronis Cyber Backup is an on-premise technology that provides backup and recovery of files, applications, and entire physical or virtual servers with bare-metal recovery support. The product can create image-based backups/snapshots of systems, including operating system, applications, configuration and data; and recover the image to the same hardware or dissimilar hardware. Note: This product has three editions: Acronis Cyber Protect Standard, Acronis Cyber Protect Advanced, and Acronis Cyber Protect Backup Advanced. This evaluation covers all three editions. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.12
Decision Date:	12/06/2023 at 02:43:55 UTC
Aliases:	Acronis Backup & Recovery
Introduced By:	TRM Request
Vendor Name:	Acronis

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
10.0	10/19/2009
11.0	06/21/2011
11.5	09/05/2012
12.0	02/07/2017
12.5	12/27/2017

Current Decision Matrix (11/30/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, 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 VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

10.0

Unapproved

11.0

Unapproved

11.5

Unapproved

12.0

Unapproved

12.5

Approved w/Constraints
[4, 5, 6]

Approved w/Constraints
[3, 4, 7, 8]

Approved w/Constraints
[3, 9, 10, 11]

Approved w/Constraints
[3, 9, 10, 12]

Decision Constraints


[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).

Note:

At the time of writing this, version 12.5 Build 16904 is the latest. Released 04/04/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Acronis Pricing	Publicly Available	This site provides pricing information for this technology.
Vendor Provided*	Acronis Cyber Protect System Requirements	Publicly Available	This site provides the system requirements for this technology.
Vendor Provided*	Acronis Backup 12.5 Release Notes	Publicly Available	This site provides a list of the new features and enhancements for this technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Acronis Backup & Recovery Agent	Acronis Backup & Recovery Agent periodically checks whether its license key is present on the license server.
Acronis Backup & Recovery Agent Core	Acronis Backup & Recovery Agent Core are applications that perform data backup, recovery and other operations on the machinesmanaged with Acronis Backup & Recovery 11.5.
Acronis Backup & Recovery Bootable Media Builder	Acronis Backup & Recovery Bootable Media Builder allows the user tp browse backups with Internet Explorer as if they were ordinary folders and drug-and-drop or copy-paste files and folders from them.
Acronis Backup & Recovery Command-Line Tool	Acronis Backup & Recovery Command-Line Tool is a command-line interface with the acrocmd utility.
Acronis Backup & Recovery Management Console	Acronis Backup & Recovery Management Console is an administrative tool for local access toAcronis Backup & Recovery 11.5 agent.
Acronis Backup & Recovery Tray Monitor	Tray Monitor notifies the user of the status of the progress of the Acronis backup software.
Acronis License Server (ALS)	Acronis License Server (ALS) is a component that manages licenses of Acronis products. This product allows users to delete, delegate, and add licenses through a Management Console or the command line.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Disaster Recovery
Security Data Security	Data Loss Prevention

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Oracle Linux - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Citrix Hypervisor - (required for some configurations)
Hyper-V Server (Stand-alone Edition) - (required for some configurations)
Microsoft SharePoint Server - (required for some configurations)
Microsoft Structured Query Language (SQL) Server
Red Hat Enterprise Virtualization (Servers) - (required for some configurations)
VMware vSphere

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include data loss prevention.
This is a well-documented technology.
This technology is Federal Information Processing (FIPS) 140-2 compliant.

Adoption Risks

This technology can potentially use Microsoft SharePoint Server, an unapproved technology.
This technology can potentially use Hyper-V Server (Stand-alone Edition), an unapproved technology.
This technology can potentially use Red Hat Enterprise Virtualization (Servers), an unapproved technology.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There are published vulnerabilities CVE-2022-3405 and CVE-2022-30995 that affect version 12.5 build before 16545 of this software.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Acronis Cyber Backup management console does not use multifactor authentication.
Multiple agents are required to backup different systems including: Agent for Windows, Agent for Linux, Agent for Mac, Agent for SQL, Agent for Exchange, Agent for Office 365, Agent for Active Directory, Agent for Oracle, Agent for VMware (Windows), Agent for VMware (Virtual Appliance), Agent for Hyper-V.
The cloud version of Acronis Cyber Backup does not reside in the Department of Veterans Affairs (VA) Enterprise Cloud (VAEC) or FedRAMP Certified Data Centers.

Architectural Benefits

The technology is portable as it runs on multiple VA-approved operating systems.
This technology supports AES Encryption.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (11/30/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (11/30/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES