All projects
Security engineering / evidence workbench

Alchemist
Sentinel.

An incident story you can inspect. Follow a shell event and a blocked outbound connection without confusing observations with intent.

Source repository
Scenario
SYN-001 / fixed replay
Namespace
demo-checkout
Pod
checkout-api-replay
Disposition
Needs human review

01 / Evidence timeline

Fixture timestamps · UTC · not live telemetry

This synthetic application is expected to run /app/server, not an interactive shell. All records below are authored fixtures, not collected security evidence.

  1. E01
    Synthetic workload inventory

    Workload context established

    The replay inventory associates checkout-api-replay with the demo-checkout namespace.

    Inspect E01 fixture record
    {
      "namespace": "demo-checkout",
      "pod": "checkout-api-replay",
      "expectedProcess": "/app/server"
    }
  2. E02
    Synthetic runtime event

    Unexpected shell observed

    A /bin/sh process appears in the application container, outside the declared replay baseline.

    Inspect E02 fixture record
    {
      "namespace": "demo-checkout",
      "pod": "checkout-api-replay",
      "type": "process",
      "executable": "/bin/sh",
      "parent": "/app/server"
    }
  3. E03
    Synthetic network-policy verdict

    Outbound connection blocked

    The fixture records a denied TCP connection to documentation-only address 203.0.113.42:443 from the same pod.

    Inspect E03 fixture record
    {
      "namespace": "demo-checkout",
      "pod": "checkout-api-replay",
      "type": "connection",
      "destination": "203.0.113.42:443",
      "verdict": "DENY"
    }

02 / Deterministic findings

Local fixture rules only. Exact field matches, scoped to this namespace and pod; no model, risk score or autonomous verdict.

Observed / F01

Shell outside the declared baseline

Exact executable match: /bin/sh. This rule does not establish who launched it or why.

Inspect evidence E02
Observed / F02

Denied outbound connection

Exact verdict match: DENY. The fixture does not show a successful connection or data transfer.

Inspect evidence E03

03 / Hypotheses, not conclusions

Authored investigation prompts, not AI output. Temporal proximity in one pod does not prove causation.

Unverified / needs corroboration

Possible unauthorized command execution

The shell could indicate compromise, but an approved debugging session is also possible. Review access and exec audit records before attributing intent.

Unverified / needs corroboration

Possible attempted external communication

The denied flow could be related to the shell or an unrelated application action. Process-to-flow attribution and destination context are missing; exfiltration is not established.

04 / Review-only remediation

Proposal, not execution

Preserve → corroborate → approve

No apply, isolate, delete or restart controls exist in this demo. These are review suggestions for a real investigation, not instructions executed against infrastructure.

  1. Preserve runtime, network and access records; establish provenance and retention before considering changes.
  2. Check approved debugging activity and correlate process identity with the denied flow. Confirm policy behavior independently.
  3. If corroborated, have an authorized responder review containment and workload hardening, with impact assessment, explicit approval and a rollback plan.
  4. Verify any separately approved change and document the outcome. This replay cannot demonstrate containment or recovery.

Scope: one synthetic pod, two exact-match findings, no completeness guarantee. The linked repository is a separate implementation; this page does not attest to its runtime behavior or live integrations.