Repository navigation
Add Zero-Day Response demo (PHP2Shell): KNOW, CONTAIN, FIX, PROVE - #12
Conversation
Co-Authored-By: Codex gpt-6.1-sol <noreply@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RDaQ1UYzj2bq8iJgo9m2o2
Resolves the _config.yml exclude conflict with the CI/CD pipeline demo by keeping both entries (cicd-pipeline/ and zero-day-response/). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RDaQ1UYzj2bq8iJgo9m2o2
|
@IPvSean since you reviewed the seed side (ansible/product-demos#389), could you review this one too? It's the dependency for #389. I merged main in to clear a |
IPvSean
left a comment
There was a problem hiding this comment.
Review
Strong demo — KNOW → CONTAIN → FIX → PROVE is clear, the AI CHECK gates are excellent, catalog hygiene looks right (featured: false, tmm_created: true, _config.yml exclude), and the “no exploit code / AcmeCMS is simulated” framing is solid. Lab story and README setup/run/teardown are presenter-grade.
Please address the items below before merge (product-demos seed depends on this landing on main).
Before merge
-
Rebase / merge latest
main
Branch is behind recent marketplace work (Lightwell rename, Arcade embed, origin filters, workflow icon CSS). GitHub shows mergeable, but_data/demos.ymland_data/demo_pages.ymlboth changed on both sides — please refresh so we don’t land stale catalog wiring. -
Second workflow in the UI
workflow_jsononly points atao/flow-a-know-contain.json. The detail-page Import workflow JSON CTA therefore only surfaces KNOW + CONTAIN. Please make FIX + PROVE obviously importable too — e.g. call it out next to the primary CTA / in page copy, or otherwise exposeao/flow-b-fix-prove.jsonclearly on the detail page (not only in the README table). -
Filter discoverability (optional but nice)
Detailao_building_blocksincludeshttp_request,conditional, andconverge, but those keys are not inmarketplace_filters, so marketplace pills won’t filter this demo by them. Consider adding the ones you care about to the filter row.
Non-blockers
demo_ideasis fine; we may trim those site-wide later- Short mermaid summary of the 26-step canvas is a good tradeoff
- AWS six-node estate is heavy but provision /
role_action: deprovision+p2s-demo=trueis clear - Fake CVE IDs (
CVE-2026-*) are OK given the historical-replay framing — keep that wording visible on the detail page - Honest note that
CHECKvalidates shape only (human still reads the words) is the right call
Once the rebase + dual-workflow discoverability are in, this looks good to merge ahead of the APD seed PR.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1ZJ6wTqhD8ht6azTfRUHo
…r pills
- demo-cta.html: optional workflow_json_label and workflow_json_more ({path, label}
list), each rendered as another Download JSON button. Demos without these keys
render exactly as before.
- Zero-Day Response: label the KNOW + CONTAIN download and add FIX + PROVE
(ao/flow-b-fix-prove.json) next to it.
- Detail page copy: import order, and the historical-replay framing (recorded
advisory snapshots, lab estate, simulated "AcmeCMS" vendor, no exploit code).
- marketplace_filters: add conditional, converge (also used by CI/CD and
Multi-OS patching) and http_request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C1ZJ6wTqhD8ht6azTfRUHo
|
Thanks for the review. Pushed:
The historical-replay wording is on the detail page now too. One correction: the CVE IDs are real (php-src advisories, Red Hat RHSB-2026-013); what's simulated is the "AcmeCMS" vendor and the lab estate. The site builds clean with the same warnings as main. |
Co-authored-by: Cursor <cursoragent@cursor.com>
IPvSean
left a comment
There was a problem hiding this comment.
Re-reviewed after your updates. Prior items look good:
- Rebased/merged main (I resolved the fresh conflicts from the OpenFlake / walkthrough / em-dash work that landed after your push, and pushed that merge to this branch).
- Both workflows are importable via Download JSON: KNOW + CONTAIN and Download JSON: FIX + PROVE.
- Filter pills for conditional / converge / http_request are in place.
- Historical-replay framing is on the detail page. Thanks for the CVE clarification - real advisories, simulated AcmeCMS/lab estate.
Approved. Safe to merge when you are ready (product-demos #389 can follow).
Add zero-day-response and zero-day-response-fix to demos.yml (twelve p2s-* job templates on the KNOW+CONTAIN slug) and document both workflows in the AO hub. Same seed shape as Multi-OS / CI/CD. Depends on ansible-tmm/aap-orchestrator-demos#12 landing on main first. Co-authored-by: Sean Cavanaugh <sean@cavanaugh.pro> Co-authored-by: Cursor <cursoragent@cursor.com>
What it shows. A zero-day exploited before the fix exists, run as two automation orchestrator workflows: KNOW +
CONTAIN (evidence and log look-back in parallel, deterministic classification, AI reads the recorded vendor
advisory, policy gate, test host, two owner approvals, production verify, board update) and FIX + PROVE
(per-CVE answers from the Red Hat Security Data API, test and rolling patch with rollback, interim controls removed
only where the fix is verified, re-scan, case kept open while lanes remain). AI reads, owners decide, AAP acts.
Status.
active. Seeded into APD by ansible/product-demos#389 (merge this one first: the seed readsmain).Preview (temporary, on the fork). https://oatakan.github.io/aap-orchestrator-demos/demos/zero-day-response/
Tested. On a Red Hat Demo Platform "Ansible Product Demos" environment (AAP 2.7, automation orchestrator 1.3.1,
LiteMaaS
qwen3-235b): AO uninstalled, reinstalled by APD's Install from the seed branch (with a test-only pointer to the fork), then the README'ssetup, run, reset and teardown steps followed as written. After the final AI wording changes, Install re-seeded the same
environment and both workflows ran green again: every AI answer passed its
CHECKstep and was reviewed against the run's evidenceby the coding agent running the test, and every approval went through the AO UI, clicked by a scripted browser.
AI wording. Live runs slipped more often than replays: earlier prompts failed review on several live runs, and only one
live pair has run since the last fix.
CHECKvalidates shape only, so keep a human reading the words (see "Using a differentmodel" in the README).
What a reviewer needs. AWS (the demo provisions its own six-instance estate in
us-east-1, taggedp2s-demo=true, and removes it withrole_action: deprovision) and a LiteMaaS model. No Mattermost, no cloud stack.Files.
zero-day-response/(two workflow exports with placeholder credentials, playbooks and roles, recordedadvisories with
SHA256SUMS, README), plus the catalog entries in_data/demos.yml,_data/demo_pages.yml,_data/demo_playbooks.yml,demos/zero-day-response/index.html, the_config.ymlexclude and a row in both tables of the rootREADME.md.bundle exec jekyll buildis clean.No exploit code: verification uses benign requests and business transactions. "AcmeCMS" is a simulated vendor.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RDaQ1UYzj2bq8iJgo9m2o2