NIS2 requires incident detection. A SIEM is how you get it. But most SIEM guidance is written for enterprises with a SOC and a team of analysts. Here's how a 5-50 person company actually runs detection without any of that.
SIEM (Security Information and Event Management) collects logs from your systems, applies detection rules, and alerts you when something matches. It's the difference between "we noticed an incident" and "we detected an incident within the NIS2 deadline."
Don't try to detect everything. Start with what matters:
Add rules as you go. Five rules that work are better than 500 rules that don't. Test each one — send a simulated attack and check whether the alert fires.
Pick one log source (your cloud platform, your endpoint tool, your identity provider). Connect it to your SIEM. Write one detection rule. Test it. If it fires, add another. If it doesn't, fix it before adding more. In a month you'll have 10 working rules. That's more detection than most companies your size have.
NIS2 wants detection that works, not detection that exists. Five tested rules with evidence are worth more than 500 untested rules in a dashboard nobody looks at.
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.