Skip to main content
Back to the connector catalogue

Connector

Snipe-IT

API credential, entered client by client.

Open-source IT asset management tool, used by MSPs to record their clients' hardware. Vigicap reads the total number of registered hardware assets to evaluate the ReCyF objective « Inventaire des actifs ».

01

What to create in the tool

The access is created in Snipe-IT, not in Vigicap.

Where to generate it

Generate an API token in Snipe-IT: user menu (top right) > Manage API Keys > Create New Token — the token is shown only once, copy it immediately.

Minimum role

Utilisateur non-admin dédié, rattaché à un groupe de permissions (Admin > Groups) n'accordant que la consultation des actifs — le jeton personnel hérite exactement des droits de cet utilisateur, sans droit de création, de modification ni de suppression.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

  • API tokensecret

    Account > API > Create New Token.

    Jeton API Snipe-IT

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
  • 8.1 User endpoint devices

ReCyF objectives it pre-fills

A reading feeds one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.

  • #1 Recensement des systèmes d'informationInventory of 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.