Home / Help centre / Integrations & API
Integrations & API
What is the cloud key vault integration used for?
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.
| Field | What to enter |
|---|---|
| Name | A label you will recognise, such as Prod vault SP |
| Tenant ID | The tenant identifier from your cloud account |
| Client ID | The application identifier of the service principal |
| Client secret | The 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.
Related questions
- How do I connect my cloud key vault?
- How do I check that my key vault connection works?
- My key vault connection won't verify. What should I check?
- Why can't I see my saved token or key any more?
- How does Cyberlop store my credentials and tokens?
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.