Connector

ConnectSecure

A single agency-level credential, for the whole portfolio.

Vulnerability management, external attack-surface scanning and CIS assessment for MSPs (formerly CyberCNS). A single key reads every one of your client companies. The vulnerability-management level rests on the AGE of critical and high findings rather than on their count: ten found yesterday and two sitting a month old do not describe the same situation. Out-of-support products are reported separately — no patch will resolve them.

What to create in the tool

The access is created in ConnectSecure, 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 ConnectSecure : Global > Settings > Users > menu Action (trois points) > API Key, puis copiez le Client ID et le Client Secret. Il vous faut aussi le nom de votre tenant et l'adresse de votre pod (par exemple https://pod401.myconnectsecure.com) : ConnectSecure n'expose aucun moyen de découvrir le pod, et une adresse de pod erronée ne lit rien sans le dire.

Minimum role

Clé d'API créée sur un utilisateur dédié (Global > Settings > Users > Action > API Key). Toutes les lectures de ce connecteur sont des GET sous le préfixe /r/ (lecture seule côté API). Le client_id et le client_secret n'expirent pas, mais le jeton d'accès qu'ils produisent est limité à deux heures par ConnectSecure : chaque synchronisation s'authentifie pour elle-même. La clé hérite des droits de l'utilisateur qui l'a créée — créez-la sur un compte en lecture seule, et non sur un compte d'administration globale.

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 du pod
Chaque client ConnectSecure est hébergé sur un pod numéroté. L'adresse figure dans celle de votre console.
https://pod401.myconnectsecure.com
Nom du tenant
Le nom de votre tenant ConnectSecure, tel qu'il apparaît à la connexion.
Client ID
Client Secretsecret

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.

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.