Programma pilota: 30 % di sconto nel primo anno. Posti limitati. Vedi le condizioni

Fissa un primo colloquio
Complass – Navigate compliance Complass – Navigate compliance

Collegato direttamente

GitHub: Chi può fare cosa nel codice? Complass lo sa.

Membri, team e permessi per le verifiche degli accessi, più impostazioni come l’obbligo di 2FA come evidenza.

Come funziona

  1. Create a GitHub app

    You create your own GitHub app with read permissions only and install it on your organisation.

  2. Check the preview

    The first run is a preview. Nothing is stored until you adopt it.

  3. Sync regularly

    After that Complass syncs daily, or every six hours or weekly if you prefer.

  4. Review access

    Members and rights appear in access reviews. You match people once by hand, because Complass reads no e-mail addresses.

Which data is exchanged

Data flow between Complass and GitHub
DirectionDataAvviso
GitHub → ComplassMembers with role and 2FA status, outside collaborators, teams with members and repositoriesOwners count as privileged.
GitHub → Complass (optional)Direct repository rights from write access upwardsAt most 2,000 repositories per run.
GitHub → Complass (evidence)Only switches and figures, such as required 2FA, number of owners, branch protection, secret scanning, push protection and DependabotNo alert contents and no secrets.
Complass → GitHubNothingComplass refuses apps with write or admin permissions.
Not readCode, issues, pull requests, secrets, e-mail addresses, real names, avatars and the audit logComplass does not request this data at all.

Setup

  • Your own GitHub app, installed on exactly one organisation on GitHub.com.
  • Read permissions on members, organisation administration and repository metadata. Repository administration only for direct rights and settings such as branch protection.
  • In Complass you enter the organisation, app ID, installation ID and the app's private key.
  • Administrators with the right for API, webhooks and integrations can set it up.

Sicurezza e protezione dei dati

  • Read only: Complass checks the app's permissions on every test and refuses write and admin permissions.
  • The private key is stored encrypted in Complass. Each run creates a token valid for at most one hour, in memory only.
  • Complass only connects to the GitHub API.
  • Only active repositories count for evidence. With the topic "complass-ignore" you leave a repository out.

Domande frequenti

Does it work with GitHub Enterprise Server?

No, only with organisations on GitHub.com.

We have several organisations. What now?

One connection covers exactly one organisation.

Can Complass read our code?

No. The app needs no permission on contents, and Complass requests neither code nor issues or pull requests.

More connections

Which packages include the connection to GitHub, see the package overview. See the packages

I nomi di prodotti e i marchi citati appartengono ai rispettivi titolari. Non esiste alcuna partnership, certificazione o raccomandazione da parte dei titolari. GitHub è un marchio di GitHub, Inc.

Provate Complass con i vostri dati

Create voi stessi il vostro accesso di prova, se volete con un progetto di esempio per ogni quadro normativo. Se preferite vedere prima Complass, richiedete una demo.