Where to find them
The former Runtime Security API keys link redirects to Settings → API keys.
Keys created before this change keep working unchanged.
Create a key
1
Choose what it is for
Pick one purpose: Data Security, Runtime Security,
Endpoint, Shadow AI, or Entire platform. A purpose appears
only if your workspace licence covers it and you hold permissions for it.
2
Choose what it may do
Tick the narrowest set that works. Only permissions you hold are offered.
3
Set how long it lasts
Give the key an expiry. A key with an end date is one nobody has to remember.
4
Copy the secret
The key is shown once. If you miss it, rotate the key to issue a new one.
What each purpose offers
Endpoint and Shadow AI use the same permissions as Runtime Security. A key that
reads endpoint events can also read Runtime Security events, and a key that
manages endpoints can also change Runtime Security configuration. The
console states this beside each option.
Rotate and revoke
Rotate a key to issue a new secret before the old one stops working in your systems, then delete the old key. Deleting or disabling a key is instant and audit-logged, and later calls with it return401. Name each key after what
uses it, so it is obvious in the audit trail.
Keys that belong to an App
A Runtime Security key can be limited to one App, or to several. A key limited to one App needs no App ID in its requests. When that App is archived or deleted, every key limited to it alone is revoked in the same step, and each revocation is written to the audit trail. A key limited to several Apps keeps the others and loses only this one. Turning an App off does not touch its keys. See Apps.Use a key
Send the key in theX-API-Key header.

