Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.7

Anaconda

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:	Anaconda is a Python and R distribution technology for large-scale data processing, predictive analytics, and scientific computing. Anaconda distribution comes with 7,500 open-source packages can be installed from PyPI as well as the Conda package and virtual environment manager. This technology provides data-science packages suitable for Windows, Linux, and macOS. Data stored by this technology can be stored on a user`s local drive, Anaconda Cloud, or a Microsoft Structured Query Language (SQL) database. This technology is available in five editions, 2 for individual users and 3 for organizations. Individual user plans are Free and Starter. Organization plans are Pro (Cloud), Business, and Enterprise. This entry covers only the Organization editions. Note: The vendor pages are only accessible through a private connection. 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/
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 System Security Officer (ISSO), 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 v25.7
Decision Date:	07/30/2025 at 03:04:28 UTC
Introduced By:	TRM Request
Vendor Name:	Anaconda

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.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.3	07/02/2015
4.2	09/28/2016
4.4	05/21/2017
5.x	10/25/2017
2019.x	04/04/2019
2020.x	03/11/2020
2021.x	05/15/2021
2022.x	05/10/2022
2023.x	03/20/2023
2024.x	02/26/2024
2025.x	06/23/2025

Current Decision Matrix (07/23/2025)

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 System Security Officer (ISSO), 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

CY2023

CY2024

CY2025

Future>

Release

2.3

Unapproved

Authorized w/ Constraints (POA&M)

4.2

Unapproved

Authorized w/ Constraints (POA&M)

4.4

Unapproved

Authorized w/ Constraints (POA&M)

5.x

Approved w/Constraints
[10, 14, 15, 16, 17]

Approved w/Constraints
[14, 15, 16, 17, 18, 19, 20]

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

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

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

Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24, 25]

Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 25, 26]

2019.x

Unapproved

Authorized w/ Constraints (POA&M)

2020.x

Unapproved

Authorized w/ Constraints (POA&M)

2021.x

DIVEST
[10, 14, 15, 16, 17]

DIVEST
[14, 15, 16, 17, 18, 19, 20]

DIVEST
[14, 16, 17, 18, 19, 20, 21]

Unapproved

Authorized w/ Constraints (POA&M)

2022.x

Approved w/Constraints
[10, 14, 15, 16, 17]

DIVEST
[14, 15, 16, 17, 18, 19, 20]

DIVEST
[14, 16, 17, 18, 19, 20, 21]

DIVEST
[16, 17, 18, 20, 21, 22, 23]

DIVEST
[16, 17, 20, 21, 22, 23, 24, 25]

Authorized w/ Constraints (POA&M)

2023.x

Unapproved

Approved w/Constraints
[14, 15, 16, 17, 18, 19, 20]

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

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

DIVEST
[16, 17, 20, 21, 22, 23, 24, 25]

Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 24, 25]

Authorized w/ Constraints (POA&M)

2024.x

Unapproved

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

Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 24, 25]

Authorized w/ Constraints (DIVEST)
[16, 17, 20, 21, 22, 23, 25, 26]

2025.x

Unapproved

Authorized w/ Constraints (POA&M)

Authorized w/ Constraints
[16, 17, 20, 21, 22, 23, 25, 26]

Note:

At the time of writing, version 5.8.1.6 is the most current version for Enterprise, released 07/03/2025.

At the time of writing, version 2025.06-1 is the most current version for the Free version, released 07/18/2025.

Decision Constraints


[10]	Per the Initial Product Review, users must abide by the following constraints: 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. This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Anaconda. Currently Kubernetes, Docker, and OpenShift are container products VA is evaluating. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information. 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. System owners must ensure they are using the most recent version of Anaconda. Currently version 2020.11 for Individual Edition and 5.4.1 for the Enterprise Edition. Users should check with their supervisor, Information System Security Office (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

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

[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 VA Handbook 6500.

[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]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

[18]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Per the Initial Product Review, users must abide by the following constraints: Anaconda will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Anaconda. Currently Kubernetes, Docker, and OpenShift are container products VA is evaluating. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information. 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 must ensure they are using the most recent version of Anaconda. Currently version 2023.03-0for Individual Edition and 5.6.1 for the Enterprise Edition. Users should check with their supervisor, Information System Security Office (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations

[19]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

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

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

[22]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

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

[24]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users must not use R-Studio with this technology, as it is unapproved for use on the TRM, other options are available. Per the Initial Product Review, users must abide by the following constraints: Anaconda will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Anaconda. Currently Kubernetes, Docker, and OpenShift are container products VA is evaluating. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information. 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 must ensure they are using the most recent version of Anaconda. Currently version 2023.03-0for Individual Edition and 5.6.1 for the Enterprise Edition. Users should check with their supervisor, Information System Security Office (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations

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

[26]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M. Users must not utilize R-Studio, as it, at the time of writing, requires a POA&M. This technology can potentially utilize publicly available artificial intelligence (AI) services. Per the Initial Product Review, users must abide by the following constraints: Anaconda will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information. The use of AI is increasing, and guidance is still developing. Users must check the most recent VA guidance before using AI technologies and solutions. Consideration should be given to the source of any initial data for the AI tool, if any VA data will be collected and ingested into the data set, where that data will be stored, and what rights the VA has to that data. “No web-based, publicly available generative AI service has been approved for use with VA-sensitive data. Examples of these include OpenAI’s ChatGPT and GPT4, Google’s Bard, Anthropic’ s Claude, and Microsoft’s new Bing. VA follows existing federal requirements and processes to ensure VA data is protected. When users enter information into an unapproved web-based tool, VA loses control of the data. Due to potential information security risks, SaaS/PaaS solutions must complete the Business Integration and Outcomes Service (BIOS) 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 must use the latest version of this product and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities. System owners must ensure that they fully review the Anaconda Terms of Service and that they have the correct licensing to use this product. OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” and OMB Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’ ability to use software that is not developed using secure practices. The attestation form will allow software producers to confirm that they follow those practices. VA Supply Chain Risk Management (SR) Policy and VA Handbook 6500.6, Contract Security, Appendix C states that the contractor (including producers and resellers) shall comply with Office of Management and Budget (OMB) M-22-18 and M-23-16 when using third-party software on VA information systems or otherwise affecting the VA information. This includes new software purchases and software renewals for software developed or modified by major version change after the issuance date of M-22-18 (September 14, 2022).

Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
Numba	Numba is an open-source Just-In-Time compiler (JIT) that translates a subset of Python and NumPy into fast machine code using Low Level Virtual Machine (LLVM), via the llvmlite Python package. It offers a range of options for parallelising Python code for Computer Processing Unit's (CPUs) and Graphic Processing Unit's (GPUs), often with only minor code changes.


Application Technology Development Tools	Development Frameworks

General Analysis

Adoption Benefits

The Individual Edition of this technology can be acquired without cost through open source licensing and supports VA`s open source initiative. This technology also has an enterprise edition with a licensing fee.
Commercial services and support are available for the enterprise edition for this software.
This technology has a comprehensive set of documentation.

Adoption Risks

This technology can integrate with and alter database technologies.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search/ for more details.
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.
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.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
This technology can potentially use Secure Sockets Layer (SSL), a protocol which requires a POA&M for use on the VA network.
This technology can potentially use R-Studio which requires a POA&M for use on the VA network.
This technology can potentially utilize publicly available artificial intelligence (AI) services.
IPR/SAR Adoption Risk - Anaconda is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified.
IPR/SAR Adoption Risk - Anaconda is an AI platform.
IPR/SAR Adoption Risk - Anaconda includes cloud-based functionality.
IPR/SAR Adoption Risk - There are multiple published vulnerabilities including CVE-2025-32799 and CVE-2025-32798 that affect versions prior to 25.4.0 of Anaconda.
IPR/SAR Adoption Risk - According to vendor documentation “Use of Anaconda by those at organizations with more than 200 employees or contractors (including Affiliates), or special use cases of Anaconda (such as mirroring and enterprise scaled usage ),requires a paid Business license. If you are at an academic, non-profit or research institution you may be exempt from the paid license requirement.”
IPR/SAR Adoption Risk - Anaconda only provides a Secure Software Development Attestation Form for one component of Anaconda (Package Security Manager Cloud).
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology can use a VA-preferred database.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

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 (07/30/2025 at 03:04:28 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.7

General Information

Vendor Release Information

Current Decision Matrix (07/23/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

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

General Information

Vendor Release Information

Current Decision Matrix (07/23/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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