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

Connector

Microsoft Defender for Cloud

API credential, entered client by client.

Reads an Azure subscription's conformance to the hardening standards assigned to it (Microsoft Cloud Security Benchmark, CIS, ISO 27001…): passed, failed and skipped controls, standard by standard. Skipped controls are shown separately and excluded from the rate, because they are how a conformance rate becomes flattering. The Secure Score is displayed but feeds no objective. One connection reads one subscription. 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 Microsoft Defender for Cloud, 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 Azure : Microsoft Entra ID > Inscriptions d'applications > Nouvelle inscription, puis Certificats et secrets > Nouveau secret client. Attribuez ensuite le rôle « Security Reader » à ce principal sur l'abonnement (Abonnements > Contrôle d'accès IAM).

Minimum role

Rôle intégré « Security Reader » (Lecteur de sécurité) sur l'abonnement, porté par un principal 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

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.

  • Tenant ID (Directory ID)

    GUID visible sur la page d'aperçu de Microsoft Entra ID.

  • Subscription ID

    GUID de l'abonnement à lire. Une connexion = un abonnement.

  • Application (client) ID
  • Secret clientsecret

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.