Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.1

Cisco AnyConnect Secure Mobility Client

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:	Cisco AnyConnect Secure Mobility Client provides endpoint security, policy enforcement, and encrypted network connectivity for a variety of platforms to allow corporate network access. 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 authorized by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.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 v24.8
Decision Date:	08/15/2024 at 17:13:03 UTC
Aliases:	Cisco AnyConnect VPN Client
Introduced By:	SCCM
Vendor Name:	Cisco Systems, Inc

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.X -VPN Client
3.0.X
3.1.08009
4.3.02039
4.4.01054
4.5.03040
4.6.00362	03/29/2018
4.6.04054
4.8.01090	10/28/2019
4.8.02045	02/17/2020
4.8.03036	03/16/2020
4.9.01095	09/06/2020
4.9.06037	02/05/2021
4.10.01075
4.10.0314	09/22/2021
4.10.x	04/10/2022
5.1.x.x	02/06/2024

Current Decision Matrix (08/14/2024)

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 VAIT 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.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2022

CY2023

CY2024

Future>

Release

2.X -VPN Client

Unapproved

3.0.X

Unapproved

3.1.08009

Unapproved

4.3.02039

Unapproved

4.4.01054

Unapproved

4.5.03040

Unapproved

4.6.00362

Unapproved

4.6.04054

Unapproved

4.8.01090

Unapproved

4.8.02045

Unapproved

4.8.03036

Unapproved

4.9.01095

Approved w/Constraints
[4, 12, 13, 14, 15, 16]

DIVEST
[4, 12, 13, 14, 16, 17, 18]

Unapproved

4.9.06037

Unapproved

4.10.01075

Unapproved

4.10.0314

Unapproved

4.10.x

Unapproved

Approved w/Constraints
[4, 12, 13, 14, 16, 17, 18]

Approved w/Constraints
[14, 17, 18, 19, 20, 21, 22]

Approved w/Constraints
[14, 17, 18, 20, 21, 22, 23]

Approved w/Constraints
[14, 17, 20, 21, 22, 23, 24]

DIVEST
[14, 20, 21, 23, 24, 25, 26]

5.1.x.x

Unapproved

Approved w/Constraints
[14, 20, 21, 23, 24, 25, 26]

Decision Constraints


[1]	1) Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. 2) This technology is authorized for use only to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). 3) Should there be a need to use this technology for other purposes such as to allow access to another organizations network resources, those specific uses and instances of this technology must be authorized by the Enterprise Security Change Control Board (ESCCB) along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA) which detail the security requirements for those users and systems that share information and information resources. As a part of that documentation, specific authorized instances of this technology, software version and any required patches must be address as part of the MOU/ISA. A link to the ESCCB approval process is provided in the reference section of this entry.

[2]	1) Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. 2) This technology is authorized for use only to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). 3) Should there be a need to use this technology for other purposes such as to allow access to another organizations network resources, those specific uses and instances of this technology must be authorized by the Enterprise Security Change Control Board (ESCCB), along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for those users and systems that share information and information resources. As a part of that documentation, specific authorized instances of this technology, software version and any required patches must be address as part of the MOU/ISA.

[3]	This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology should follow external data connection processes outlined in the constraint above.

[4]	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 ISO can provide assistance in reviewing the NIST vulnerabilities.

[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]	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]	This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above.

[8]	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.

[9]	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.

[10]	This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above. The baseline authorized version of this technology is version 4.6.04054. Only baselined version should be used at VA.

[11]	This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Network Security Operations Center (NSOC), Enterprise Systems Engineering (ESE) and the local Information Security Officer (ISO). Other uses of this technology must follow external data connection processes outlined in the constraint above. The baseline authorized version of this technology is version 4.6.04054. Only the baseline version of this technology should be used at VA.

[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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[13]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

[14]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[15]	This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Cyber Security Operations Center (CSOC), Enterprise Systems Engineering (ESE) and the local Information System Security Officer (ISSO). Other uses of this technology must follow external data connection processes outlined in the constraint above. The baseline authorized version of this technology is version 4.9.01095. Only the baseline versions of this technology should be used within VA environments.

[16]	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.

[17]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Cyber Security Operations Center (CSOC), Enterprise Systems Engineering (ESE) and the local Information System Security Officer (ISSO). Other uses of this technology must follow external data connection processes outlined in the constraint above. Only VA Baselined versions of this technology are authorized for use. For more information, please visit the baseline documentation for this technology via the “Reference” tab (within the VA network only).

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

[19]	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.

[20]	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.

[21]	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.

[22]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[23]	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.

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

[25]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology is authorized primarily to connect authorized client devices to the VA Production Network when used in a configuration and with equipment that have both been authorized by the Cyber Security Operations Center (CSOC), Enterprise Systems Engineering (ESE) and the local Information System Security Officer (ISSO). Other uses of this technology must follow external data connection processes outlined in the constraint above. Only VA Standard versions of this technology are authorized for use. Refer to the VA Standard Cisco AnyConnect Secure Mobility Client in the `Reference` tab for more information.

[26]	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.

Note:

At the time of writing, version 5.1.4.74 is the most current version, released 06/17/2024.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 4.10.04071 and 4.10.07061. Version 5.1.3.62 is under testing and development for six weeks from 08/07/2024.

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
AnyConnect Diagnostics and Reporting Tool (DART)	DART is the AnyConnect Diagnostics and Reporting Tool that can be used to collect data useful for troubleshooting AnyConnect installation and connection problems. This component doesn`t have a dedicated product page for release 4.x.
Cisco AnyConnect Identity Services Engine (ISE) Compliance Module (also known as Posture Module)	This component allows the user to analyze an endpoint`s compliance when it comes to antivirus, antispyware, and firewall software.
Network Access Manager	The Network Access Manager is client software that provides a secure Layer 2 network in accordance with policies set forth by the enterprise network administrators. The Network Access Manager detects and selects the optimal Layer 2 access network and performs device authentication for access to both wired and wireless networks. The Network Access Manager manages user and device identity and the network access protocols required for secure access. It works intelligently to prevent end users from making connections that are in violation of administrator-defined policies.


Network and Telecommunications Transport	Wide Area Network (WAN)

General Analysis

Adoption Benefits

This technology has a comprehensive set of documentation.
The vendor of this technology is an industry leader in the subject matter.
Use of this technology ensures staff can securely access the VA network with a remote desktop.
This is a well-documented technology.
The use of this technology may help improve the security posture of the organization.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see <a href = "https://nvd.NIST.gov/vuln/search" target="_blank">https://nvd.NIST.gov/vuln/search</a> for more details.
Although this vendor utilizes Federal Information Processing (FIPS) 140-2 encryption, there is no indication based on the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standards (FIPS) 140-2 certified.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
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.
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.
There are other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
This technology may utilize external data connections.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.

Architectural Risks

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

- The information contained on this page is accurate as of the Decision Date (08/15/2024 at 17:13:03 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.1

General Information

Vendor Release Information

Current Decision Matrix (08/14/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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 25.1

General Information

Vendor Release Information

Current Decision Matrix (08/14/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework