Skip to main content
Vigicap
Try it
Back to the connector catalogue

Connector

AWS Security Hub

API credential, entered client by client.

Reads the AWS account's conformance to the hardening standards subscribed in Security Hub (CIS AWS Foundations, AWS Foundational Security Best Practices): which standards are active and how many controls fail, by severity. Security Hub's overall score is displayed but feeds no objective — it aggregates controls belonging to six domains at once. One connection reads one region. 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 AWS Security Hub, 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 AWS : IAM > Utilisateurs > Informations d'identification de sécurité > Créer une clé d'accès, sur un utilisateur portant la politique AWSSecurityHubReadOnlyAccess. La région doit être celle où Security Hub est activé — une connexion lit une seule région.

Minimum role

Politique gérée AWSSecurityHubReadOnlyAccess, sur un utilisateur ou un rôle 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

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.

  • Région AWS

    Par exemple eu-west-3. Security Hub est régional : les constats restent dans la région qui les a produits.

  • Access Key ID

    Commence par AKIA pour une clé d'utilisateur.

  • Secret Access Keysecret
  • Session Token (optionnel)secret

    Uniquement pour des identifiants temporaires STS. Laissez vide pour une clé permanente.

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.

  • #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.