Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 25.1

AppDynamics
AppDynamics Technology

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 02/22/2010
3.8 06/14/2014
3.9 09/24/2014
4.0 04/02/2014
4.1 06/23/2015
4.2 02/23/2016
4.3 04/05/2017
4.4 11/01/2017
4.5.x 07/15/2018
20.x 02/01/2020
21.x 01/18/2021
22.x 05/05/2022
23.x 01/30/2023
24.x 04/17/2024

Current Decision Matrix (06/24/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 CY2017 CY2018 CY2019 Future>
Release Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
2.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
3.8 Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
3.9 Approved w/Constraints
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[6, 8, 9, 10]
Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
4.0 Approved w/Constraints
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[5, 6, 7]
DIVEST
[6, 8, 9, 10]
Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
4.1 Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
DIVEST
[6, 8, 9, 10]
DIVEST
[6, 8, 9, 10]
DIVEST
[6, 9, 10]
Unapproved Unapproved Unapproved Unapproved Unapproved
4.2 Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[5, 6, 7]
Approved w/Constraints
[6, 8, 9, 10]
Approved w/Constraints
[6, 8, 9, 10]
DIVEST
[6, 9, 10]
DIVEST
[6, 9, 10]
DIVEST
[6, 9, 10]
Unapproved Unapproved Unapproved
4.3 Unapproved Unapproved Unapproved Unapproved Approved w/Constraints
[6, 8, 9, 10]
Approved w/Constraints
[6, 8, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
DIVEST
[6, 9, 10]
DIVEST
[6, 9, 10]
Unapproved Unapproved
4.4 Unapproved Unapproved Unapproved Unapproved Approved w/Constraints
[6, 8, 9, 10]
Approved w/Constraints
[6, 8, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
DIVEST
[6, 9, 10]
DIVEST
[6, 9, 10]
4.5.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
Approved w/Constraints
[6, 9, 10]
20.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
21.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
22.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
23.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
24.x Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
 

Decision Constraints

[1]This review approves the AppDynamics Pro on-premise solution and does not include the software as a service (SaaS) version.

[2]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 authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized 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 authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[3]This review is specific to the AppDynamics Pro on-premise solution and does not include the software as a service (SaaS) version of the solution. The SaaS version will require an additional security review to verify that it complies with organization security policies.

[4]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 Security Officer (ISO) 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).

[5]This review is specific to the AppDynamics on-premise solution and does not include the software as a service (SaaS) version of the solution. The SaaS version will require an additional security review to verify that it complies with organization security policies.

[6]Users should check with their supervisor, Information Security Office (ISO) 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.

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

[8]This review is specific to the AppDynamics on-premise solution and does not include the software as a service (SaaS) version of the solution.

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

[10]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).
Note: At the time of writing, version 24.6.0 is the most current version, released 06/24/2024.
- The information contained on this page is accurate as of the Decision Date (06/26/2024 at 16:14:49 UTC).