Connector

Jamf Pro

API credential, entered client by client.

Apple device management (macOS, iOS, iPadOS). Encryption is read from the DETAILED STATE rather than the boolean flag: a Mac with an encrypted boot volume and an unencrypted data volume reports “FileVault enabled” while holding data in the clear, and only “all encrypted” counts as protected. This connector NEVER reads the endpoint that returns the FileVault recovery key. Jamf distinguishes “disabled” from “not collected”, and so does this reading — one is a finding about the client, the other about the inventory.

What to create in the tool

The access is created in Jamf Pro, 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

Dans Jamf Pro : Settings > API roles and clients > créez un rôle avec le seul privilège « Read Computers », puis un client d'API portant ce rôle. Notez le Client ID et le Client Secret. L'adresse est celle de votre instance (par exemple https://votreorg.jamfcloud.com).

Minimum role

Client d'API Jamf Pro (Settings > API roles and clients) avec un rôle contenant UNIQUEMENT « Read Computers ». Toutes les lectures de ce connecteur sont des GET sur l'inventaire. N'ACCORDEZ PAS le privilège « View Disk Encryption Recovery Key » : ce connecteur ne lit jamais l'endpoint qui renvoie la clé de récupération FileVault, et n'a donc aucun besoin de ce droit. L'état du chiffrement est lu dans la section DISK_ENCRYPTION de l'inventaire, qui ne contient aucune clé.

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

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 l'instance Jamf ProURL
Jamf Cloud ou une installation sur site : les deux fonctionnent.
https://votreorg.jamfcloud.com
Client ID
Client Secretsecret

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.

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

The API is public and documented, but it can only be reached with a paid subscription the vendor issues no trial for: there is no instance we can obtain to run it against. This is not “not yet done” — it would take a customer lending us their tenant.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.