docs(1-getting-started): add opinionated MSSP walkthrough#221
Draft
maximelb wants to merge 2 commits into
Draft
Conversation
Adds a long-form, end-to-end walkthrough for service providers starting on LimaCharlie: control-org bootstrap, customer-org template, telemetry (sensors + adapters + sleeper), starter detections, LCQL hunting, alerting/Cases, outputs, multi-tenant access, AI agents, IaC with Git Sync, cost guardrails, an onboarding playbook, and a 12-month maturity ladder. Wired into the Getting Started nav, linked from the index, and cross-linked from the existing MSSP use-case page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…d POC guide Comprehensive expansion of the MSSP walkthrough so a new MSSP customer can run their entire POC off this single page. Now 20 parts / ~2,660 lines / +2,066 net insertions, covering: - Concrete worked example (Northwind Security with ACME, Globex, Initech) - Real install commands for Windows (EXE / MSI / PowerShell), Linux (deb / binary), macOS, with the actual self-contained PowerShell script to send customer IT - Full adapter YAML for Microsoft 365, Okta, AWS CloudTrail (S3 + SQS) with hive secret references throughout - Adapter deployment options (As-a-Service, on-prem, Windows service, Linux systemd unit template) - Day-1 telemetry smoke test per source (what to do, what to look for) - Detection pattern catalogue with 8 production-ready rules covering simple, nested, stateful (with child / with events), behavioral (suppression-as-state), threat-feed-driven, and sensor-variable patterns - Top-10 EDR event-type reference, common detection-writing pitfalls - Full Cases extension config YAML (severity, SLA, auto-grouping, retention), case lifecycle CLI cookbook, tailored ingestion mode walkthrough - Concrete output configs for S3 (with IAM policy), syslog/TLS, BigQuery (with custom_transform), webhook (with HMAC verification explanation), Slack with step-by-step provisioning - 15 ready-to-use MSSP-baseline LCQL queries committed as a saved-query library - Template strings quick reference - Five-OG access model from mssp-demo (Administrators / Analysts / Viewers / Auditors / Break-Glass active-responders), root-account pattern, permission groupings for common automation use cases, full onboarding bash script, quarterly access verification script - New: sensor commands and live-response section — top commands by category, cross-fleet selectors, Reliable Tasking for offline sensors, isolation automation pattern - New: forensics & IR extensions — Artifact, Dumper, Velociraptor, Atomic Red Team, YARA Manager, Payload Manager - New: threat-intel & lookups — auto-refreshing public feeds (AlienVault, Tor, Talos), lookup-driven detections, MSSP-managed soc-blocked-ips/hashes/domains pattern that turns one investigation into ongoing protection - AI: full IaC YAML for triage and investigator agents from the lean-soc reference, responder workflow snippets, sample reporter daily report, cost-guardrail checklist, Bring-Your-Own provider note - IaC: mssp-demo repo layout (concrete file tree, all.yaml, customer main.yaml with global+local include pattern, real installation_keys.yaml, real outputs.yaml), bootstrap-from-existing-org flow, Git Sync deploy-key setup, CI workflow example - New: end-to-end 10-step smoke test with expected results - Billing math (per-source GB/day estimates by company size), three cost rules of thumb, output billing per stream All 100+ relative cross-references resolve to real files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Comprehensive, opinionated walkthrough that a new MSSP can run their entire LimaCharlie POC off —
docs/1-getting-started/mssp-walkthrough.md, 20 parts, ~2,660 lines, designed to be self-contained (the reader rarely needs to leave the page for the day-1 work).Wired into the Getting Started nav (right after Core Concepts), linked from
docs/1-getting-started/index.md, and cross-linked from the existinguse-cases/mssp-msp-mdr.mdoverview as the practical companion.Article structure
Uses a fictional MSSP (Northwind Security) with three sample customers (ACME, Globex, Initech) to keep examples concrete throughout.
soc-blocked-{ips,hashes,domains}pattern that turns one investigation into ongoing protectionall.yaml, customermain.yamlwith global+local includes, realinstallation_keys.yamlandoutputs.yamlexamples, secrets-as-references, bootstrap-from-existing-org, dry-run gating, Git Sync deploy-key setup commands, CI workflow exampleStats
Test plan
use-cases/mssp-msp-mdr.mdtip box works🤖 Generated with Claude Code