Skip to content

Add Zero-Day Response demo (PHP2Shell): KNOW, CONTAIN, FIX, PROVE - #12

Merged
IPvSean merged 5 commits into
ansible-tmm:mainfrom
oatakan:add-zero-day-response
Nov 11, 2026
Merged

IPvSean merged 5 commits into
ansible-tmm:mainfrom
oatakan:add-zero-day-response

Conversation

@oatakan

@oatakan oatakan commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

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 reads main).

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's
setup, 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 CHECK step and was reviewed against the run's evidence
by 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. CHECK validates shape only, so keep a human reading the words (see "Using a different
model" in the README).

What a reviewer needs. AWS (the demo provisions its own six-instance estate in us-east-1, tagged
p2s-demo=true, and removes it with role_action: deprovision) and a LiteMaaS model. No Mattermost, no cloud stack.

Files. zero-day-response/ (two workflow exports with placeholder credentials, playbooks and roles, recorded
advisories 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.yml exclude and a row in both tables of the root README.md. bundle exec jekyll build is 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

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
@oatakan

oatakan commented Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

@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 _config.yml conflict with the CI/CD demo (both exclude entries kept); the site builds clean with the same warnings as main.

@IPvSean IPvSean left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

  1. 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.yml and _data/demo_pages.yml both changed on both sides — please refresh so we don’t land stale catalog wiring.

  2. Second workflow in the UI
    workflow_json only points at ao/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 expose ao/flow-b-fix-prove.json clearly on the detail page (not only in the README table).

  3. Filter discoverability (optional but nice)
    Detail ao_building_blocks includes http_request, conditional, and converge, but those keys are not in marketplace_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_ideas is 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=true is clear
  • Fake CVE IDs (CVE-2026-*) are OK given the historical-replay framing — keep that wording visible on the detail page
  • Honest note that CHECK validates 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.

oatakan and others added 2 commits November 10, 2026 20:18
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
@oatakan

oatakan commented Nov 10, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the review. Pushed:

  1. Merged latest main, with no conflicts and no change to the zero-day-response files.
  2. The detail page now has two download buttons, "Download JSON: KNOW + CONTAIN" and "Download JSON: FIX + PROVE", and the description says to import both, KNOW + CONTAIN first. It's done with two optional keys in demo-cta.html (workflow_json_label, workflow_json_more); other demos render as before.
  3. Added conditional, converge and http_request to the marketplace filters.

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 IPvSean left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-reviewed after your updates. Prior items look good:

  1. 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).
  2. Both workflows are importable via Download JSON: KNOW + CONTAIN and Download JSON: FIX + PROVE.
  3. Filter pills for conditional / converge / http_request are in place.
  4. 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).

@IPvSean
IPvSean merged commit cb7d945 into ansible-tmm:main Nov 11, 2026
IPvSean added a commit to oatakan/ansible-product-demos that referenced this pull request Nov 11, 2026
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>
@oatakan
oatakan deleted the add-zero-day-response branch November 11, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants