|
<Past |
Future> |
| 19x.x.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 247.x |
Approved w/Constraints [5, 7, 8, 10, 11] |
DIVEST [5, 8, 10, 11, 12, 13] |
DIVEST [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 290.x |
Unapproved |
DIVEST [5, 8, 10, 11, 12, 13] |
DIVEST [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 292.x |
Unapproved |
Approved w/Constraints [5, 8, 10, 11, 12, 13] |
Approved w/Constraints [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints [5, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (DIVEST) [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints (POA&M) |
| 317.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
Authorized w/ Constraints [5, 8, 10, 11, 13, 14, 15] |
| Note: |
At the time of writing, version 317.1 is the most current version, released 06/26/2025. |
| | | | [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. | | | [7] | Users must ensure that Google Chrome is implemented with VA-authorized 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. | | | [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 authorized 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-authorized 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 authorized 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. | | | [14] | Users must ensure that Google Chrome is implemented with VA-authorized 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 authorized to be used with Google Chrome.
This technology can potentially be downloaded through the Google Chrome Web store, which is disabled for general use on the VA network.
Users must not utilize Chromium, as it, at the time of writing, requires a POA&M. | | | [15] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. |
|