About

How cisonews.ai works

cisonews.ai covers AI security for security leaders: the regulation and standards that bind AI systems, the incidents where AI was part of a security failure or attack, and explainers on what both mean for a CISO.

Who we are

cisonews.ai tracks AI laws, AI standards and AI security incidents for security leaders. Pages carry the byline cisonews.ai Desk. We do not use invented personas.

We use AI in research and drafting

AI tools help us find sources, read them and draft pages. An AI model does not supply facts: a drafting agent may only write what a source it fetched in that same run says, and each factual statement is stored with the exact supporting passage from its source. Those passages form an audit trail kept in the page file.

How a page is verified

Every factual sentence traces to a source listed at the foot of the page, with its publisher, its publication date where the source shows one, and a tier.
Tier A sources are the organization itself, regulators, legislatures, courts and official standards bodies. Tier B is established trade and business press. Anything else can only appear next to a tier A or B source for the same fact. Incident entries use tier A or B only.
An automated check re-fetches each source and confirms that every supporting passage appears on it. Pages that fail are not published.
A publication gate enforces the network rules in code: honest dates, minimum substance, no banned filler, no duplicated text, and human review for anything that could harm someone's reputation.
Incident entries record what was reported and by whom. They never assign blame to a named person.

How we date pages

Each page shows two dates. Published is the day the page first went live on cisonews.ai, and it is never moved backwards. The event date is when the thing described happened. The site launched on 27 September 2026, so every page about an earlier law, standard or incident was compiled on its published date from public records, and says so at the top of the page. Structured data reports the published date, never the event date.

Corrections and tips

Corrections are made on the page, noted there with a date, and logged on the corrections page. To report an error or send a tip, see contact.