Acceptable Use Policy Template: NIS2 Never Names It, but 8 CIR Annex Points Shape What Staff Sign
NIS2 never says ‘acceptable use policy’ — yet 8 CIR Annex points shape what staff sign. Template sections, owners, and the consent line to leave out.
NIS2 compliance guides and resources
NIS2 never says ‘acceptable use policy’ — yet 8 CIR Annex points shape what staff sign. Template sections, owners, and the consent line to leave out.
A data classification policy under NIS2 sets the level that 9 other CIR controls read. Build four-axis levels, handling rules and the evidence auditors check.
The DORA regulation covers 20 types of financial firm and 19 named tech providers. Its 4-hour reporting clock, penalties and three links to NIS2, explained.
Payment, e-money and crypto fintechs are usually DORA-only: NIS2’s annexes never list them. A scope map of 8 fintech models, including those neither law reaches.
No NIS2 text sets an audit interval, so your audit program’s own plan becomes the benchmark. Scope, a risk-tiered 3-year cadence, and the evidence to keep.
By our count, a security awareness training platform alone proves 2 of NIS2’s 13 Annex 8 training requirements. See which ones still need your own documents.
NIS2’s implementing regulation names 11 elements your IT security policy must contain. Five are missing from almost every free template – here they are.
NIS2 sets no retention period and never uses the word version. Here is what CIR 2024/2690 Annex 1.1.1 binds you to, and how to derive a defensible schedule.
NIS2 change management policy sits under Article 21(2)(e), not (a). What Annex 6.4 binds you to in four sentences, and which ITIL extras are only ENISA advice.
NIS2 names retention three times and never gives a number. Here is how to build a data retention policy auditors accept — and defend the periods you set.