Home / The Industry Wire / The OWASP Wire

Industry news, read from a vault · beta

The OWASP Wire

Everything happening at and about OWASP: project releases, the GenAI Security Project, the Foundation and its board, events and chapters, and OWASP in the news. Each story is traced to its source and joined to the projects graph. Each story with where it came from and who else covered it, corrected where it is read, live from the wire's vault. A beta, with one named reader by their agreement.

The wires: The Industry WireThe AWS WireThe OWASP Wire · Day by dayThe charterFor the desks

What this is

Everything happening at and about OWASP, weekly: project releases, the GenAI Security Project, the Foundation and its board, events and chapters, and OWASP in the news. Each story is traced to its source and joined to a graph of the projects, their leaders and the standards they map to, which this page draws from the same vault. For every story: where it came from, who else covered it, one exact quote with its source, and why it matters. The stories are found, grouped and written by agents, from a registry of sources with a licence tier each (the sources), and every story says what it is: ai-generated, unreviewed until a person has reviewed it. The current edition is of 2026-10-13: first edition: two weeks of OWASP, with September context. Each edition adds what happened and keeps the earlier stories, so the page is the whole wire so far, not one edition of it.

Corrections propagate. When the desk fetches a primary source it could not reach, or finds a story wrong, it corrects the story in the vault and records the correction, dated, in the story’s own changes; this page draws them under the story, in blue, for as long as the vault keeps them, and the edition’s header carries the desk’s note of what was corrected. The vault’s release notes name the stories added and updated in each publish, and the page flags them Updated. A corrected story is corrected where it is read, which is the argument this site makes of every publication.

Read it as an inbox. The bar above the stories says what is new since your last visit, how much of it is for you and how much is not under the lens you read as, and what the wire’s desk says changed in the vault: its release notes, one per publish (data/releases.json), newest first since your last visit. At each story, one tap: Done, Read later, Follow up, Not for me, More like this or Wrong; the story leaves your inbox, and the filters bring it back. Your decisions and what you have seen are kept in this browser first and reach your own vault when you press Update the vault; until then the bar and the Vault button say what is only here. Each wire keeps its own inbox, its own visit and its own lens. How it works.

Read as someone. The same stories reach different readers. Choose a persona and the edition shows what reached them, through which concern, and what was withheld, with the reason. That join is recorded in the vault by the wire’s own code (pipeline/join.py), not computed here; the page shows the record. If you are reading this site as one of its personas, the lens follows it.

The map. The vault carries a graph of 20 entities (data/map.json: each with its aliases, its facts, its leaders and the standards it maps to), and the page draws it under the bar: each entity with the stories whose named entities match it, so a story is read beside what it is about. Nothing is computed beyond that match; the facts are the vault’s.

Who should know. The reach page lists who this wire concerns and how to reach them, by organisation route only, under the contact rules this site publishes: what this site found on the organisations’ own contact pages, and what the vault carries. The charter says what every agent in the chain enforces; day by day shows every wire’s releases and stories by date.

Where it comes from. The data is not on this site. It is in an encrypted vault that the wire’s agents write to, and this page opens it in your browser with a published read key: eitf274v on dev.send.sgraph.ai. A commit to the vault is on this page within two minutes, with no release of the site. Anyone can read the whole vault, and its history, with sgit clone sgit_public_read_b09571f053cc19f5f8b50f8a8d0d82a115e07282fca14e58e7c3328975cd9d79:eitf274v. How the wire works has the contract and the wire’s own documents, read from the same vault.