Vigicap
Connector
NetBird
API credential, entered client by client.
Open-source WireGuard-based private network, self-hostable, used in place of a VPN concentrator. Vigicap reads how many devices are enrolled and connected, whether local accounts must present a second factor and whether sessions expire, to assess the ReCyF objective on securing remote access. Remote access that does not pass through NetBird is not visible from this source.
01
What to create in the tool
The access is created in NetBird, 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 le tableau de bord NetBird, ouvrez Team > Service Users, créez un utilisateur de service dédié à Vigicap, puis générez un jeton d'accès personnel depuis sa fiche. Le jeton n'est affiché qu'une fois. L'URL à saisir est celle de votre instance de management (par exemple https://netbird.exemple.fr) ; pour NetBird Cloud, utilisez https://api.netbird.io. L'instance doit présenter un certificat TLS valide et reconnu : Vigicap n'offre aucune option pour désactiver la vérification TLS.
Minimum role
Créez un utilisateur de service dédié (Team > Service Users) et générez-lui un jeton d'accès personnel. Ce connecteur n'appelle que des lectures (GET /api/accounts, /api/peers, /api/policies). NetBird ne publie pas d'énumération de ses rôles ni de portée par jeton : n'utilisez jamais le jeton d'un administrateur humain, et révoquez-le depuis la même page si la connexion est retiré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.
- Jeton d'accès personnelsecret
Jeton généré sur un utilisateur de service dédié (Team > Service Users). Jamais celui d'un administrateur humain.
nbp_…
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.
- #8 Sécurisation des accès distants aux systèmes d'informationSecuring remote access to the information systems
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 was written from the vendor's documented API and has not yet been run against a real instance.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.