Vigicap
Connector
WALLIX Bastion
API credential, entered client by client.
Privileged access management (French vendor): session gateway, secrets vault, approval workflow, session recording. Two distinct readings. Does administration actually go THROUGH the bastion? An authorization that allows the target's password to be RETRIEVED lets an administrator connect directly, outside the bastion — the dedicated path becomes optional. And is it traceable? A session authorization with no recording is an administrator acting without a record. This connector never asks for the vault's secrets.
01
What to create in the tool
The access is created in WALLIX Bastion, 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 le Bastion : créez un utilisateur dédié en lecture seule, puis une clé d'API pour lui (Configuration > Utilisateurs). Saisissez ici l'adresse du Bastion, le nom de cet utilisateur et la clé. N'accordez pas le droit « Credential recovery » : ce connecteur ne lit aucun secret du coffre.
Minimum role
Utilisateur Bastion dédié en lecture seule, avec une clé d'API (et non le mot de passe d'un administrateur humain) : la clé se révoque seule. Toutes les lectures de ce connecteur sont des GET sur les autorisations, les équipements et les comptes. CE CONNECTEUR N'ENVOIE JAMAIS le paramètre `passwords=true` sur /api/accounts, qui ferait renvoyer en clair les mots de passe et les clés privées des comptes à privilèges. Le profil de l'utilisateur n'a donc aucun besoin du droit « Credential recovery », et il ne faut pas le lui accorder.
Taken from the vendor's own role model, and checked before publication.
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.
- Adresse du BastionURL
L'adresse de votre appliance WALLIX Bastion. Une adresse privée (RFC1918) est le cas normal.
https://bastion.interne.example
- Utilisateur d'API
Le nom de l'utilisateur Bastion auquel la clé appartient.
- Clé d'APIsecret
La clé générée dans le Bastion pour cet utilisateur. Préférez-la au mot de passe d'un administrateur : elle se révoque indépendamment.
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 2 objectives of the ANSSI ReCyF framework. It PROPOSES them: a level only counts once a consultant has confirmed it.
- #11 Maîtrise de l'administration des systèmes d'informationControl of the administration of the information systems
- #19 Administration des systèmes d'information depuis des ressources dédiéesAdministration of the information systems from dedicated 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.