Connector
Datto RMM
API credential, entered client by client.
RMM platform (formerly CentraStage) used by MSPs to monitor a client's fleet. Vigicap reads — read-only — the device inventory, their online/offline status, antivirus status and patch status, for the ReCyF objectives « Inventaire des actifs », « Gestion des correctifs » and « Protection contre les codes malveillants ». Assets with no agent and third-party application patches are not covered.
01
What to create in the tool
The access is created in Datto RMM, not in Vigicap.
Where to generate it
Datto RMM → Setup > Global Settings > Access Control: enable "Enable API Access", then Setup > Users > your user > "Generate API Keys". The URL to enter is the "API URL" shown on the user's record (e.g. https://pinotage-api.centrastage.net). Enter the client's site UID to limit reads to its fleet: otherwise the API keys give access to the entire account.
Minimum role
Générez la paire de clés depuis un compte dont le niveau de sécurité API n'accorde que les droits en lecture « Setup > Global Settings: View », « Sites > Sites: View » et « Sites > Devices: View » — le minimum que Datto documente pour les trois appels de ce connecteur.
Taken from the vendor's own role model, and checked before publication.
02
What to enter in Vigicap
- API keysecret
Setup > Users > user > Generate API Keys ("API Key").
- API secret keysecret
Generated together with the API key ("API Secret Key") — shown only once.
- Client site UIDoptional
Optional but recommended — limits reads to the site (client) in question. Leave blank to read the entire account.
ex. 7f1c0f8e-2b34-4c9a-9f1e-0a2b3c4d5e6f
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
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
- 8.1 User endpoint devices
- 8.7 Protection against malware
- 8.8 Management of technical vulnerabilities
- 8.19 Installation of software on operational systems
- 8.23 Web filtering
- 8.29 Security testing in development and acceptance
- 8.32 Change management
ReCyF objectives it pre-fills
A reading feeds 3 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
Read-only
Vigicap writes nothing to the tool while reading.
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 device inventory of one site — the siteUid field scopes the read to a single client, not to your whole portfolio.
- For each device: its online or offline state, antivirus status and patch status.
- Three ReCyF objectives: asset inventory, patch management, protection against malicious code.
What it does not read
Agentless assets and third-party application patches, like any RMM. And, unlike NinjaOne, no encryption state: there is no fourth objective here because there is no fourth reading.
What these signals do not prove
- "Offline" and "gone" look very much alike from a console. A device powered off for six months still counts in the inventory until somebody removes it.
- An antivirus status reported by the RMM is the agent's statement about a third-party product. The antivirus vendor's own console remains the more direct source.
- Does the connector read all my clients at once?
- No. The siteUid limits it to one site, so to one client. It is a per-client connector, not an agency-level one.
- Is it read-only?
- Entirely. It writes nothing and reads no ticket state back.