Vigicap
Connector
Qualys CSAM
API credential, entered client by client.
Connects the Qualys inventory (CyberSecurity Asset Management / Global AssetView) to read how many assets are recorded. This connector does NOT read vulnerabilities, and that is an API limit rather than an omission: Qualys's JSON API exposes no vulnerability count at all, and the surface that does answers in XML. Machines Qualys never discovered stay invisible from this source.
01
What to create in the tool
The access is created in Qualys CSAM, 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
Créez dans Qualys un compte de service avec un rôle en LECTURE SEULE : contrairement aux autres connecteurs, la gateway Qualys n'accepte pas de clé d'API et exige un identifiant et un mot de passe de compte. Adresse de l'instance : l'URL de la gateway de VOTRE plateforme (ex : https://gateway.qg1.apps.qualys.com) — un compte n'existe que sur une plateforme.
Minimum role
The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.
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.
- Identifiant
Compte de service Qualys, en lecture seule de préférence.
- Mot de passesecret
Mot de passe du compte ci-dessus. La gateway Qualys ne propose pas d'authentification par clé d'API.
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
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
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.