Connector
Cisco Meraki
A single agency-level credential, for the whole portfolio.
Cloud-managed network (MX firewalls, MS switches, MR access points). A single key reads all of the organisations your account has access to.
01
What to create in the tool
The access is created in Cisco Meraki, not in Vigicap.
Where to generate it
Dashboard Meraki > profil > API access > Generate new API key. L'accès API doit aussi être activé sur chaque organisation (Organization > Settings).
Minimum role
Clé d'API Meraki en lecture seule (rôle « read-only » sur l'organisation).
Taken from the vendor's own role model, and checked before publication.
02
What to enter in Vigicap
- Clé d'APIsecret
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
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
- 8.1 User endpoint devices
- 8.8 Management of technical vulnerabilities
- 8.19 Installation of software on operational systems
- 8.29 Security testing in development and acceptance
- 8.32 Change management
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
Vigicap writes nothing to the tool while reading.
How Vigicap handles your credentials.
Verification
This connector has been run end to end against a real instance of the tool, not merely tested against a mock.