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"
}An incident story you can inspect. Follow a shell event and a blocked outbound connection without confusing observations with intent.
Source repositoryFixture 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.
The replay inventory associates checkout-api-replay with the demo-checkout namespace.
{
"namespace": "demo-checkout",
"pod": "checkout-api-replay",
"expectedProcess": "/app/server"
}A /bin/sh process appears in the application container, outside the declared replay baseline.
{
"namespace": "demo-checkout",
"pod": "checkout-api-replay",
"type": "process",
"executable": "/bin/sh",
"parent": "/app/server"
}The fixture records a denied TCP connection to documentation-only address 203.0.113.42:443 from the same pod.
{
"namespace": "demo-checkout",
"pod": "checkout-api-replay",
"type": "connection",
"destination": "203.0.113.42:443",
"verdict": "DENY"
}Local fixture rules only. Exact field matches, scoped to this namespace and pod; no model, risk score or autonomous verdict.
Exact executable match: /bin/sh. This rule does not establish who launched it or why.
Inspect evidence E02Exact verdict match: DENY. The fixture does not show a successful connection or data transfer.
Inspect evidence E03Authored investigation prompts, not AI output. Temporal proximity in one pod does not prove causation.
The shell could indicate compromise, but an approved debugging session is also possible. Review access and exec audit records before attributing intent.
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.
Proposal, not execution
No apply, isolate, delete or restart controls exist in this demo. These are review suggestions for a real investigation, not instructions executed against infrastructure.
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.