log saladCUSTOMER DOCUMENTATION / CONSOLE V1
Build understanding.
Then connect evidence.
Guides for evaluators, developers and agents working inside a private, customer-controlled security environment.
Private evaluation, not a hosted SaaS signup.
The website and synthetic demo do not connect to your data. The separate console is an implemented candidate with integration verification pending. Inference is disabled. Cloud containment and external ticket delivery are not implemented.
Start here
Start a private evaluationA short path from private console access to a reviewable investigation.Authentication & authorityCookie sessions, same-origin mutations and narrowly scoped source tokens.Onboard sources & ingestAttach existing acquisition safely; distinguish configuration from provider verification.Schemas & evidencePartial OCSF mapping, native provenance and evidence-backed narratives.Query hot & historical evidenceTyped filters now; SQL preview is not unrestricted SQL execution.Detections, signals & casesStrict stateless rules, durable alerts and honest ATT&CK context.Workflows & human approvalBound exact local case changes to a reviewed digest and revision.Private deployment & retentionBYOS is an ownership boundary, not a compliance badge.Costs & operational statusKeep estimates, observations, bills and missing information separate.Troubleshooting & reconciliationRecover by inspecting persisted state, not by assuming the last request failed.Capabilities & limitsA versioned public boundary for implementers, evaluators and agents.API referenceActual paths, security requirements and typed schemas from console-v1.
Agent entry points
llms.txt · OpenAPI 3.1 · Capabilities and limits · Local search index
Machine clients should read the limits and authority boundaries before acting. A source token is not a general agent credential. Model output never authorizes an action.