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.
01
What to create in the tool
The access is created in NinjaOne, not in Vigicap.
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.
02
What to enter in Vigicap
- 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
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.
These fields are filled in client by client: they say which account in the ticketing tool 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
04
What it does, and what it does not do
ISO 27001 controls covered
This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.
- 5.9 Inventory of information and other associated assets
- 5.10 Acceptable use of information and other associated assets
- 5.11 Return of assets
- 5.12 Classification of information
- 5.14 Information transfer
- 5.34 Privacy and protection of PII
- 8.1 User endpoint devices
- 8.7 Protection against malware
- 8.8 Management of technical vulnerabilities
- 8.9 Configuration management
- 8.12 Data leakage prevention
- 8.19 Installation of software on operational systems
- 8.23 Web filtering
- 8.24 Use of cryptography
- 8.27 Secure system architecture and engineering principles
- 8.29 Security testing in development and acceptance
- 8.32 Change management
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
Vigicap writes nothing to the tool while reading.
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.
How Vigicap handles your credentials.
Verification
This connector was written from the vendor's documented API and has not yet been run against a real instance.
What this connector reads, exactly
- The client's device inventory, read-only, under the monitoring scope.
- System patch state, antivirus state, and BitLocker volume encryption.
- It is the broadest RMM connector in this list: it feeds four ReCyF objectives — asset inventory, patch management, protection against malicious code, and encryption.
What it does not read
Agentless assets and third-party application patches. Both absences matter: an estate where half the machines have no agent reads as a compliant estate half the size, and a machine perfectly patched at the system level can carry a vulnerable browser or PDF reader this source cannot see.
What these signals do not prove
- BitLocker encryption is read per volume. A machine whose system volume is encrypted and whose data disk is not is not an encrypted machine.
- A patch state of "up to date" is relative to the RMM's catalogue. It does not cover what that catalogue ignores — see third-party application patches above.
- Why does this connector feed four objectives when other RMMs feed fewer?
- Because it reads four distinct things where another reads two or three. The difference comes from what the source exposes, not from a setting on our side.
- Does it write into NinjaOne?
- It can file tickets there and read their state back. The inventory and posture reads change nothing.