Dynatrace Synthethic Recorder

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:	DynaTrace Synthetic Recorder is a screen recording technology that is used to record the sequences of clicks that users want simulated user sessions to follow when browser clickpaths are replayed. Users can record button clicks, page scrolls, and even user input. This Google Chrome extension is part of Dynatrace product offerings. The extension will not work or show any presence unless the user logs on to an account at www.dynatrace.com.
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.5
Decision Date:	05/30/2024 at 02:59:18 UTC
Introduced By:	TRM Request
Vendor Name:	DynaTrace

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
19x.x.x
247.x	08/02/2022
290.x	04/22/2024
292.x

Current Decision Matrix (05/22/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 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

CY2025

CY2026

CY2027

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

19x.x.x

Unapproved

247.x

Divest
[5, 8, 10, 11, 12, 13]

Unapproved

290.x

Divest
[5, 8, 10, 11, 12, 13]

Unapproved

292.x

Approved w/Constraints
[5, 8, 10, 11, 12, 13]

Decision Constraints


[1]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: Ensure all applications that use Dynatrace Synthetic Recorder employ a FIPS 140-2 validated cryptographic modules for encryption of data at rest and in transit. The administrator or installer must ensure that Dynatrace Synthetic Recorder is obtained from the authentic webstore or website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Based on the Department of Defense Mobile Code categorization schema (Instruction 8552.01), the ESECVS has concluded the DynaTrace Synthetic Recorder is shown to conform to Category 2 definitions. Category 2 mobile code technologies have full functionality allowing mediated access and environment-controlled access to host system services and resources. Category 2 technologies may have known security vulnerabilities but also have fine-grained, periodic, or continuous countermeasures or safeguards. VA Solution Delivery, Desktop and Device Engineering manages the Chrome, standard configuration. The standard is based on the Chrome DISA STIG, which requires all extensions to be blocked by default. For browser plugins/extensions to be included in the national standard configuration, a request and a business justification must be submitted to Desktop and Device Engineering at the following URL: https://vaww.eie.va.gov/SysDesign/CS/dtrequests. If approved and enabled, all VA endpoint browsers will receive the extension. Therefore, all browser extensions must be evaluated to determine how each will affect the browser with all the other approved extensions as well as performance of the browser.

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

[3]	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 approved and the user should take the proper steps to decline those installations.

[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]	Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements.

[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]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Security Assessment Review, users must abide by the following constraints: Ensure all applications that use Dynatrace Synthetic Recorder employ a FIPS 140-2 certified cryptographic modules for encryption of data at rest and in transit. The administrator or installer must ensure that Dynatrace Synthetic Recorder is obtained from the authentic webstore or website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware.

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

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

[10]	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 approved and the user should take the proper steps to decline those installations.

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

[12]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Security Assessment Review, users must abide by the following constraints: Ensure all applications that use Dynatrace Synthetic Recorder employ a FIPS 140-2 certified cryptographic modules for encryption of data at rest and in transit. The administrator or installer must ensure that Dynatrace Synthetic Recorder is obtained from the authentic webstore or website with verifiable web certificate. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. The Dynatrace Synthetic Recorder Chrome Extension uses permissions that may not be necessary for the extension to function. Four Critical, Two High, Three Medium, and Two Low risk permissions for Chrome were noted. It is advised that permissions are verified with the developer and removed if they are not necessary for the extension to function. Using permissions that are not essential to the extension’s functionality expose the system, using the Dynatrace Synthetic Record Browser Extension, to potential vulnerabilities and additional risks that could otherwise be avoided by disabling nonessential permissions. This technology is only approved to be used with Google Chrome. Users must not utilize Chromium, as it is at the time of writing, unapproved in the TRM.

[13]	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 292.1 is the most current version, released 05/21/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
Chromium Framework	The Chromium product is installed on Dynatrace active gateways and enables them perform their synthetic requests unattended. The Dynatrace Synthetics software uses Chromium libraries rather than the complete product.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Chromium - (required for some configurations)

Comparable Technologies:

No comparable entries have been identified.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

The use of this technology may help improve the security posture of the organization.
This is a well-documented technology.
There is no licensing fee associated with this technology.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.

Adoption Risks

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.
This technology is a browser plug-in or extension. Proper analysis must be conducted on this technology.
This technology is a scanning utility. Users must ensure scans comply with system owner guidance.
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.
The product is not Federal Information Processing Standards (FIPS) 140-2 or its successor certified. The Dynatrace Synthetic Recorder records online activity like button clicks, page scrolls, and user input that may contain sensitive data such as Protected Health Information (PHI) or Personally Identifiable Information (PII).
The software is available as a download. A modified version of the software could introduce vulnerabilities to the Department of Veterans Affairs (VA) network.
This technology is available as freeware. If commercial support is not purchased, the product will be without clearly defined support options which may result in suboptimal enterprise level support.
Eleven findings from Chrome permissions were found:
• Critical:
o cookies - Gives your extension access to the chrome.cookies API.
o debugger - Gives your extension access to the chrome.debugger API.
o webRequest - Gives your extension access to the
chrome.webRequest API.
o - Matches any URL that uses a permitted scheme
• High:
o tabs - Gives your extension access to privileged fields of the Tab
objects used by several APIs including chrome.tabs and
chrome.windows. In many circumstances your extension will not need
to declare the "tabs" permission to make use of these APIs.
o contentSettings - Gives your extension access to the
chrome.contentSettings API.
• Medium:
o webNavigation - Gives your extension access to the
chrome.webNavigation API.
o Storage - Gives your extension access to the chrome.storage API.
o Downloads - Gives your extension access to the chrome.downloads
API.
• Low:
o webRequestBlocking - Required if the extension uses the
chrome.webRequest API in a blocking fashion.
o activeTab - Requests that the extension be granted permissions
according to the activeTab specification.
This technology is a browser plug-in or extension.
This technology can potentially use Chromium, an unapproved technology.

Architectural Benefits

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 is not portable as it runs only on Windows platforms.

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 (05/22/2024)

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 (05/22/2024)

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