Vigicap
Connector
SonicWall NSM
A single agency-level credential, for the whole portfolio.
Central management for SonicWall firewalls (Network Security Manager), cloud or on-premise. NSM's tenants are your clients: one connection reads them all. The most useful reading is CONFIGURATION DRIFT — for each firewall NSM says whether the configuration held in the console was actually deployed. A console screenshot shows an intention; this connector says whether the appliance enforces it. Hardware lifecycle counts too: an appliance past end of support will receive no further updates.
01
What to create in the tool
The access is created in SonicWall NSM, 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
Il vous faut l'adresse de votre NSM (cloud, par exemple https://nsm-uswest.sonicwall.com, ou l'adresse de votre appliance NSM On-Prem), le numéro de série du tenant, et un code SSO obtenu depuis MySonicWall (GET https://api.mysonicwall.com/api/hgms/get-cloud-tenants donne le tenant et son numéro de série). Le jeton NSM qui en découle vit huit heures, avec une coupure au bout de quinze minutes d'inactivité.
Minimum role
Utilisateur NSM dédié en lecture seule, et un code SSO obtenu depuis MySonicWall pour ce tenant. Toutes les lectures de ce connecteur sont des GET. IMPORTANT : ne saisissez PAS ici votre clé d'API MySonicWall — ce connecteur n'en a pas besoin et ne doit pas la détenir, car c'est la clé qui permet de commander et de réaffecter des licences. Seuls le code SSO (à durée de vie limitée) et le numéro de série du tenant sont demandés.
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.
- Adresse de NSMURL
L'hôte régional de NSM Cloud, ou l'adresse de votre appliance NSM On-Prem. Les deux éditions sont acceptées.
https://nsm-uswest.sonicwall.com
- Numéro de série du tenant
Le numéro de série du tenant MySonicWall. Obtenu via GET https://api.mysonicwall.com/api/hgms/get-cloud-tenants.
- Code SSO MySonicWallsecret
Le jeton SSO émis par MySonicWall pour ce tenant. Ce n'est PAS votre clé d'API MySonicWall, qui ne doit pas être saisie ici.
03
Per-client routing
The credential itself is not repeated: one, entered once at agency level, covers the whole portfolio — the difference you feel with forty clients rather than four.
04
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.
- #5 Maîtrise des systèmes d'informationControl of the information systems
- #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 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.