Home / The OWASP Wire / The OWASP Wire: who should know
Industry news, read from a vault · beta
The OWASP Wire: who should know
Who should be told, and the route to tell them: organisations, never people, from their own published contact pages.
The wires: The Industry WireThe AWS WireThe OWASP Wire · Day by dayThe charterFor the desks
Who the stories of The OWASP Wire concern, and how to reach them, so that they can be told this wire exists and sent what it found. By organisation route only, under the contact rules this site already publishes: a role address from the organisation’s own contact page, one hop, the page’s bytes hashed when fetched; never a person’s address, never a directory, never a guess. Everything here is public, so anyone can check who was told. The routes this site found are recorded in admin/build/wire-reach.json; the desk adds its own to the vault as data/contacts.json under the same rules, and this page draws both, with what the vault already carries: the map’s entities with their public pages and repositories, and the sources’ sites.
Opening the vault…
For an agent
Who The OWASP Wire concerns and how to reach them, by organisation route only, under the contact rules at world-news-day/data/contact-rules.json: 2 route(s) this site found (admin/build/wire-reach.json: organisation, the contact page fetched and hashed, the role addresses the page publishes, and what it says each is for), data/contacts.json from the vault when the desk adds it, the map's entities with pages and repositories, and the sources' sites. Never a personal address. The charter: wire/charter.html.