Cybrary ForgeCYBRARY / FORGE
Back to SOAR Range

Integrations & Vault

Catalog → instance → credential → health. Secrets are write-only: the vault holds the value server-side and hands workflows a reference, so nothing here, in a run record, in an export or in the assistant's context can ever contain one.

Configured instances
Summit Search
schema 1.4.0

Search indexed telemetry, read notable events, and post enrichment back.

Endpoint
https://siem.range.internal/api
Environment
test
Credential reference
vault/siem-test
Supported auth
api-key, jwt

Operations

  • Run searchsiem.search
    read
    retry: safe
    search:read
  • Fetch notable eventsiem.get-notable
    read
    retry: safe
    notable:read
  • Append investigation notesiem.annotate
    mutating
    retry: keyed
    notable:write

Health ladder

Not tested yet. The ladder runs endpoint policy → DNS → TLS → auth → scope probe → API version → sample op → schema → rate limit → remediation.

Vault
Summit search key
active

vault/siem-test · api-key · vault_s…f2a

scopes: search:read, notable:read

Kestrel response app
active

vault/edr-test · oauth2 · vault_e…f2a

scopes: host:read, host:contain, file:quarantine

Northgate service principal
active

vault/identity-test · oauth2 · vault_i…f2a

scopes: user:read, audit:read

Parcel mail app
active

vault/email-test · oauth2 · vault_e…f2a

scopes: mail:read, mail:purge

Lookout Glass key
active

vault/threat-intel-test · api-key · vault_t…f2a

scopes: intel:read, sandbox:submit

Bastion Edge certificate
expired

vault/network-test · mtls · vault_n…f2a

scopes: policy:read, policy:write, dns:write

Meridian integration user
active

vault/itsm-test · basic · vault_i…f2a

scopes: ticket:read, ticket:write

Relay Deck bot
active

vault/chat-test · oauth2 · vault_c…f2a

scopes: chat:write, channel:create

Rotating a credential keeps its reference, so no published workflow needs an edit — which is exactly why nodes bind references and never values.