Connector

Google Security Command Center

API credential, entered client by client.

Reads a Google Cloud organisation's active misconfiguration findings (Security Health Analytics), by severity. Only findings of class «misconfiguration» are counted: a detected threat and an unencrypted disk must not move the same level. A zero total can also mean Security Health Analytics is not enabled (SCC Standard), so it is never presented as good configuration. Requires SCC Premium or Enterprise. Objective 18 is reserved for essential entities: for a client classified as an important entity this reading is recorded in the history but changes no level, since the referential does not apply that objective to them.

What to create in the tool

The access is created in Google Security Command Center, 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

Dans Google Cloud : IAM et administration > Comptes de service > Créer, puis Clés > Ajouter une clé (JSON). Attribuez ensuite roles/securitycenter.findingsViewer AU NIVEAU DE L'ORGANISATION — un rôle posé sur un projet ne donne pas accès à SCC.

Minimum role

Rôle « Security Center Findings Viewer » (roles/securitycenter.findingsViewer) au niveau de l'organisation, porté par un compte de service dédié. Aucune écriture n'est effectuée.

Taken from the vendor's own role model, and checked before publication.

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.

ID d'organisation
Numérique, visible dans le sélecteur d'organisation de la console Google Cloud.
E-mail du compte de service
Champ client_email du fichier JSON de clé.
Clé privéesecret
Champ private_key du fichier JSON, collé tel quel — les \n sont acceptés.

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.

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.

#18 Sécurisation de la configuration des ressources des systèmes d'informationSecuring the configuration of information systems resources

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.

Verification

The API is public and documented, but it can only be reached with a paid subscription the vendor issues no trial for: there is no instance we can obtain to run it against. This is not “not yet done” — it would take a customer lending us their tenant.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.