VigicapConnector
Google Workspace
OAuth connection, authorised by the client in their own tenant.
Reads two-factor authentication coverage and the domain's account hygiene.
01
What to create in the tool
The access is created in Google Workspace, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.
Where to generate it
The exact path through the vendor's console is not documented here to date. We are not describing it from memory: the vendor's own documentation is the authority.
Minimum role
The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.
02
What to enter in Vigicap
The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.
The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.
This connector asks for no additional field.
03
Per-client routing
The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.
04
What it does, and what it does not do
ReCyF objectives it pre-fills
A reading feeds one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.
- #10 Gestion des identités et des accès des utilisateurs aux systèmes d'informationManagement of user identities and of user access to the information systems
Read-only
The reads are read-only: Vigicap writes nothing into the tool while reading it.
What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.
Scopes requested
The exact scopes requested at authorisation, named as the vendor names them.
- openid
- https://www.googleapis.com/auth/admin.directory.user.readonly
Verification
This connector has been run end to end against a real instance of the tool, not merely tested against a mock.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.