About · Faculty
Six practitioners do the bulk of the writing, with a wider working group that reviews drafts and an advisory ring kept deliberately opaque. Faculty rotate. The standard does not.
Lead author · Sections III, IV
Lisbon, PT
Twelve years operating bot defense for ticketing and travel marketplaces. Previously ran the anti-abuse team at a top-five global ticketing platform; now consults on adversarial traffic for sports leagues and live-event operators.
Lead author · Sections V, VIII
London, UK
Edge engineer who has shipped production WAF rules at hyperscale CDNs. Maintains the open-source library used in every Section V challenge lab. Speaks rarely. Writes carefully.
Lead author · Sections VI, VII
Stockholm, SE
Researcher with a CS dissertation on adversarial machine learning applied to fraud signals. Spent four years inside a major ride-hailing trust team. Co-authors the curriculum's detection-tuning runbooks.
Working group · Section II, IX
Brooklyn, US
Historian of automation, ex-journalist, current security writer. Responsible for the curriculum's taxonomy work and the long-form essays that anchor Section II. Edits every public draft before it ships.
Working group · Section I, exam blueprint
Bengaluru, IN
Curriculum designer with a background in adult security education at a Big Four firm. Owns lab provisioning, exam item authoring, and the candidate handbook. The reason the lab actually works on day one.
Working group · Industry liaison
Copenhagen, DK
Co-founded one of the early bot-management vendors; sold it; now sits on the working group as a deliberate vendor-skeptical voice. Reviews every draft for marketing language and asks hard questions about evidence.
Advisory ring
The standard is reviewed before each public draft by operators whose employers prefer they not be publicly associated with adversarial-traffic work. We list the kinds of organizations they come from. We do not list the people.