Cybersecurity & NIS2 | Endpoint security, MDR, ISO 27001 | Newblend
Newblend Book an introduction
Cybersecurity

Security you can demonstrate

Security is no longer only a technical question. Clients, insurers and legislation ask for evidence: which measures are in place, who is responsible, and what happens during an incident. We arrange both the technology and the record.

In short
  • Endpoint security and managed detection and response, monitored around the clock.
  • Awareness training and phishing simulations, reported per department.
  • ISO 27001 as a framework; Newblend is certified to ISO/IEC 27001:2023 itself.
  • NIS2 support: baseline assessment, measures, incident process and supply chain questions.
  • Documentation drawn from daily work, so an audit becomes a matter of exporting.
Last updated: 5 August 2026
What we do

Four areas

NIS2 and the Dutch Cybersecurity Act

The Dutch implementation takes effect on 15 August 2026; Belgium implemented earlier. Baseline assessment, measures plan and incident process.

Lees meer

ISO 27001

A management system that is used rather than filed. We arrange the structure, the technology and the evidence.

Lees meer

Endpoint security & MDR

Detection and response on endpoints, with alerts assessed by people and incidents followed up.

Lees meer

Awareness

Training per role and phishing simulations, measured on reporting speed rather than click rates.

Lees meer
Baseline

The measures we always check first

  • Multi-factor authentication on every account, including administrative accounts.
  • Backup with a recovery procedure that has actually been tested.
  • Patch management with demonstrable execution, not good intentions.
  • Monitoring and logging, so an incident can be reconstructed afterwards.
  • Supplier management: which parties touch your systems, and what have they arranged.
  • Awareness of staff, with evidence that training happens periodically.
  • An incident process with roles, contacts and reporting deadlines, rehearsed at least once.
Reporting deadlines

Under NIS2 a significant incident requires an early warning within 24 hours, an incident report within 72 hours and a final report within a month. Deciding who does what afterwards costs days you do not have.

How we work

From assessment to evidence

  1. STAP 01
    Baseline assessment

    Where you stand against the measure categories, at a fixed price and with a readable report.

  2. STAP 02
    Measures plan

    What to fix first, what can wait, and what it costs. Prioritised by risk, not by product.

  3. STAP 03
    Implementation

    Technology configured and the incident process written down, with named roles and contact details.

  4. STAP 04
    Maintaining evidence

    Tickets, monitoring and patch reports as your documentation, reviewed at least annually.

Frequently asked questions

Does NIS2 apply to us?

That depends on your sector, your size and your position in the supply chain. The NIS2 check works through those criteria in seven questions.

Do we need ISO 27001 certification?

Not necessarily. The framework is useful even without certification. We set it up so that certifying later is a small step.

Do you handle incidents yourselves?

Yes. Detection and response run around the clock, and we guide the incident process including the reporting obligations.

Is awareness training really necessary?

It is one of the measures clients ask about most, and it is part of the NIS2 duty of care. It also prevents the incidents we see most often.

Read more

Do you know where you stand?

The NIS2 check takes two minutes and shows which obligations apply to you.