Feature · Crew

Security Studio

Track security signals, test detection rules and prepare explanations.

Last changed

Generated from commit 0ab68bc ·

How it works

No guide is written for this feature yet. The operations and screens below come straight from the code. The help center has the guides that exist.

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • getSecurityStudio

    AdminNo API tokens

    Gets the security studio.

    Types: Record<string, never> returns SecurityStudioSnapshot

  • runSecurityBacktest

    AdminNo API tokens

    Runs the security backtest.

    Types: { labId: SecurityLabId | 'all' } returns SecurityBacktest

  • createSecurityDraft

    AdminNo API tokens

    Creates a security draft.

    Types: { labId: SecurityLabId } returns SecurityDraft

  • updateSecurityFinding

    AdminNo API tokens

    Updates the security finding.

    Types: { id: string; revision: number; status: SecurityFindingStatus; note: string } returns SecurityFinding

  • updateSecurityDraft

    AdminNo API tokens

    Updates the security draft.

    Types: { id: string; revision: number; title: string; status: 'draft' | 'ready'; posts: SecurityPost[] } returns SecurityDraft

  • ingestSecurityEvents

    Admin

    Ingests security events.

    Types: { source: string; events: SecurityEventInput[] } returns { accepted: number; duplicates: number; findings: number }

Screens

Generated from code at commit 0ab68bc ·

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.