Source hierarchy
Every legal claim is anchored on a primary source, in this order: (1) the directive or regulation text on EUR-Lex, cited via locale-suffixed ELI paths; (2) ENISA guidance and Commission communications; (3) national competent authorities (ANSSI in France, BSI in Germany, INCIBE in Spain, ACN in Italy, NCSC in the UK and Ireland); (4) national legislative gazettes when transposition acts are referenced. Vendor blogs, consultancy whitepapers, and aggregator news sites are not used as primary sources.
Review process
Each article is reviewed by the nis2insights editorial desk before publication. Review is collective rather than attributed to an individual: the editorial desk is the named reviewer in our schema.org metadata and on every article footer. We do not present fictional individual reviewers — when a real named expert agrees publicly, with a verifiable LinkedIn presence, that addition will appear here and on the relevant articles.
AI assistance disclosure
We use AI assistants for research, drafting, translation, and link-checking under human editorial supervision. Every legal reference, every cited article number, every external link is verified by a human reviewer against the primary source before publication. The editorial desk takes responsibility for the final article, including any error introduced during AI-assisted drafting.
Translation discipline
Articles are written in English and translated into French, German, Spanish, and Italian. Translations are not loose adaptations: same H2 count, same legal citations, same blockquote position. Localised idiom is allowed; altered facts are not. Each translated reference is re-verified against the locale-appropriate EUR-Lex ELI path.
Corrections
Material errors are corrected promptly and logged publicly on the corrections page. The corrections log records, for each fix: the article, the change date, what was corrected, and why. Articles that have been materially updated carry a visible Updated date in their footer, backed by the dateModified field in their schema.org metadata.
Conflicts of interest
nis2insights.com is an independent editorial publication. We do not run advertising, accept paid placements, or receive funding from cybersecurity vendors. We do not link to vendor blogs or consultancy whitepapers in article bodies. If a future commercial relationship arises, it will be disclosed on this page before any related article ships.