Skip to content

Add cloud threat-emulation skill and emulation-run harness - #68

Draft
terrancedejesus wants to merge 1 commit into
elastic:mainfrom
terrancedejesus:add-cloud-threat-emulation-skill
Draft

Add cloud threat-emulation skill and emulation-run harness#68
terrancedejesus wants to merge 1 commit into
elastic:mainfrom
terrancedejesus:add-cloud-threat-emulation-skill

Conversation

@terrancedejesus

@terrancedejesus terrancedejesus commented Aug 24, 2026

Copy link
Copy Markdown

co-authored with @bryans3c

Summary

  • Adds a JSON-only emulation-run MCP tool (no React UI) that is the fail-closed state machine for one cloud threat-emulation engagement: plan, digest-bound approve, record, finalize. It does not call cloud APIs.
  • Ships the cloud-threat-emulation skill (methodology + progressive-disclosure references). Coverage is scored with existing threat-hunt and manage-rules.
  • Registers the tool via registerTrackedTool, gitignores on-disk emulation-runs/, and documents the JSON-only exception in architecture and contributing docs.

Test plan

  • npx vitest run src/tools/emulation-run.test.ts src/tools/emulation-run-state.test.ts src/tools/tracked-app-tool.test.ts
  • Integration test still lists emulation-run in tools/list
  • New chat with this branch’s MCP: emulation-run appears; set_plan returns stop=true and a plan_digest
  • Confirm emulation-runs/ is not committed (gitignored)
  • Confirm no cluster credentials, tenant IDs, or lab run folders are in the diff

Keep phase order and digest-bound approval in a JSON-only MCP tool so the agent is not the run. The skill teaches the methodology and scores coverage with existing hunt and rules tools.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant