KSKS Security Research
Learning map / Session 3 / Scenes 05–13

ORCHESTRATOR 02 · CAPABILITY FLOWS

Specialists should disagreethrough evidence.

See how intake routes to document, architecture, compliance, detection, and cloud-posture specialists without losing ownership or evidence.

SentinelCSPMdocument buildersecurity architecture
Learning guide
Level
Applied
Reading time
13 min
Presentation
Session 3
Progress
2 of 5

01 · Mental model

Each capability has a distinct graph and definition of done

A document builder owns document structure and assembly, not every specialist decision. A security architect may request compliance interpretation or detection evidence. Sentinel work needs KQL schema and behavior checks. CSPM work reasons across subscriptions, connectors, recommendations, policy, and ownership.

The orchestrator lets these workflows diverge while preserving a common intake contract, artifact envelope, evidence record, policy checks, and final review boundary.

02 · Visual explanation

01Intakescope + constraints
02Doc builderHLD / LLD / plan
03Security reviewfindings + threats
04Sentinel / CSPMdomain evidence
05Delivery packvalidated artifacts
Intake fans out; artifacts convergeSpecialists may call one another through the orchestrator, but every handoff remains typed and attributable.

03 · Compare and decide

Different domains need different proof

Decision lensCapabilityRequired evidence
Document builderComplete structure and consistent terminologySource-linked decisions and resolved placeholders
Security architectTrust boundaries and abuse pathsFindings with impact, evidence, and remediation
SentinelData source and KQL semanticsSchema, fixtures, detection behavior, deployment scope
CSPMCloud hierarchy and posture controlsConnector, policy, recommendation, ownership, and rollout model

04 · Cybersecurity example

A Sentinel design disagreement

The architect recommends broad telemetry while the delivery planner flags ingestion cost and ownership gaps.

01

Both specialists return evidence-linked artifacts.

02

The orchestrator identifies the conflict by shared decision ID.

03

A human selects scope and records rationale.

04

The document builder renders the accepted position consistently.

Outcome: Disagreement becomes a reviewable decision instead of being averaged into ambiguous prose.

05 · What to remember

The 60-second recall

01

Specialists need domain-specific evidence and tests.

02

The document builder assembles accepted decisions; it does not silently invent them.

03

Conflicts should be explicit artifacts with accountable resolution.

Teach-back prompt: Explain this concept to a teammate using the diagram, then name one failure mode and the control that stops it.

06 · Questions people ask

FAQ

Prefer routing through a shared control boundary so identity, scope, artifact contracts, budgets, and lineage remain consistent.

07 · Primary sources

Continue with authoritative guidance