Do you cover NIS2 and DORA?
Yes. Both NIS2 and DORA are core to our GRC practice. We run gap analyses against the operational and reporting requirements of each, help in-scope organisations design the controls and incident-notification workflows the regulations require, and support our clients through internal-audit and supervisor-engagement processes. We work alongside your legal counsel — we do not provide legal interpretation ourselves.
Are you a certification body?
No. DataExpert does not issue ISO 27001, NEN 7510, or other formal certifications — those are issued by accredited certification bodies. We help organisations prepare for certification audits, design the underlying control programme, and remediate findings. We are independent of any certification body, which we believe is the right posture for honest gap analysis.
How is your GRC offering different from a Big-4 advisory firm?
Big-4 advisory firms typically separate their GRC practice from their cybersecurity-operations practice. DataExpert does not. The same firm that writes your control narratives also runs the detection content, the incident response, and the forensic investigations. That keeps documentation grounded in real operational practice — and reduces the gap between what is on paper and what is actually happening in your environment.
Can you help us prepare for a regulator inspection?
Yes. We support clients in advance of regulator inspections by helping them assemble evidence packages, rehearse interview formats, and identify likely findings before they happen. During an inspection, we can sit in as technical advisors to the responding team. Final responses to supervisors are always reviewed and signed off by your own legal counsel.
What is a typical GRC engagement length?
A focused gap analysis runs four to eight weeks. A full control-design programme runs three to six months. Ongoing GRC retainers — annual reviews, evidence-collection support, regulator-readiness checks — run continuously. The right shape depends on your starting position and the regulatory pressure on your timetable. We are happy to scope this in one call. [VERIFY: typical engagement lengths]
Who on our side needs to be involved?
Successful GRC engagements involve your security lead, your compliance or risk officer, an internal-audit representative, and a sponsoring executive who can unblock decisions. We do not need to embed inside every team — but we do need named points of contact who can answer process questions and approve control language. Time commitments are kept light and predictable.
Do you produce policy templates we can adopt?
We start from your existing policies wherever they exist, and we update them rather than replace them. Where new policies are required, we draft them in plain language and in the structure your governance committees already use. The goal is policy your operators read and follow — not policy that lives untouched in a SharePoint folder.
How do you handle vendor and third-party risk?
Vendor and third-party risk is integrated into our GRC programmes. We help clients design assessment questionnaires, run technical due-diligence reviews on critical vendors, and integrate third-party findings into the overall risk register. For organisations with regulated supply chains, we map the vendor programme directly against NIS2 and DORA requirements.