Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ Automation orchestrator is the workflow engine in AAP for visual, multi-step aut
|---|---|---|
| [RHEL CVE Remediation](cve-remediation/) | **Active** | AI triage via Lightspeed MCP → auto-patch dev, approve prod, or investigate with Mattermost report |
| [Multi-OS Cloud Patching](multi-os-cloud-patching/) | **Active** | Playbook orchestration - RHEL and Windows on AWS with snapshot rollback (playbooks from product-demos) |
| [Zero-Day Response: PHP2Shell](zero-day-response/) | **Active** | Zero-day before the fix - evidence and look-back, AI reads the advisory, policy gate and test host, owners approve, patch only where a fix exists |
| [Disk Utilization & Remediation](disk-utilization/) | **Active** | Check disk usage → switch on % → continue, cleanup, EBS expand, or fallback → Mattermost notify |
| [Intelligent Cert Lifecycle](cert-lifecycle/) | **Active** | AI agent picks PEM vs keystore renewal; operator approves; AAP renews and validates |
| [Service State Routing](service-health/) | **Active** | Check service → switch on state → log OK, start, restart, or install |
Expand Down Expand Up @@ -50,6 +51,7 @@ See the [demo marketplace](https://ansible-tmm.github.io/aap-orchestrator-demos/
| [proactive-assessment/](proactive-assessment/) | Scheduled scan-before-expiry |
| [cve-remediation/](cve-remediation/) | Intelligent CVE patching with Lightspeed MCP |
| [multi-os-cloud-patching/](multi-os-cloud-patching/) | Multi-OS cloud patching with snapshot rollback (product-demos playbooks) |
| [zero-day-response/](zero-day-response/) | Zero-day response - contain before the fix, patch where it exists, prove it |
| [disk-utilization/](disk-utilization/) | Proportional disk remediation with switch routing |
| [event-driven-xsos-rca/](event-driven-xsos-rca/) | SQS → EDA → xSOS RCA for unknown issues |
| [ai-incident-triage/](ai-incident-triage/) | AI-assisted incident response |
Expand Down
1 change: 1 addition & 0 deletions _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ exclude:
- kernel-compliance/
- novel-incident-remediation/
- cicd-pipeline/
- zero-day-response/
- collections/
- shared/
- README.md
Expand Down
3 changes: 3 additions & 0 deletions _data/ao_glossary.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,15 @@ category_order:
marketplace_filters:
- agentic
- switch
- conditional
- converge
- approval
- webhook_trigger
- manual_trigger
- aap_job_template
- aap_job_template_dynamic
- script
- http_request
- mcp_integration
- servicenow_mcp

Expand Down
28 changes: 28 additions & 0 deletions _data/demo_pages.yml
Original file line number Diff line number Diff line change
Expand Up @@ -414,3 +414,31 @@ novel-incident-remediation:
- Fire a service_down incident to walk the impact report and service recovery path
- Fire an unknown incident to show the AI agent activating, enriching the SNOW ticket, and generating the remediation plan
- Compare the unknown path approval step - show the AI reasoning in the SNOW ticket before approving

zero-day-response:
description: A zero-day is being exploited before a fix exists. Two automation orchestrator workflows run the response a board asks for - KNOW (evidence, classification, log look-back), CONTAIN (AI-extracted interim controls, policy gate, test, two named owner approvals, production verify, board update), then FIX and PROVE (per-stream fix availability from the Red Hat Security Data API, test and rolling patch, controls removed only where the fix is verified, re-scan, case kept open while lanes remain). Import both workflows with the two Download JSON buttons - KNOW + CONTAIN first, then FIX + PROVE. This is a historical replay - the advisories are recorded snapshots, the estate is a lab, "AcmeCMS" is a simulated vendor, and there is no exploit code.
ao_building_blocks:
- manual_trigger
- agentic
- http_request
- conditional
- converge
- approval
- aap_job_template
one_liner: AI reads. Owners decide. AAP acts. Automation orchestrator holds every lane.
why_it_matters:
- The gap between first exploitation and the fix is where the risk is; the demo shows a governed way to act inside it instead of waiting for a patch.
- Classification, fix status and verification are reviewed, deterministic automation. AI reads advisories and explains - it cannot change a priority or skip a gate.
- Every AI answer is validated by a deterministic check step, every AI-proposed control by a policy gate and a test host, and every production change by an owner approval.
- Interim controls come off only where the fix is verified running, so there is no forgotten workaround - and the case stays open, with owners, for the lanes that are not fixed.
related_table:
heading: Vulnerability demos in this catalog
headers: [Demo, Type, Focus]
rows:
- ["Zero-Day Response", "AI-assisted", "Exploited before the fix → contain with owner approvals → patch where a fix exists → prove"]
- ["RHEL CVE Remediation", "AI-assisted", "CVE alert → AI triage → auto-patch, approve, or investigate"]
- ["Patch Severity Routing", "Rule-based", "Switch on scan severity → patch now, schedule, batch, or compliant"]
demo_ideas:
- Run KNOW + CONTAIN end to end and stop on the security approval panel - the AI summary, the tested change and Red Hat's residual-risk sentence on one screen
- Show the board update's "not claimed" list - control verified is not safe
- Run FIX + PROVE to show the fix arriving unevenly - patched lanes, a vendor appliance still contained, an unknown asset still escalated
52 changes: 52 additions & 0 deletions _data/demo_playbooks.yml
Original file line number Diff line number Diff line change
Expand Up @@ -482,3 +482,55 @@ novel-incident-remediation:
path: novel-incident-remediation/aap/playbooks/incident_log_and_report.yml
description: Logs the unrecognized incident details and posts a work note to the ServiceNow ticket flagging it for manual triage.
runs_on: localhost (ServiceNow API)

zero-day-response:
status: active
items:
- name: infra_provision_aws.yml
path: zero-day-response/playbooks/infra_provision_aws.yml
description: Creates (or, with role_action deprovision, removes) the dedicated VPC and six tagged RHEL instances.
runs_on: AWS (localhost)
- name: estate_configure.yml
path: zero-day-response/playbooks/estate_configure.yml
description: Builds or resets the estate to its vulnerable baseline.
runs_on: RHEL hosts
- name: p2s_scan.yml
path: zero-day-response/playbooks/p2s_scan.yml
description: KNOW — evidence from every PHP asset, then the deterministic classification.
runs_on: RHEL hosts
- name: p2s_lookback.yml
path: zero-day-response/playbooks/p2s_lookback.yml
description: KNOW — log look-back, were we already hit?
runs_on: RHEL hosts
- name: p2s_ai_check.yml
path: zero-day-response/playbooks/p2s_ai_check.yml
description: Parses and validates every AI answer against its schema.
runs_on: localhost
- name: p2s_spec_check.yml
path: zero-day-response/playbooks/p2s_spec_check.yml
description: Policy gate — is the AI-extracted control spec inside the reviewed envelope?
runs_on: localhost
- name: p2s_controls.yml
path: zero-day-response/playbooks/p2s_controls.yml
description: CONTAIN — applies and verifies the interim controls, test then production.
runs_on: RHEL hosts
- name: p2s_fix_availability.yml
path: zero-day-response/playbooks/p2s_fix_availability.yml
description: FIX — decides per stream on the Red Hat API answers the workflow recorded.
runs_on: localhost
- name: p2s_patch.yml
path: zero-day-response/playbooks/p2s_patch.yml
description: FIX — patch and verify, test then rolling production with rollback.
runs_on: RHEL hosts
- name: p2s_standdown.yml
path: zero-day-response/playbooks/p2s_standdown.yml
description: Removes interim controls only where the fix is verified.
runs_on: RHEL hosts
- name: p2s_case_record.yml
path: zero-day-response/playbooks/p2s_case_record.yml
description: PROVE — records the AI-drafted update on the case; refuses an empty draft.
runs_on: localhost
- name: p2s_independent_check.yml
path: zero-day-response/playbooks/p2s_independent_check.yml
description: Independent read of live estate state and business transactions, outside the response roles.
runs_on: RHEL hosts
41 changes: 41 additions & 0 deletions _data/demos.yml
Original file line number Diff line number Diff line change
Expand Up @@ -757,3 +757,44 @@
F --> G@{ img: "__ASSET__/assets/icons/launch-aap-job-template.png", label: "Notify Operators", pos: "b", h: 96, constraint: "on" }
classDef noBorder fill:transparent,stroke:transparent
class A,B,C,D,E,F,G noBorder

- slug: zero-day-response
title: Zero-Day Response
subtitle: KNOW, CONTAIN, FIX, PROVE - PHP2Shell on RHEL and AWS
category: patching
status: active
featured: false
uses_ai: true
tmm_created: true
tags:
- Task agent
- Approval
- Conditional
- AWS
thumbnail:
gradient: "linear-gradient(135deg, #4a1a1a 0%, #1a0d0d 50%, #2a1a3a 100%)"
icon: "🚨"
blurb: A zero-day lands before the fix. Evidence and look-back in parallel, AI reads the vendor advisory, a policy gate and test host prove the interim controls, owners approve, and the fix is applied only where it exists. Two workflows, 12 playbooks and a six-instance AWS estate.
stats:
workflows: 2
playbooks: 12
setup_minutes: 25
url: /demos/zero-day-response/
github_path: zero-day-response/
github_doc: zero-day-response/README.md
workflow_json: zero-day-response/ao/flow-a-know-contain.json
workflow_json_label: KNOW + CONTAIN
workflow_json_more:
- path: zero-day-response/ao/flow-b-fix-prove.json
label: FIX + PROVE
workflow_mermaid: |
flowchart LR
A@{ img: "__ASSET__/assets/icons/manual-trigger.png", label: "Advisory received", pos: "b", h: 96, constraint: "on" } --> B@{ img: "__ASSET__/assets/icons/launch-aap-job-template.png", label: "KNOW: Evidence + look-back", pos: "b", h: 96, constraint: "on" }
B --> C@{ img: "__ASSET__/assets/icons/task-agent.png", label: "AI: Explain for humans", pos: "b", h: 96, constraint: "on" }
C --> D@{ img: "__ASSET__/assets/icons/task-agent.png", label: "AI: Read the advisory", pos: "b", h: 96, constraint: "on" }
D --> E@{ img: "__ASSET__/assets/icons/launch-aap-job-template.png", label: "Policy gate + test", pos: "b", h: 96, constraint: "on" }
E --> F@{ img: "__ASSET__/assets/icons/approval-node.png", label: "Security + service owner", pos: "b", h: 96, constraint: "on" }
F -->|Approved| G@{ img: "__ASSET__/assets/icons/launch-aap-job-template.png", label: "PROD: Contain + verify", pos: "b", h: 96, constraint: "on" }
G --> H@{ img: "__ASSET__/assets/icons/task-agent.png", label: "AI: Board update", pos: "b", h: 96, constraint: "on" }
classDef noBorder fill:transparent,stroke:transparent
class A,B,C,D,E,F,G,H noBorder
19 changes: 16 additions & 3 deletions _includes/demo-cta.html
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
{% comment %}
Demo page actions - GitHub doc link and workflow JSON download.
Usage: {% include demo-cta.html demo=demo %}
Demos with more than one workflow can set workflow_json_label (names the primary JSON)
and workflow_json_more: a list of { path, label } entries, each rendered as another download button.
{% endcomment %}
{% assign d = include.demo %}
{% assign gh_base = "https://github.com/" | append: site.repository | append: "/blob/main/" %}
Expand All @@ -16,9 +18,19 @@
<a href="{{ gh_base }}{{ d.setup_guide }}" class="btn btn-secondary" target="_blank" rel="noopener">Setup guide</a>
{% endif %}
{% if d.status == "active" and d.workflow_json %}
{% assign json_filename = d.workflow_json | split: '/' | last %}
{% assign json_entries = "" | split: "" %}
{% assign json_primary = d.workflow_json | append: "|" | append: d.workflow_json_label | split: "|" %}
{% assign json_entries = json_entries | push: json_primary %}
{% for extra in d.workflow_json_more %}
{% assign json_extra = extra.path | append: "|" | append: extra.label | split: "|" %}
{% assign json_entries = json_entries | push: json_extra %}
{% endfor %}
{% for entry in json_entries %}
{% assign json_path = entry[0] %}
{% assign json_label = entry[1] %}
{% assign json_filename = json_path | split: '/' | last %}
<a
href="{{ raw_base }}{{ d.workflow_json }}"
href="{{ raw_base }}{{ json_path }}"
class="btn btn-secondary btn-download"
data-download-json
data-filename="{{ json_filename }}"
Expand All @@ -27,6 +39,7 @@
<svg class="btn-download__icon" viewBox="0 0 24 24" aria-hidden="true">
<path fill="currentColor" d="M12 3a1 1 0 0 1 1 1v9.586l2.293-2.293a1 1 0 0 1 1.414 1.414l-4 4a1 1 0 0 1-1.414 0l-4-4a1 1 0 1 1 1.414-1.414L11 13.586V4a1 1 0 0 1 1-1zm-7 14a1 1 0 0 1 1 1v1h12v-1a1 1 0 1 1 2 0v2a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1v-2a1 1 0 0 1 1-1z"/>
</svg>
Download JSON
Download JSON{% if json_label and json_label != "" %}: {{ json_label }}{% endif %}
</a>
{% endfor %}
{% endif %}
4 changes: 4 additions & 0 deletions demos/zero-day-response/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
---
layout: demo-detail
demo_slug: zero-day-response
---
Loading