Systemübersicht

Inhalt dieses Artikels

• Speicherarchitektur
• Bereitstellungsoptionen
• Datenaufbewahrung und Rechenzentrumsredundanz
• Sicherheit
• Open-Source-Abhängigkeiten für GitHub Enterprise Server

Speicherarchitektur

GitHub Enterprise Server requires two storage volumes, one mounted to the root filesystem path (/) and the other to the user filesystem path (/data/user). Diese Architektur vereinfacht die Upgrade-, Rollback und Wiederherstellungsprozeduren, indem die in Ausführung befindliche Softwareumgebung von den persistenten Anwendungsdaten getrennt wird.

Das Root-Dateisystem ist im verteilten Maschinen-Image enthalten. Es enthält das Basisbetriebssystem und die GitHub Enterprise Server-Anwendungsumgebung. Das Root-Dateisystem sollte als flüchtig behandelt werden. Daten auf dem Root-Dateisystem werden beim Upgrade auf künftige GitHub Enterprise Server-Versionen ersetzt.

Das Root-Dateisystem enthält Folgendes:

• benutzerdefinierte Zertifikate der Zertifizierungsstelle (CA) (in /usr/local/share/ca-certificates)
• benutzerdefinierte Netzwerkkonfigurationen
• benutzerdefinierte Firewallkonfigurationen
• den Replikationszustand

Das Benutzerdateisystem enthält die Benutzerkonfiguration und -daten, beispielsweise

• Git-Repositorys,
• Datenbanken,
• Suchindizes,
• auf GitHub Pages-Websites veröffentlichte Inhalte,
• große Dateien von Git Large File Storage,
• Pre-Receive-Hook-Umgebungen.

Bereitstellungsoptionen

Sie können GitHub Enterprise Server als eine einzelne virtuelle Appliance oder in einer Hochverfügbarkeitskonfiguration bereitstellen. Weitere Informationen finden Sie unter „GitHub Enterprise Server für Hochverfügbarkeit konfigurieren“.

Einige Organisationen mit Zehntausenden Entwicklern können ebenfalls vom GitHub Enterprise Server Clustering profitieren. For more information, see "Clustering overview."

Datenaufbewahrung und Rechenzentrumsredundanz

GitHub Enterprise Server unterstützt Online- und inkrementelle Backups mit den GitHub Enterprise Server-Backup-Dienstprogramme. Sie können inkrementelle Snapshots über eine sichere Netzwerkverbindung (den SSH-Verwaltungsport) über weite Entfernungen für den externen oder geografisch verteilten Storage erstellen. You can restore snapshots over the network into a newly provisioned appliance at time of recovery in case of disaster at the primary datacenter.

Zusätzlich zu Netzwerk-Backups werden AWS- (EBS) und VMware-Disk-Snapshots der Benutzer-Storage-Volumes unterstützt, während die Appliance offline ist oder sich im Wartungsmodus befindet. Regelmäßige Volume-Snapshots können als kostengünstige, unkomplizierte Alternative zu Netzwerk-Backups mit GitHub Enterprise Server-Backup-Dienstprogramme verwendet werden, wenn Ihre Service Level-Anforderungen eine regelmäßige Offline-Wartung ermöglichen.

For more information, see "Configuring backups on your appliance."

Sicherheit

GitHub Enterprise Server is a virtual appliance that runs on your infrastructure and is governed by your existing information security controls, such as firewalls, IAM, monitoring, and VPNs. Using GitHub Enterprise Server can help you avoid regulatory compliance issues that arise from cloud-based solutions.

GitHub Enterprise Server also includes additional security features.

• Operating system, software, and patches
• Network security
• Application security
• External services and support access
• Encrypted communication
• Users and access permissions
• Authentifizierung
• Audit and access logging

Operating system, software, and patches

GitHub Enterprise Server runs a customized Linux operating system with only the necessary applications and services. GitHub manages patching of the appliance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for GitHub applications. GitHub also provides critical security patches as needed outside of the regular release cycle.

Network security

GitHub Enterprise Server's internal firewall restricts network access to the appliance's services. Only services necessary for the appliance to function are available over the network. For more information, see "Network ports."

Application security

GitHub's application security team focuses full-time on vulnerability assessment, penetration testing, and code review for GitHub products, including GitHub Enterprise Server. GitHub also contracts with outside security firms to provide point-in-time security assessments of GitHub products.

External services and support access

GitHub Enterprise Server can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "Configuring email for notifications," "Setting up external monitoring," and "Log forwarding."

You can manually collect and send troubleshooting data to GitHub-Support. For more information, see "Providing data to GitHub-Support."

Encrypted communication

GitHub designs GitHub Enterprise Server to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). GitHub Enterprise Server supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "Configuring TLS."

By default, the appliance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "About SSH" and "Accessing the administrative shell (SSH)."

Users and access permissions

GitHub Enterprise Server provides three types of accounts.

• The admin Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "Accessing the administrative shell (SSH)."
• User accounts in the appliance's web application have full access to their own data and any data that other users or organizations explicitly grant.
• Site administrators in the appliance's web application are user accounts that can manage high-level web application and appliance settings, user and organization account settings, and repository data.

For more information about GitHub Enterprise Server's user permissions, see "Access permissions on GitHub."

Authentifizierung

GitHub Enterprise Server provides four authentication methods.

• SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "About SSH" and "Accessing the administrative shell (SSH)."
• Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "Using built-in authentication."
• External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "Authenticating users for your GitHub Enterprise Server instance."
• OAuth and Personal Access Tokens provide access to Git repository data and APIs for both external clients and services. For more information, see "Creating a personal access token for the command line."

Audit and access logging

GitHub Enterprise Server stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which GitHub Enterprise Server stores permanently. You can forward both types of logs in realtime to multiple destinations via the syslog-ng protocol. For more information, see "Log forwarding."

Access and audit logs include information like the following.

Access logs

• Full web server logs for both browser and API access
• Full logs for access to repository data over Git, HTTPS, and SSH protocols
• Administrative access logs over HTTPS and SSH

Audit logs

• User logins, password resets, 2FA requests, email setting changes, and changes to authorized applications and APIs
• Site administrator actions, such as unlocking user accounts and repositories
• Repository push events, access grants, transfers, and renames
• Organization membership changes, including team creation and destruction

Open-Source-Abhängigkeiten für GitHub Enterprise Server

Eine vollständige Liste der Abhängigkeiten in der Version Ihrer Appliance von GitHub Enterprise Server sowie die Lizenz jedes Projekts finden Sie unter http(s)://HOSTNAME/site/credits.

Tarballs mit einer vollständigen Liste der Abhängigkeiten und verknüpften Metadaten sind auf Ihrer Appliance verfügbar:

• Plattformübergreifende Abhängigkeiten finden Sie unter /usr/local/share/enterprise/dependencies-<GHE version>-base.tar.gz.
• Plattformspezifische Abhängigkeiten finden Sie unter /usr/local/share/enterprise/dependencies-<GHE version>-<platform>.tar.gz.

Tarballs sind mit einer vollständigen Liste der Abhängigkeiten und Metadaten auch unter https://enterprise.github.com/releases/<version>/download.html verfügbar.

Weiterführende Informationen

• „Eine Testversion von GitHub Enterprise Server einrichten“
• "Setting up a GitHub Enterprise Server instance"