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.
01
What to create in the tool
The access is created in Google Security Command Center, not in Vigicap.
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.
02
What to enter in Vigicap
- 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.
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
ISO 27001 controls covered
This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.
- 5.12 Classification of information
- 5.14 Information transfer
- 5.34 Privacy and protection of PII
- 8.1 User endpoint devices
- 8.7 Protection against malware
- 8.9 Configuration management
- 8.12 Data leakage prevention
- 8.19 Installation of software on operational systems
- 8.24 Use of cryptography
- 8.27 Secure system architecture and engineering principles
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
Vigicap writes nothing to the tool while reading.
How Vigicap handles your credentials.
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.