Adobe Bridge

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:	Adobe Bridge is a digital asset (photographs, graphics, and videos) manager. The technology provides centralized management of all digital media files for all the technologies included in Adobe Creative Suite and Adobe Creative Cloud. Bridge provides housekeeping utilities such as batch rename, assigning ratings to images, file organization, and file searching. 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 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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/30/2024 at 02:59:17 UTC
Introduced By:	TRM Request
Vendor Name:	Adobe

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
CS4	09/23/2008	10/15/2013
CS5	04/15/2010	04/12/2015
CS6	02/01/2013	05/07/2017
CC 2015 (6.0.x)	07/30/2013	06/17/2018
CC 2015 (6.1.x)	06/15/2015	06/18/2019
CC 2015 (6.2.x)	02/06/2016	02/10/2021
CC 2015 (6.3.x)
CC 2017 (7.0.x)	11/02/2016	11/02/2021
CC 2018 (8.0.x)	10/01/2017
CC 2018 (8.1.x)	07/17/2018
CC 2019 (9.1.x)	06/17/2019
10.1.1	06/01/2020
11.1	06/23/2021
12.0	10/26/2021
12.0.x	01/01/2022
13.0.x	01/01/2023
14.0.x	09/13/2023
14.1.x	05/13/2024

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

CY2020

CY2021

CY2022

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

CS5

Unapproved

CS6

Unapproved

CC 2015 (6.0.x)

Prohibited

CC 2015 (6.1.x)

Prohibited

CC 2015 (6.2.x)

Unapproved

CC 2015 (6.3.x)

Unapproved

CC 2017 (7.0.x)

Unapproved

CC 2018 (8.0.x)

Divest
[6, 10, 12, 13]

Unapproved

CC 2018 (8.1.x)

Divest
[6, 10, 12, 13]

Unapproved

CC 2019 (9.1.x)

Approved w/Constraints
[6, 10, 12, 13]

Divest
[6, 10, 13, 14]

Divest
[6, 14, 15, 16]

Divest
[6, 14, 16, 17]

Divest
[6, 16, 17, 18]

Unapproved

10.1.1

Unapproved

Approved w/Constraints
[6, 10, 13, 14]

Approved w/Constraints
[6, 14, 15, 16]

Approved w/Constraints
[6, 14, 16, 17]

Divest
[6, 16, 17, 18]

Divest
[3, 6, 16, 17, 19, 20]

Divest
[3, 6, 16, 19, 20, 21]

Divest
[6, 16, 20, 21, 22]

11.1

Unapproved

Approved w/Constraints
[6, 16, 17, 18]

Approved w/Constraints
[3, 6, 16, 17, 19, 20]

Approved w/Constraints
[3, 6, 16, 19, 20, 21]

Divest
[6, 16, 20, 21, 22]

12.0

Unapproved

Approved w/Constraints
[6, 16, 17, 18]

Approved w/Constraints
[3, 6, 16, 17, 19, 20]

Approved w/Constraints
[3, 6, 16, 19, 20, 21]

Divest
[6, 16, 20, 21, 22]

12.0.x

Unapproved

Approved w/Constraints
[3, 6, 16, 17, 19, 20]

Approved w/Constraints
[3, 6, 16, 19, 20, 21]

Approved w/Constraints
[6, 16, 20, 21, 22]

13.0.x

Unapproved

14.0.x

Unapproved

14.1.x

Unapproved

Decision Constraints


[1]	Creative Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. Use of non-Creative Cloud versions of this technology should be restricted to those who use Adobe Creative Suite digital media technologies and have an official need to publish digital media information on behalf of the Department of Veterans Affairs.

[2]	Editing and publication of official materials and graphics utilizing this software should be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options.

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

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

[5]	Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options.

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

[7]	Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

[8]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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).

[9]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).

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

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

[12]	Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

[13]	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 Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[14]	Users must ensure that Microsoft Internet Explorer (IE) is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

[15]	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 Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

[17]	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 Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

[19]	Users must ensure that Google Chrome and Microsoft Internet Explorer are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

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

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

[22]	Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used. Users must ensure that Google Chrome and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Editing and publication of official materials and graphics utilizing this software must be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options. Due to CVE-2016-0951, CVE-2016-0952, and CVE-2016-0953 Creative Cloud (CC) versions before CC 2015 (6.2.x) are prohibited.

Note:

At the time of writing, version 14.1.0 is the most current version

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 14.0.1. Version 14.0.2 and 14.0.3 are under testing and development.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
Adobe Digital Negative Graphic (DNG) Converter	Adobe Digital Negative Graphic (DNG) Converter is a utility that enables users to convert camera-specific raw image files from different types of cameras to the universal DNG format for archiving and reading.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Collaboration Software	Content Management
Collaboration and Electronic Workplace Productivity Software	File Manager and Viewer

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

DirectX
Microsoft Edge. - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include automation of file management functions using the technologies batch facility.
This technology has a comprehensive set of documentation.
There is no licensing fee associated with this technology.

Adoption Risks

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.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.

Architectural Benefits

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

Architectural Risks

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

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/28/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/28/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