Skip to main content
Vigicap
Try it
Back to the connector catalogue

Connector

ThreatDown (Malwarebytes)

API credential, entered client by client.

Connects to the ThreatDown API (Nebula, formerly Malwarebytes) to automatically check how many of the client's workstations carry the ThreatDown agent, how many are in a « protected » state, and how many detections were reported over the last 30 days. Feeds the ReCyF objective « protection contre les codes malveillants ».

Beta

01

What to create in the tool

The access is created in ThreatDown (Malwarebytes), 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

In the Nebula console: Settings > APIs & Integrations > Add, to get a client_id / client_secret pair ("read" scope is enough). The account identifier (account_id) is on the same page. Instance address: https://api.threatdown.com

Minimum role

Couple client_id / client_secret de portée « read ».

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.

  • Client identifier (client_id)secret

    Created in Nebula > Settings > APIs & Integrations.

  • Client secret (client_secret)secret

    Shown only once when the OAuth2 application is created.

  • Account identifier (account_id)

    UUID of the Nebula account, sent in the "accountid" header the ThreatDown API requires.

    00000000-0000-0000-0000-000000000000

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.

  • #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code

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. It is marked “Beta” everywhere it appears.

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