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 19.1

Github Enterprise
Github Enterprise Technology

General InformationGeneral Information help

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: GitHub Enterprise is the on-premises version of GitHub. GitHub Enterprise is designed for use by large-scale enterprise software development teams where the enterprise wishes to host their repositories behind a corporate firewall. With GitHub Enterprise, code collaboration and review are built into the development process. Teams can share work, discuss changes, and get feedback all in one place.

This technology has been deployed in VA`s on-premises Enterprise Cloud (VAEC) environment servers, in a private cloud. Approval of cloud services and cloud based products is not in the purview of the TRM. For information on cloud services and cloud based product approval, please see the ECS Portal at:

This entry pertains only to the Enterprise Github server software installed on the VA network. It does not apply or include the variety of desktop clients or additional plugins that are compatible to Enterprise Github. Their approval status are tracked separately in the TRM.
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
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v18.6
Decision Date: 06/14/2018
Introduced By: TRM Request
Vendor Name: Github
- The information contained on this page is accurate as of the Decision Date (06/14/2018).