Connector

NinjaOne

API credential, entered client by client.

RMM platform used by MSPs to monitor a client's fleet. Vigicap performs a read-only read (scope « monitoring ») of the device inventory, the system patch status, the antivirus status and the BitLocker volume encryption status, for the ReCyF objectives « Inventaire des actifs », « Gestion des correctifs », « Protection contre les codes malveillants » and « Chiffrement ». Assets with no agent and third-party application patches are not covered.

Beta

What to create in the tool

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

NinjaOne → Administration → Apps → API: create a "Client Credentials" application with the monitoring scope (read-only). The base URL is that of your region (e.g. https://eu.ninjarmm.com, https://app.ninjarmm.com, https://oc.ninjarmm.com). Enter the client's organisation ID to limit reads to its fleet.

Minimum role

Application « Client Credentials » avec le seul scope monitoring (lecture seule), limitée à l'organisation du client.

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.

Client ID
ID of the NinjaOne API application (Administration → Apps → API).
Client Secretsecret
Secret of the NinjaOne API application — shown only once at creation.
Client organisation IDoptional
Optional but recommended — limits reads to this client's fleet (NinjaOne "org=" filter). Leave blank to read the entire fleet the application can access.
ex. 42

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.

These fields are filled in client by client: they say which PSA account the ticket must land under. A wrong value does not fail the push — it succeeds against someone else, which is why Vigicap checks them the moment you type them.

Ticket form ID
NinjaOne ticket form ID to use.
e.g. 1

What it does, and what it does not do

ReCyF objectives it pre-fills

A reading feeds 4 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
#9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
#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 goes out to the tool

This connector WRITES: it creates a ticket from an action in the plan.

What comes back

The state of an already-created ticket comes back: its status, its closing date, its last activity. A closed ticket becomes a PROPOSAL a consultant confirms — never an action closed of its own accord. An agency that closes its own ticket must not be able to mark its own homework in the document an auditor reads.

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.