Security in Git

Who may do what with your repositories, which credentials reach them, and what is recorded.

Last updated 18 November 2026View as Markdown

IAM

Permissions are per repository: a policy can name one repository or all of them. A repository's resource name is rn:ews::<organization id>:git:repository/<repository id>; Git is regionless, so the region segment is empty. rn:ews::<organization id>:git:* covers every repository.

{
  "Version": "2024-01-01",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["git:GetRepository", "git:PullRepository", "git:PushRepository"],
      "Resource": "rn:ews::org-EXAMPLE1234:git:repository/5d6c2a1e-7b3f-4c8d-9e0a-1b2c3d4e5f60"
    }
  ]
}

Some actions stand apart so a policy can deny them while allowing the rest:

  • git:PublishRepository: making a repository public, at creation, import or later.
  • git:ConfigurePushMirror: sending code to a remote outside Deutsche Cloud.
  • git:BypassSecretProtection: pushing past secret scanning with a reason.
  • git:PushProtectedTag: creating, moving or deleting a protected tag.

The repository's Settings → Access grants one of three levels, each a bundle of these actions:

Level Grants
Read see the repository, its pull requests, issues and releases, and clone it
Push Read, plus push, open, review and merge pull requests, use the merge queue, publish releases, post commit statuses, upload SARIF
Administer Push, plus settings, branch and tag protection, security alerts, secret scanning bypass, deploy keys, webhooks, publishing and deleting
ActionAccessWhat it allows
git:GetServiceStatusReadView Git service status
git:ListRepositoriesReadList Git repositories
git:GetRepositoryReadView a repository
git:CreateRepositoryWriteCreate a new repository
git:UpdateRepositoryWrite · destructiveUpdate repository settings
git:StopMirroringWrite · destructiveTurn a mirror into an ordinary repository: syncing from its source ends and pushes become possible
git:ConfigurePushMirrorWrite · destructiveSet, remove or trigger a push mirror: every push is copied to a remote outside Deutsche Cloud
git:DeleteRepositoryWrite · destructiveDelete a repository
git:PublishRepositoryWrite · destructiveMake a repository public: anyone can clone and read it without credentials
git:PullRepositoryRead · sensitiveClone or pull from a repository
git:PushRepositoryWrite · destructivePush commits to a repository
git:AdminRepositoryWrite · destructiveManage repository settings, access, and branch protection
git:ManageBranchProtectionWrite · destructiveCreate and update branch protection rules
git:ListDeployKeysReadList deploy keys for a repository
git:CreateDeployKeyWriteAdd a deploy key to a repository
git:DeleteDeployKeyWrite · destructiveRemove a deploy key from a repository
git:ListGithubInstallationsReadList the organization's GitHub App installations and the GitHub repositories they cover
git:ConnectGithubWriteBind a GitHub App installation to the organization (checked with the installer's GitHub sign-in), mirror its repositories, push them back to GitHub through it, or disconnect it
git:ListWebhooksRead · sensitiveList webhooks for a repository
git:CreateWebhookWriteCreate a webhook for a repository
git:UpdateWebhookWrite · destructiveUpdate a repository webhook
git:DeleteWebhookWrite · destructiveDelete a repository webhook
git:CreateAccessTokenWriteCreate a personal Git HTTPS access token
git:ListAccessTokensReadList personal Git HTTPS access tokens
git:DeleteAccessTokenWrite · destructiveRevoke a personal Git HTTPS access token
git:RegisterSshKeyWriteRegister an SSH key for Git access
git:DeleteSshKeyWrite · destructiveRemove an SSH key from Git access
git:ListPullRequestsReadList pull requests in a repository
git:GetPullRequestReadView a pull request
git:CreatePullRequestWriteOpen a new pull request
git:UpdatePullRequestWrite · destructiveUpdate pull request title, body, or target branch
git:MergePullRequestWriteMerge a pull request
git:ClosePullRequestWrite · destructiveClose a pull request without merging
git:ReviewPullRequestWriteSubmit a review on a pull request
git:MarkFilesViewedWriteMark a pull request's files viewed (or not) for yourself
git:GetMergeQueueReadView a branch merge queue and its history
git:AddToMergeQueueWriteAdd a pull request to a merge queue ("merge when ready")
git:RemoveFromMergeQueueWrite · destructiveRemove a pull request from a merge queue
git:ListReleasesReadList and view a repository’s releases
git:CreateReleaseWriteCreate a release (and its tag, if new); publishing starts `on: release` workflows
git:UpdateReleaseWriteEdit or publish a release
git:DeleteReleaseWrite · destructiveDelete a release (its tag stays)
git:ListIssuesReadList and read a repository's issues, their comments and its labels
git:CreateIssueWriteOpen an issue
git:UpdateIssueWriteEdit, close or reopen an issue; set its labels and assignees, or a pull request’s labels
git:CommentOnIssueWriteComment on an issue
git:ManageLabelsWriteCreate, change and delete a repository's labels
git:PushProtectedTagWriteCreate, move or delete a tag matching a tag protection rule (in addition to PushRepository)
git:BypassSecretProtectionWritePush a commit containing a detected secret anyway, with a reason (`git push -o secret_scanning.bypass=…`)
git:ListSecurityAlertsReadView secret scanning, dependency and code scanning alerts and the security overview
git:UpdateSecurityAlertWriteResolve, dismiss or reopen a security alert
git:UploadCodeScanningResultsWriteUpload a SARIF file of code scanning results for a commit
git:ListCommitStatusesReadRead the statuses external tools reported on a commit
git:CreateCommitStatusWriteReport a status (pending, success, failure, error) on a commit

Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.

Credentials

Credential Reaches Notes
Access token HTTPS and the API, for the repositories its owner may reach Shown once; optional expiry (1 to 365 days); can be narrowed to some repositories and to read only; lastUsedAt kept
Account SSH key SSH, for the repositories its owner may reach No passwords over SSH
Deploy key SSH, one repository Read-only unless created with write access; can never push a protected tag

A token never does more than its owner's own policies allow.

Network exposure

  • Repositories are served over HTTPS and SSH on the Git host. Verify the server's SSH host key fingerprint by hand before the first connection; it is shown as Server fingerprint under Account → SSH keys.
  • A public repository can be cloned anonymously; anonymous requests are rate-limited per address and answered 429 with Retry-After past the limit. See Public repositories.
  • Webhooks reach only public https:// addresses and follow no redirects; imports fetch only from https:// sources.

Audit

Every write is authorized and recorded in the audit log, including turning secret push protection off for a repository. A push past secret scanning is also recorded as an alert, with the person's name and reason. Webhook deliveries of a webhook with a secret are signed with HMAC-SHA256 in X-EWS-Signature-256.

Did this page help you?