Skip to main content
Back to the connector catalogue

Connector

Cert Spotter

API credential, entered client by client.

Monitoring of the public Certificate Transparency logs. Vigicap queries the client's domain and reads how many public DNS names a certificate covers, how many expire within 30 days and how many already have. It is the only source that observes a client's exposed surface from outside, querying nothing they run — which is how it surfaces forgotten subdomains. This connector proposes no ReCyF level: a public certificate attests that a name was published, not that an asset exists.

01

What to create in the tool

The access is created in Cert Spotter, 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 un jeton sur https://sslmate.com/account/api_credentials (une offre gratuite existe, avec un quota de requêtes). Saisissez le domaine racine du client : les sous-domaines sont inclus automatiquement.

Minimum role

Un jeton d'API Cert Spotter en lecture (SSLMate > API keys). Ce connecteur n'appelle que GET /v1/issuances. Aucun accès au système du client n'est nécessaire : les journaux de transparence des certificats sont publics, et le jeton ne sert qu'à interroger SSLMate.

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.

  • Jeton d'API Cert Spottersecret

    Créé dans votre compte SSLMate, en lecture seule.

  • Domaine du client

    Domaine racine ; les sous-domaines sont inclus automatiquement.

    exemple.fr

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

This connector feeds no ReCyF objective, and that is not a gap: it does not measure a client's posture.

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.