You can outsource a lot of cybersecurity work, but only the work itself. Accountability stays with you, and under the Dutch implementation of NIS2 it sits with your board.
My advice is to match each task to the right route, whether that is an MSSP, an interim professional or a seconded specialist, and to keep oversight and risk ownership in-house in every case. That part is not for sale.
What outsourcing cybersecurity does and doesn't hand over
The Netherlands brought NIS2 into national law through the Cyberbeveiligingswet (Cbw, the Dutch Cybersecurity Act), which took effect on 15 August 2026. Under the Act the board approves the security measures required by the duty of care and oversees how they are carried out. Board members also need enough knowledge to judge risks and measures, and have to complete training for it. Article 20 of the NIS2 Directive adds that management bodies can be held liable when the organisation breaches those rules.
Financial services firms get it in even plainer terms. Article 28 of DORA states that a financial entity using ICT services remains fully responsible for its obligations at all times, and Article 5 puts final responsibility for ICT risk management with the management body.
No supplier contract changes that. The part you can hand over is the operational work: monitoring, analysis, patching, testing and reporting.
Three routes, three different problems
MSSPs, interim professionals and secondment get lumped together, yet each one fixes something different. Pick the wrong one and you end up paying for a service when you needed a person, or the reverse.
An MSSP for round-the-clock operations
A managed security service provider sells a service with agreed availability and response times: 24/7 monitoring, an outsourced SOC, firewall or endpoint management. This is work that has to carry on through every night and weekend, and staffing that rota yourself is beyond most organisations.
Be clear about what you are buying, though. An MSSP watches the signals you feed it and acts within the scope of the contract. Someone on your side still has to check that the right log sources are connected and that a 3am alert reaches a person who can make a decision. If you are weighing up the build option instead, this piece on building a SOC team sets out what that takes.
Interim for direction, projects and peaks
An interim professional works inside your organisation, under your direction, on something with a clear start and finish. That could be a Cbw implementation, an IAM migration, an audit finding that has to be closed or the gap left by a departing security officer. Unlike a managed service, they adapt to how your organisation actually runs.
Interim is also how you bring oversight in-house temporarily when you don't have it yet. An interim CISO steering your MSSP contract is a very different arrangement from an MSSP steering itself.
Secondment for capacity that stays longer
Secondment sits in between. The specialist joins your team for an extended period while staying employed by the secondment agency. It suits work that isn't temporary when you haven't yet decided whether to turn it into a permanent role. There is often an option to take the specialist on yourself after a set period.
What always stays in-house
However good the supplier, there are three things I would never outsource.
- Risk ownership. Someone in your organisation decides which risks are acceptable and puts that to the board. An MSSP can advise, but it shouldn't be deciding which residual risks you carry.
- Supplier management. Supply chain security is one of the ten duty-of-care measures listed by the Dutch National Cyber Security Centre (NCSC). The NCSC recommends recording supplier requirements in measurable, unambiguous terms, for example in an SLA. Your MSSP is one of those suppliers, so somebody has to write those terms and check they are met.
- Decisions during an incident. NIS2 requires an early warning within 24 hours of becoming aware of a significant incident. Your MSSP may spot it first, but you file the report and you decide what it means for the business. Agree in advance who rings whom, and when.
Worth knowing: Annex I of NIS2 lists managed service providers and managed security service providers as a sector of high criticality in their own right. Your provider may therefore have obligations of its own. That helps, but it doesn't take any of yours away.
Lead times and flexibility
MSSP contracts usually run for a longer term and come with an onboarding phase: connecting log sources, tuning use cases, testing escalation paths. Allow a few weeks for that. Once it is running, the service scales without you having to recruit.
Interim is the quickest to start and the easiest to end, which makes it a good fit for projects and bridging periods and a poor one for work that will run for years. Secondment falls in the middle on flexibility: you commit to a longer period without the risk of a permanent hire.
If you are unsure which model fits a particular role, this comparison of six staffing models sets out the differences.
Combining outsourcing with hiring
A mix usually works best. Leave the 24/7 operation with an MSSP, give oversight to an internal owner, and bring in temporary specialists for projects your own team can't carry.
No internal owner yet? Start there. An interim CISO or information security officer can firm up the MSSP contract, set out who reports what and when, and help the board sign off the measures while you recruit a permanent successor. Incident response raises the same trade-off, which I cover in this piece on retainers versus an interim DFIR specialist.
At MVPeople we provide interim professionals through MVPeople and seconded specialists through MVProfessionals. We are not an MSSP, so I have no interest in selling you a managed service. You can see the profiles we place on our pages for CISOs and security officers and SOC specialists.
Not sure what to outsource and what to keep? Call or email me and we'll go through your current contracts together.

