Skip to main content
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.

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

  • 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

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.