Corrections
14 corrections were made on 19 Nov 2026, each listed below with the old value and the new value. A correction is any change to a fact, quotation, number or date after publication. The same day, 33 pages were merged into others and now answer with a permanent redirect. Report an error to the editor address.
Corrections log, newest first
| Date | Page | Old value | New value |
|---|---|---|---|
| 19 Nov 2026 | AI agent autonomy levels | Snoozing a finding was rated rollout 1, total 8, able to reach L5 after evidence, on the reasoning that a snoozed finding returns on its date. | Rollout 2, total 9, level L4: a snoozed exploitable finding stays hidden until its date. Two of the eight actions can reach L5, four stay at L4 and two stay with a person. |
| 19 Nov 2026 | Build vs buy | Vendors per job: 27 for triage, 15 for code fixes, 11 for disclosure response; 38 vendors in all. | 28, 16 and 10; 39 vendors in all, 69 listings, as in the use-case data. |
| 19 Nov 2026 | Method | The checklist was described as 18 questions quoting 16 pages; the source list held two CISA alerts and no New Zealand NCSC page. | 17 questions in ten pages (the downloadable data file still holds 20 rows, three of them for pages that were merged), quoting 15 pages; the source list matches the data. |
| 19 Nov 2026 | About | The scope line gave 38 vendors and 83 published agents. | 39 vendors, 85 published agents and 69 listings, as in the use-case data and the method page. |
| 19 Nov 2026 | Glossary | The benchmarks entry said the benchmarks section covers seven public ones; the intro said all definitions were quoted; a source was listed that no definition cited. | Six benchmark families, as on the benchmarks page; 19 definitions quoted and 21 marked as the site's own wording; the uncited source is removed. |
| 19 Nov 2026 | Agentic AI vs generative AI in security | A table caption cited "this site's CVE-2026-21589 record", a page that is not on the site. | The caption cites the Atlassian advisory and the CISA KEV entry, both in the source list. |
| 19 Nov 2026 | Evidence and audit trail | Retention was a flat 15 months, and the EU six-month floor was given without the date from which it applies. | Later of audit close and six months after the entry, as on the run-logs guide; the floor applies from 2 Dec 2027 (Annex III) or 2 Aug 2028 (Annex I). |
| 19 Nov 2026 | How to build an agent harness | Fastly was described as seeing no exploitation on 28 Aug and mass exploitation from 1 Sep. | Single-digit probes on 29 and 30 Aug, about 75,000 attempts on 31 Aug and about 171,000 on 1 Sep, as on the agent harness page. |
| 19 Nov 2026 | Dates to know (page removed, see below) | Google Project Zero's comparison of Big Sleep with the Fuzzilli fuzzer was labeled "third-party". | Labeled "vendor": the post compares a Google system, and Project Zero is part of Google. |
| 19 Nov 2026 | Dates to know (page removed, see below) | The overlap between the two bug finders was described as "partial". | "25% overlap in the specific bugs reported", the figure in the Project Zero post. |
| 19 Nov 2026 | Dates to know (page removed, see below) and glossary | The system was written "BigSleep" on one page and "Big Sleep" on the other. | "Big Sleep" on both. Project Zero's post uses both spellings; Google's product name is Big Sleep. |
| 19 Nov 2026 | Dates to know (page removed, see below) | A section listed sources that had returned errors or lacked a usable item, and the intro gave the date window twice. | The section is removed. The window (21 Aug to 19 Nov 2026) is stated once, in the selection rule. |
| 19 Nov 2026 | Glossary | Definitions were paraphrases with a vendor example; 11 sources were listed although more were quoted in the text. | Definitions are quoted from NIST CSRC, OWASP, MITRE ATLAS, the EU AI Act or the issuer, or marked as the site's own wording. The 31 sources cited are listed with their read date. |
| 19 Nov 2026 | Corrections | The log read "None so far" and carried a price example (Gemini 4 Carbon input at $2.00 to 30 Nov 2026, $4.00 from 1 Dec 2026) as a scheduled change. | The log lists the changes above. Scheduled price changes are not corrections and are recorded in the cost guide. |
Pages merged on 19 Nov 2026
A merged page no longer exists. Its address answers with a permanent redirect (HTTP 301) to the page that took over what was true and useful on it, or to the home page where no page did. Links and bookmarks to the old address still arrive.
| Old address | Now answered by | What moved |
|---|---|---|
| /faq/ | Home | Answers on the goal of agentic AI, its main risk and what it is used for now sit on the home page; the rest were already answered on the guide, harness and cost pages. |
| /guides/ | Home | The index of the guides, one line each; 14 guides are built now. |
| /use-cases/method/ | Method | How a job entered the list and how a vendor was confirmed. |
| /evaluation-checklist/method/ | Method | How the checklist questions were chosen and sourced. |
| /build-or-buy/method/ | Method | How the build or buy worksheet was built. |
| /use-cases/vulnerability-triage-and-remediation/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /use-cases/new-disclosure-response/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /use-cases/code-and-dependency-fixes/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /use-cases/cloud-posture/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /use-cases/threat-modeling/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /use-cases/access-reviews/approval-and-evidence/ | Home | Approval and evidence detail for the job. |
| /vendors/ | Home | The vendor lists, now shown per job in the use-case map. |
| /use-cases/ | Home | The six-job matrix with vendor counts. |
| /use-cases/vulnerability-triage-and-remediation/ | Home | The vendor list for the job, with approval wording and sources. |
| /use-cases/new-disclosure-response/ | Home | The vendor list for the job, with approval wording and sources. |
| /use-cases/code-and-dependency-fixes/ | Home | The vendor list for the job, with approval wording and sources. |
| /use-cases/cloud-posture/ | Home | The vendor list for the job, with approval wording and sources. |
| /use-cases/threat-modeling/ | Home | The vendor list for the job, with approval wording and sources. |
| /use-cases/access-reviews/ | Home | The vendor list for the job, with approval wording and sources. |
| /dates-to-know/ | Home | The dated list was removed; no page took it over. |
| /editorial-policy/ | About | Scope and hosting. Source labels are on the method page; what counts as a correction is on this page. |
| /evaluation-checklist/ | Home | The checklist index. The questions are on the ten checklist pages and in the downloadable data file. |
| /evaluation-checklist/tool-permissions-and-identity/ | Home | Removed. Questions Q04 and Q17 remain in the downloadable data file only. The tool register is on tools and permissions. |
| /evaluation-checklist/untrusted-input/ | Home | Removed. Question Q18 remains in the downloadable data file only. |
| /guidance/ | Home | The list of official guidance documents; the documents each page relies on are in its own source list. |
| /guides/how-to-use-agentic-ai-in-cybersecurity/ | Home | Removed. Terms are defined in the glossary. |
| /guides/what-is-agentic-ai-in-cybersecurity/ | Home | Removed. The definition and a worked contrast are in agentic AI vs generative AI in security. |
| /guides/human-in-the-loop-vs-human-on-the-loop/ | Home | Removed. Approval design is in human approval design. |
| /guides/what-an-agent-should-never-do-alone/ | Home | Removed. The limits that go with each autonomy level are in AI agent guardrails. |
| /guides/multi-agent-systems-in-security-work/ | Home | Removed. Splitting work between agents is in orchestration and subagents. |
| /build-or-buy/ | Build vs buy | The cost line, control tests and pilot plan. |
| /benchmarks/cyberseceval/ | Benchmarks | CyberSecEval was dropped from the benchmark list. |
| /agent-harness/agent-harness-examples/ | Agent harness | The list of open harness projects was removed. |
What counts as a correction
- A quotation that does not match the vendor's or standards body's page as it was on the read date.
- A number that does not match its source, or a source address that no longer shows the same text.
- A vendor entry that states an agent or an approval step the cited page does not describe.
- A wrong date, version name or label.
A vendor changing its product or its prices after the read date is not an error in the page; the entry is out of date and is re-read in the next edition. A disagreement with how a page is written is not an error either.
How to report an error
Write to editor@agenticaiincybersecurity.com with the page address and a public address that shows the right text. Every cell on the site is a quotation or a count from a public page, so a page behind a login cannot be used as proof. The message is read as written; no account or form is involved. Accepted corrections appear in the table above with the date, the old value and the new value.
Sources
- Google Project Zero, Fuzzers vs. AI: Comparing Fuzzilli and BigSleep on JavaScript Engines (27 October 2026), read 19 Nov 2026
Last reviewed 19 Nov 2026