GitHub Enterprise is a version control/source control solution which combines the power and flexibility of GitHub with the security, administration, and control businesses need. With GitHub Enterprise, you can foster greater transparency and collaboration amongst developers and allow seamless integration of third party tools — all without compromising security practices.
- Collaboration-Code search, Pull requests, Inline editing, @mentions
- Security Encryption. In flight & at rest. Track issues
- 2-factor authentication, Team/Org permissions. Fork & Instance permissions
- LDAP,SAML,CAS & Audit (User Actions & Git Actions)
- AWS/AWS GovCloud/Azure,GCP,On-premise,Deployment flexibility
- High availability, Locally controlled backups, Monitoring&Dashboards
- Management via SSH, Custom SMTP configuration
- In-app messaging to users, Custom upgrades
- Flexible hosting options & 24x7 support on urgent issues
- Government-Streamline government IT infrastructure from end to end
- Code collaboration, review with control, visibility and automated intelligence.
- Share team work, discuss changes-get feedback all in one place.
- Security-Manage permissions from one place with SAML/LDAP Sync
- Invite cross-team collaboration on GitHub-providing essential controls
- GitHubEnterprise-available on VMware, AWS, OpenStack,on prem/private cloud.
- Configure your instance to meet your security and regulatory needs.
- Built-in-tools & dashboard to administer your Github instance
- Review license, browse user reports, initiate an SSH key audit.
- Improve DevOps-Global support team is available 24/7
- Government-Streamline government IT infrastructure from end to end.
£200 to £250 per user per year
- Education pricing available
- Free trial available
|Software add-on or extension||Yes, but can also be used as a standalone service|
|What software services is the service an extension to||Git, Github|
|Cloud deployment model||Hybrid cloud|
|System requirements||Underlying Infrastructure|
|Email or online ticketing support||Email or online ticketing|
|Support response times||
As part of the GitHub for Business plan.
24/5 support with 8-hour response time.
|User can manage status and priority of support tickets||No|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
|Support levels||GitHub employs dedicated engineers as the first and only level of support. With this in mind, we expect our first and single line of support to be able to troubleshoot any issues, no matter how technical. If a ticket requires further investigation then the support engineer will proactively work with the engineering team responsible for the feature in question.|
|Support available to third parties||Yes|
Onboarding and offboarding
User Documentation is provided upon request.
All of the install guides are available online.
Onsite training, Online training, Kickstarts and further assistance is available - but at an additional cost.
The product aims to be self-sufficient for all levels of knowledge.
|Other documentation formats||MS word|
|End-of-contract data extraction||Customer code is held in Git, an open source standard used by the majority of the world's developers. Code can be transferred to any Git based repository through a GitClone|
|End-of-contract process||The subscription fee grants access to the service, so no payment results in the account being locked. When an account is locked, private repositories cannot be accessed until paid status is resumed. Private data will never be made public, nor will it be automatically deleted. However, after a period of non-payment, GitHub reserves the right to delete content from locked repositories. GitHub aims to be user focussed so will not ask the buyer to pay retrospectively for periods of non-payment while the private data is locked. If the buyer needs short-term access to the repositories to migrate data away from the service, this will be provided via GitHub Support at no additional charge.|
Using the service
|Web browser interface||Yes|
|Application to install||Yes|
|Compatible operating systems||
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||GitHub uses different views for mobile devices to present only essential information in order to preserve fast loading times. Users can still choose to visit to full desktop version if they're after a feature that is not shown on the mobile view.|
|Accessibility standards||None or don’t know|
|Description of accessibility||Users have full access once software license keys are delivered. From there the user has the ability to grant or restrict access to anyone|
Full UI test has been conducted.
Integral part of QA
|What users can and can't do using the API||GitHub's API aims to cover all functionality of the product. Users are given the expectation that whatever can be done through the browser should have an API counterpart.|
|API documentation formats||
|API sandbox or test environment||No|
|Description of customisation||
Specific operating system customisation.
Customisation is Usually carried out by network ops and any persons with authorisation.
|Independence of resources||GitHub has put in place rate limiting and DDOS protection technologies and software techniques. GitHub is currently in the top 60 of the most visited websites on the Internet. GitHub measures its load in the millions of users and as such applies very rigorous controls around fair usage to guarantee a reliable service for everyone.|
|Service usage metrics||Yes|
Yes. We provide an overview of the service. At the account level we provide valuable data and graphs around the repository and team activity. In GitHub you can quickly check contribution statistics, commit activity and a visual network of branches and forks. Administrators have access to all data via the API.
Contribution statistics, commit activity and a visual network of branches and forks. At an instance level we provide: Application Server Availability, Mean Web Response Time, Mean API Response Time, 98th perc. Web Response Time, Exception Percentage, Mean Webhook Delivery Time, 98th perc. Browser Time to First Byte.
|Reporting types||API access|
|Supplier type||Reseller providing extra features and support|
|Organisation whose services are being resold||Github Inc.|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Security Clearance (SC)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Supplier-defined controls|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||In-house|
|Protecting data at rest||
|Other data at rest protection approach||Through logical and physical access controls, both within the application design, and controls that are configurable by the customer (2FA). By design, GitHub requires the data at rest to be unencrypted.|
|Data sanitisation process||No|
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||Git data can be exported by using the built-in mechanisms for cloning repositories. All other metadata like Issues, Pull Requests, Wikis, Projects and developer data has to be extracted using the API.|
|Data export formats||
|Other data export formats||Dowloaded either by the Git protocol/via the API.|
|Data import formats||
|Data protection between buyer and supplier networks||Other|
|Other protection between networks||
All data is encrypted in transit using HTTPS or SSH.
SSL is sufficient to protect the data in transit.
|Data protection within supplier network||Other|
|Other protection within supplier network||
GitHub has multiple layer of network defences in place, including Border router which also performs stateless traffic filtering, Firewall, and Application proxy. Network devices are configured to only allow permitted traffic and services (ports) through preconfigured restricted routes. All other traffic are routed to the DMZ and firewall.
Logging and monitoring, SIRT investigation, access management, change management, standardised config management.
Availability and resilience
GitHub puts in place rate limiting and DDOS protection technologies and software techniques. Currently Top 60 of the most visited websites in the internet we measure our load in the millions of users and as such we apply very rigorous controls around fair usage to guarantee a stable service for everyone.
|Approach to resilience||GitHub puts in place rate limiting and DDOS protection technologies and software techniques. Currently Top 60 of the most visited websites in the internet we measure our load in the millions of users and as such we apply very rigorous controls around fair usage to guarantee a stable service for everyone.|
Identity and authentication
|User authentication needed||Yes|
|Other user authentication||Users need a username and password to authenticate. Furthermore if two-factor authentication is enabled GitHub supports Timed One Time Password (TOTP), Universal two-factor (U2F) and text messaging. For Git authentication users can provide a username/password pair or authenticate via an SSH key pair.|
|Access restrictions in management interfaces and support channels||Support is available for all users and is done via e-mail. Access control is delegated to the e-mail server and client(s). Regarding management interfaces GitHub provides several different user roles within a GitHub for Business account. Management control of the account is given to Organisation Owners. Within an organisation non-owners can be made administratives of groups of repositories but without access to the management interface for the buyer's account.|
|Access restriction testing frequency||Less than once a year|
|Management access authentication||
Audit information for users
|Access to user activity audit information||You control when users can access audit information|
|How long user audit data is stored for||User-defined|
|Access to supplier activity audit information||No audit information available|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||No|
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Other security accreditations||No|
|Named board-level person responsible for service security||Yes|
|Security governance accreditation||No|
|Security governance approach||Github VP of Security reports into the CEO/CTO of the company; strong sponsorship and integration into engineering, IT, legal and other company functions ensures secure mindset is part of being an employee. As GitHub runs on GitHub itself, all part of the Security and Security-GRC org have direct visibility into work and are active contributors across the product and service.|
|Information security policies and processes||We have a core employee handbook that outlines a number of employment standard and expectations of conduct that employees must sign as part of their hiring paperwork, including code of conduct, computing policy, and escalation to security for incidents. This is available on our intranet, and is supplemented by other complementary policy type documents.|
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||GitHub is an Agile/Devops development culture, and uses GitHub.com to build and execute change management over the GitHub product offerings.|
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||Github do not state compliance with one individual standard we have included leading industry practices that are approrpiate to GitHub. We are in our readienss phase on our SOC 2 audit work, this report will be available once issued, but no hard date has been set for the audit at this time. Github subscribe to vendor vulnerabilities communications, assess any notifications for relevance, and patch; this is also complemented by our internal application security team reviews and automated testing, by external security researchers testing of our systems, and resulting patching.|
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||Hot storage of centralised system logs varies by sub-system ranging from 15 to 30 days. Core system logs are archived indefinitely. Monitoring for unexpected occurrences and subsequent alerting is sent to Security Operations for investigation|
|Incident management type||Supplier-defined controls|
|Incident management approach||
We do not state compliance with one individual standard we have included leading industry practices that are appropriate to GitHub. We are in our readiness phase on our SOC 2 audit work, this report will be available once issued, but no hard date has been set for the audit at this time.
We have an established SIRT, modelled on leading industry practices.
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£200 to £250 per user per year|
|Discount for educational organisations||Yes|
|Free trial available||Yes|
|Description of free trial||
Try Github Enterprise trial version.
With GitHub Enterprise, organisations can enable transparent access to resources without compromising security or taking on risk. Developers can easily find and reuse code, collaborate on projects regardless of team or geography, and interactively learn from each other throughout the development process.
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|