Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 26.1

Apache Directory Studio

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:	Apache Directory Studio is a directory management platform for use with Lightweight Directory Access Protocol (LDAP) servers. This technology is a Rich Client Platform (RCP) for the Eclipse platform and includes several Eclipse Open Services Gateway initiative (OSGi) plug-ins designed to build and maintain a client platform. Additional plugins may be integrated into Apache Directory Studio and plugins may be run within Eclipse itself. This technology may be configured to interface with any LDAP server and has optional functionality to create LDAP server instances via the ApacheDS component. This technology may create or modify LDAP Data Interchange Format (LDIF) files associated with the connected LDAP server. Additionally, this technology stores all information regarding users, hosts, and services in the LDAP base.
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.9
Decision Date:	09/08/2025 at 18:27:26 UTC
Introduced By:	TRM Request
Vendor Name:	Apache Software Foundation (ASF)
Cage Code:	N/A

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.x	01/10/2012

Current Decision Matrix (08/27/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	Unauthorized, Conditions Required^[a] : 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	Unauthorized, Conditions Required^[b] : 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	Unauthorized, Conditions Required^[c] : 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 Unauthorized, Conditions Required ^[a] .

<Past

CY2025

CY2026

CY2027

Future>

Release

2.x

Authorized w/ Constraints
[11, 12, 14, 16, 17]

Authorized w/ Constraints
[11, 12, 14, 17, 18]

Note:

At the time of writing, version 2.0.0-M17 is the most current version, released 07/24/2021.

Decision Constraints


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

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

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

[16]	This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol. This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Open Java Development Kit (OpenJDK) should not be used with this technology as it is unapproved. Other options are available, see Category Tab for details. Per the Initial Product Review, users must abide by the following constraints: Apache Directory Studio will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information where applicable. AdoptOpenJDK is not an authorized solution for use within the VA. VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO, ISO and SS for pre-existing systems to enter a POA&M for the “TRM Unapproved technology”. Other Java Development Kit (JDK) solutions should be considered for use with Apache Directory Studio.

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

[18]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M. This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Users must not utilize Open Java Development Kit (OpenJDK), as it, at the time of writing, requires a POA&M. Per the Initial Product Review, users must abide by the following constraints: Apache Directory Studio will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information where applicable. AdoptOpenJDK is not an authorized solution for use within the VA. VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO, ISO and SS for pre-existing systems to enter a POA&M for the “TRM Unapproved technology”. Other Java Development Kit (JDK) solutions should be considered for use with Apache Directory Studio.

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
Apache Directory Server	The Apache Directory Server (ApacheDS) component of this technology allows for the creation and launching of LDAP servers. The embedded servers created by ApacheDS store private keys and other related information on a single server.
Apache Directory Server Configuration	The Apache Directory Server Configuration component enables users to edit the server configuration files (.xml and .ldif) of an Apache Directory Server Installation.
LDAP Browser	The Lightweight Directory Access Protocol (LDAP) Browser interfaces with the LDAP Server and allows users to view, read, and modify an LDAP Server architecture tree. From here, entries may be added, edited, or removed.
LDIF Editor	The Lightweight Directory Interchange Format (LDIF) Editor provides an interface for editing LDIF files. This component provides syntax highlighting capabilities as well as content assistance.
Schema Editor	The Schema Editor allows for the editing of schema files in the OpenLDAP format. This component allows attributie types and object classes to be edited for Apache Directory Server and OpenLDAP.


Application Technology Application and Web Server Software	Application Server Software

General Analysis

Adoption Benefits

This technology has a comprehensive set of documentation.
This technology may improve productivity for specific staff whose responsibilities include managing Apache servers.
This technology is available at no cost through open source licensing and supports VA`s open source initiative.

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.
This technology can potentially use Secure Sockets Layer (SSL), a protocol which requires a POA&M for use on the VA network.
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.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
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 Open Java Development Kit (OpenJDK) which requires a POA&M for use on the VA network.
IPR/SAR Adoption Risk - The product is not Federal Information Processing standards (FIPS) 140-2 or its successor certified.
IPR/SAR Adoption Risk - Apache Directory Studio uses Java and recommends AdoptOpenJDK for use with the product.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

- The information contained on this page is accurate as of the Decision Date (09/08/2025 at 18:27:26 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (08/27/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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (08/27/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

EMAIL UPDATES

VA Categories

View the VA Categorization Framework