Self-check
Your score stays on your own device.
-
A colleague says: 'We have had backups for years, so we are covered.' What is true?
A backup that was never restored is an assumption. Restore it on a test environment and you see what is missing.
-
The order system is used all day; the internal wiki hardly at all. How do you set their recovery?
Losing a night of input is a problem for an order system, while a wiki can wait. So agree the numbers per system.
-
You order a penetration test. What do you agree in writing before it starts?
The scope comes first: which systems, production or a copy, and what happens once they are inside. Plus a phone number in case something breaks.
-
Your machine supplier's technician needs remote access to one machine. What do you arrange?
The technician gets the machine and nothing else. Two-step verification belongs on every connection from outside.
-
Someone says: 'NIS2 means replacing all our IT.' What is true?
What is missing tends to be logging nobody reads, backups never restored and access left open after someone leaves. Those are fixed in your existing setup.
-
A significant incident on a Friday evening, with half the management away. What gets the first report out on time?
The first signal is due within 24 hours, and a fuller report follows later. A procedure nobody has used is one you find at the wrong moment.
-
An auditor asks who has access to the customer file. What is the strongest answer?
An auditor looks at practice. Evidence that comes from your own systems holds up, and next year it is still there.
-
You are setting SPF right. What do you list first?
It is hardly ever just the mail server: your accounting package, web shop and newsletter send too. Leave one out and its mail can land in spam.