Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Integrations & API

Integrations & API

What is the cloud key vault integration used for?

Quick answer

The cloud key vault integration lets Cyberlop read scan credentials from your own vault instead of you typing them into profiles. You save a service principal once, with a name, tenant ID, client ID and client secret, then verify it. The client secret is encrypted and never shown again.

The short version

Some scans need a login. Passwords and API keys for those logins are sensitive. Many teams already keep them in a cloud key vault, with access rules, rotation and an audit trail that their security team trusts and reviews. The integration lets Cyberlop read those secrets from the vault when it needs them.

How it works in Cyberlop

Open Integrations and choose the third tab, the one for your cloud key vault, which holds a service principal: the identity Cyberlop uses when it reads secrets from the vault for a scan.

FieldWhat to enter
NameA label you will recognise, such as Prod vault SP
Tenant IDThe tenant identifier from your cloud account
Client IDThe application identifier of the service principal
Client secretThe secret of that service principal

Press Verify to test the connection, then Save. If you come back later, the secret field is blank. That is normal, because Cyberlop encrypts it at rest and never shows it again.

The API has a matching call, POST /api/keyvault/verify. It checks the vault connection and the named secrets, and needs the profile:manage_credentials permission.

Why use it

It keeps secrets where they already live. When a team rotates a password in the vault on a fixed schedule, Cyberlop can follow that change without anyone retyping it.

  • Secrets stay in one place.
  • Rotation is easy.
  • Fewer people need to see the raw values, which also makes access reviews and audits much simpler to answer.

What to do next

Follow how to connect the key vault, then how to verify it. If the check fails, read why Verify fails. The pages we reviewed do not show how a profile points at a named secret. Ask us through the contact page if you need that step. Good secrets management starts with keeping values out of forms.

Full tutorial

How to connect a cloud key vault to Cyberlop

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Wiring it into your pipeline?

Share what you are building and we will help you set up the right token, profile and job.