diff --git a/corpus/MANIFEST.yaml b/corpus/MANIFEST.yaml
index 975df1a..b76a35d 100644
--- a/corpus/MANIFEST.yaml
+++ b/corpus/MANIFEST.yaml
@@ -368,3 +368,27 @@ resources:
       benchmark reliability. Distinct from the Phase 1 report
       (llm-exploit-generation-1.0, linked only), which it follows rather than
       supersedes.
+
+  - id: genai-red-teaming-manual-1.0
+    title: "GenAI Red Teaming Manual: A Practical Guide for Adversarial Testing of Generative AI Models & Systems"
+    initiative: red-teaming
+    version: "1.0"
+    status: current
+    format: pdf
+    path: corpus/red-teaming/GenAI-Red-Teaming-Manual-v1.0.pdf
+    license: CC-BY-SA-4.0
+    source_url: https://genai.owasp.org/resource/genai-red-teaming-manual-version-1-0/
+    vendored_date: "2026-10-28"
+    published: "2026-10-01"
+    notes: >
+      Practical, phase-by-phase AI red-teaming methodology (144pp, October
+      2026): planning & scoping (stakeholders, frameworks, governance and
+      regulation, environment/access), reconnaissance & fingerprinting (public
+      artifacts, supply chain), surface mapping, exploitation & impact,
+      persistence & escalation, post-exploitation, evaluation & reporting, and
+      post-engagement remediation, plus when to run an AI red team exercise
+      and how testing maps to the GenAI system lifecycle. Appendix B has
+      worked red-teaming examples. Use for "how do I red team this GenAI
+      system / agent" and test-planning questions; pair with
+      red-teaming-vendor-evaluation-criteria-1.0 when choosing providers or
+      tooling.
diff --git a/corpus/red-teaming/GenAI-Red-Teaming-Manual-v1.0.pdf b/corpus/red-teaming/GenAI-Red-Teaming-Manual-v1.0.pdf
new file mode 100644
index 0000000..786babd
Binary files /dev/null and b/corpus/red-teaming/GenAI-Red-Teaming-Manual-v1.0.pdf differ