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

Connector

Pi-hole

API credential, entered client by client.

Self-hosted network DNS blocker (Pi-hole v6), used by MSPs to filter advertising/malicious domains at the client's network level. Vigicap reads the size of the blocklist (gravity) and the volume of filtered DNS queries to evaluate the ReCyF objective « Sécurisation de la messagerie et du web (filtrage DNS) ». This connector only covers DNS filtering of web traffic, not e-mail security, which caps the automatic proposal at level 3.

01

What to create in the tool

The access is created in Pi-hole, 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

In Pi-hole (v6 only — the v5 ?auth= token API is not compatible): Settings > API (or Web interface / API depending on the version), "App password" section — generate it and copy it immediately, it is shown only once.

Minimum role

The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.

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.

  • App passwordsecret

    Settings > API > App password — dedicated to the API, distinct from the full web password.

    Mot de passe d'application Pi-hole

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.

  • #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code

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

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

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