Connector

Tactical RMM

API credential, entered client by client.

Self-hosted open-source RMM. Vigicap reads the list of deployed agents (status, Windows patches pending approval) to evaluate the ReCyF objectives « Recensement des systèmes d'information » and « Maîtrise des systèmes d'information ». Only Windows patches are covered: Linux/macOS agents are not counted in the patch ratio.

Beta

What to create in the tool

The access is created in Tactical RMM, 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 Tactical RMM : Settings > Global Settings > API Keys > Add. Choisissez un utilisateur dédié à droits limités — la clé hérite de son rôle. Attention : l'API n'est pleinement fonctionnelle que si l'instance présente un certificat TLS valide (certificat Let's Encrypt wildcard) ; un certificat auto-signé sera refusé par Vigicap (aucune option pour désactiver la vérification TLS, par sécurité).

Minimum role

Une clé API est émise POUR un utilisateur et hérite de son rôle — créez un utilisateur dédié avec un rôle en lecture seule (Settings > User Management > Roles) avant de générer sa clé (Settings > Global Settings > API Keys).

Taken from the vendor's own role model, and checked before publication.

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.

Clé APIsecret
Settings > Global Settings > API Keys > Add — associée à un utilisateur dédié, idéalement en lecture seule.
Clé API Tactical RMM

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.

What it does, and what it does not do

ReCyF objectives it pre-fills

A reading feeds 2 objectives of the ANSSI ReCyF framework. It PROPOSES them: a level only counts once a consultant has confirmed it.

#1 Recensement des systèmes d'informationInventory of information systems
#5 Maîtrise des systèmes d'informationControl of 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. It is marked “Beta” everywhere it appears.

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