Industry · Security & legal tech

App development for security and legal tech. Two disciplines where confidentiality is the product.

We build custom apps for cybersecurity vendors and legal service providers: SOC portals, CISO dashboards, contract management, case management and e-discovery. Professional secrecy and NIS2 are not a plugin but an architectural choice, built in from the first sprint rather than layered on in an audit week.

SecuritySOC & SIEM tooling
SecurityVulnerability management
Legal techContract management
Legal techCase management & e-discovery

The Dutch security and legal tech market in numbers.

~17.000
Lawyers registered with the NOvA (Netherlands Bar)
~2.700
Law firms in the Netherlands
~450
Cybersecurity vendors and MSSPs active in the NL
NIS2
Mandatory for thousands of essential and important entities

Source: NOvA annual report, CBS (Statistics Netherlands), NCSC NIS2 implementation report.

Two industries, one shared requirement.

At first glance, a SOC analyst and a property lawyer have little in common. One hunts for indicators of compromise in a SIEM, the other drafts a deed of transfer. But in both industries you are essentially selling the same thing: confidentiality that must be demonstrable. A layperson must not be able to reach the data, a regulator must be able to see who did, and the client, whether a company or an individual seeking legal help, must be able to produce evidence when something goes wrong.

That makes these two sectors much closer to each other, in terms of software architecture, than to the average B2B SaaS product. A good legal-tech application and a good security tool share the same foundations: end-to-end encryption with keys you manage yourself, a record-level audit trail, a role-and-permissions model that takes the principle of least privilege seriously, and data-residency choices you can defend to a regulator. The rest is content: in legal tech it revolves around case files, in security around alerts.

Our broader approach to custom apps is on the app development overview page. On this page we show how we translate that approach specifically to cybersecurity vendors, law firms, corporate legal departments and compliance functions, and which compliance layer we include as standard because in these sectors adding it afterwards is not an option.

Apps that fit every sub-discipline.

Security and legal tech are each divided into a handful of specialisms, each with its own flow, its own integrations and its own compliance requirements. For each discipline we show what we typically build, and which modules we include as standard.

SOC & vulnerability management

The workhorse for cybersecurity vendors, MSSPs and in-house SOC teams. Here we build customer portals in which an end organisation sees its own alert feed, vulnerability status and incident timeline, plus the operator side in which your own analysts triage, work through runbooks and report back to the customer. Pentest reports are generated from the same data, so a customer doesn't receive three different documents with conflicting figures.

Our SOC module set includes a SIEM add-on for the most widely used platforms (Microsoft Sentinel, Splunk, Elastic), a ticketing layer that feeds straight into the end customer's ServiceNow or Jira, and a reporting engine for both operational weekly reports and board-level quarterly overviews. Everything with keys that you or your customer manage, not us.

  • Multi-tenant customer portalsEvery end customer in their own tenant, with their own data, roles and retention.
  • SIEM integrationsBidirectional integration with Sentinel, Splunk, Elastic, Wazuh and IBM QRadar.
  • Vulnerability management dashboardsAsset inventory, CVSS scoring, remediation status and asset ownership.
  • Pentest report generatorFindings from the same dataset, readable for both the customer and the developer.

Built to the strictest standards of security and the legal profession.

In both sectors the compliance requirements are non-negotiable. From sprint 1 we work within the framework of GDPR, NIS2, ISO 27001 and the specific professional rules of the legal profession and the notarial profession. The regulator gets no opportunity to ask questions we can't answer.

GDPR Art. 32 + 35

Security and DPIA

Privacy by design as the starting point. On every project we deliver a DPIA document. Data flows, retention and data subject rights are documented for your DPO. In a legal context this also means explicit legal bases for special-category personal data within case files.

NIS2 Directive

Incident reporting obligation and risk management

For essential and important entities (and their suppliers) we build the incident management flow in line with the NIS2 timelines: early warning to the CSIRT, follow-up notification, final report. Integrated with your own escalation process, not separate from it.

ISO 27001 + 27017/27018

Information security management

We work to an ISO 27001-compliant development process, with traceable risk assessment, a secure SDLC and a tested deployment flow. For cloud implementations, additional controls from 27017 and 27018 where relevant.

EU AI Act

Responsible use of AI in legal tech

For AI features such as automatic classification of incoming post, case-law search and contract clause extraction, we map out the risk classification and document the governance, the origin of the training data and the human-intervention points. For law firms, this is the difference between an impressive demo and something you actually dare to use.

eIDAS Regulation

Qualified electronic signature (QES)

eIDAS-compliant signing for clients and lawyers, with an audit log per signature and a qualified timestamp. We integrate with DocuSign, Adobe Sign, ValidSign, KENA, Signhost and specific notarial providers where required.

NOvA regulation + Wna

Professional secrecy as a system property

For law firms and notaries, we build professional secrecy into the architecture: BYOK encryption, administrators can see that a case file exists but not its contents, and audit logs are themselves tied to the case file. A third party, including us, cannot view the data.

NEN 7510

Healthcare-legal intersections

For legal tech applications at the intersection with healthcare (medical disciplinary cases, legal matters in youth care, personal injury), we deliver NEN 7510-compliant work: the additional information security controls that the healthcare standard imposes on a legal case file.

Seamlessly connected to the security and legal ecosystem.

We integrate with the tools your security team or your firm already works with. No migration of your entire stack: our app complements it and replaces individual components only where they no longer fit.

Microsoft Sentinel
SIEM / SOAR
Splunk & Elastic
Log platforms
CrowdStrike
EDR / XDR
Tenable / Qualys
Vulnerability scanners
BaseNet / Cleverdesk
Law practice management
DocuSign / ValidSign
E-signing & eIDAS
Relativity / Nuix
E-discovery
KvK / CDR / CTR
Legal registers

No one-off integrations on a per-project basis.

We have standardised the integrations above across multiple security and legal projects. For a new project, we set up the integration using the same abstraction layer: fewer bugs, faster lead times, and your IT team can manage it themselves if we step away. For the financial side of your legal practice, we integrate with Exact, MoneyMonk, AFAS or e-Boekhouden via the same integration layer we use for contract management software.

For specific firm software (in-house middleware, on-prem Java legacy systems, or niche tools such as FilelinX or Knight), we build case by case. This takes extra time in the planning phase but prevents integration debt that you would still be feeling years later.

Typical apps we build for these sectors.

Twelve types of apps that we use as building blocks: six for security, six for legal tech. In practice, a project usually combines two or three of these types.

Security

SOC portals for MSSPs

A client environment where an end organisation tracks its alerts, escalations and SLA status, and an analyst environment where your team does triage, works through runbooks and documents handovers. A single source of truth instead of a SIEM with a mailbox next to it.

Security

Vulnerability management dashboards

Asset inventory, CVSS scoring, remediation tracking and ownership per asset. With automatic correlation between vulnerabilities and ongoing incidents, so a patch team knows which CVE is running on a priority-1 asset and which is not.

Security

CISO reporting and GRC dashboards

Board-level reporting for CISOs: control maturity per ISO domain, open audit findings, risk acceptance log and NIS2 status. Designed for the quarterly conversation with the board, not for audit week.

Security

Incident response apps

Mobile and desktop app for the IR team: playbooks, evidence collection, chain of custody, and a communication log for internal stakeholders and, where relevant, the regulator. NIS2 timelines built in, not tucked away in a PDF on the wall.

Security

Security awareness and phishing simulation

Your own content, your own branding, and integration with your HR system for cohort segmentation and targeted campaigns per department. With reporting that shows where the weak spots are without naming and shaming individual employees.

Security

Pentest reporting platform

For pentest firms: from scope document through execution to readable findings. A client portal where the end organisation tracks the remediation status of each finding. With an automated re-test flow and certificate issuance.

Legal tech

Contract management (CLM)

End-to-end contract management for corporate legal teams and legal service providers: drafting from a clause library, negotiation with version tracking, e-signing, an archive with retention rules, and obligation tracking. Builds on our contract management software approach.

Legal tech

Case management for law firms

Client files with statutory deadlines, decision points and time registration that feeds straight into invoicing. For legal aid practices, including Legal Aid Board export. Built on the same foundations as our case management system.

Legal tech

Legal research with LLMs

Case law search with language models, trained or fine-tuned on public rulings and your firm's own precedents. With source citations per answer and a confidence score, so a lawyer can verify the outcome. Part of our broader AI development practice.

Legal tech

E-discovery and review platforms

For investigation and dispute practices: import of large document corpora, deduplication, OCR, predictive coding (TAR), and privilege review with chain of custody. EU data residency and keys under your control, because an investigation leaves no room for doubt about where the data went.

Legal tech

Compliance and regtech apps

GDPR DPIA tooling, AI Act conformity assessment, NIS2 self-assessment, AML onboarding for banks and notaries, sanctions list screening, and UBO checks via the KvK. For compliance officers, DPO services and Big Four auditors who deliver this tooling as a service to their end clients.

Legal tech

Secure messaging and client portals

End-to-end encrypted communication between client and lawyer, or between security team and customer. Message threads tied to a file or case, signed read receipts, and no email attachments ending up on a private tablet. Optionally with blockchain attestations as indisputable proof of existence.

From intake to go-live in clear steps.

A project for a security vendor or a law firm has its own rhythm. Five phases that are identical for every project: the scope per phase differs, the rhythm does not.

01 · Audit

Workflow mapping

Days on site with your SOC team or with two lawyers. Result: current flows mapped, bottlenecks marked, compliance requirements inventoried.

02 · Design

Threat model and scope

For each discipline, which flow goes into the app, which integrations take priority, and which flows are left for later. Including an explicit threat model before we start building.

03 · Build

Sprints with security review

One working flow delivered every sprint. Security review is part of the definition of done; no after-the-fact pentest that blows everything open.

04 · Cutover

Phased rollout

One team first, then the next. With every rollout: training, documentation, and hand-over to your own IT or compliance team.

05 · Maintenance

Ongoing compliance

We adapt with every change in legislation and CVE disclosure. Fixed monthly price, security patches within an agreed SLA window, and transparent time tracking for extra work.

The context we work in.

NCSC NIS2 guidance

"Essential and important entities must take appropriate technical, operational and organisational measures to manage the risks to the security of network and information systems, and be able to demonstrate this."

NOvA regulation on the legal profession

"Lawyers must organise their practice in such a way that professional confidentiality is safeguarded, including in the digital working environment and when third parties are used to manage data."

EU AI Act, Art. 6 and Annex III

"AI systems intended to be used by a judicial authority or on their behalf to assist a judicial authority in researching and interpreting facts and the law are classified as high-risk AI systems."

Answers for CISOs, partners and heads of legal.

The questions we hear most from security managers, lawyers and compliance officers.

Do you have experience with security vendors, or only with security teams at end-user organisations?
Both. We build platforms for MSSPs and cybersecurity vendors who deliver their service to end customers (multi-tenant SOC portals, GRC-as-a-service, pentest reporting), and we build internal tools for security teams at end-user organisations (CISO dashboards, awareness platforms, incident response apps). The architectural approach is the same; the tenant layer differs.
How do you handle professional secrecy technically for law firms?
We build professional secrecy as a property of the system, not as a compliance layer on top. Encryption with keys you control (BYOK), administrators can see that a file exists but not its contents, audit logs are themselves bound to the file, and backups are encrypted with the same keys. EU-hosted cloud or on-premises, depending on your policy and the Dutch Bar Association (NOvA) requirements for your type of practice.
Can an app for lawyers or a SOC portal run on-premises?
Yes. For law firms with strict professional-secrecy policies, for government supervision applications, and for security vendors serving enterprise customers with data-sovereignty requirements, we run the entire stack in your own data centre or a Dutch single-tenant private cloud. In both scenarios, the encryption keys stay with you.
How do you make sure NIS2 incident notifications reach the CSIRT on time?
We build the reporting flow into the incident response app in line with the NIS2 timelines: early warning within 24 hours, follow-up notification within 72 hours, final report within one month. The flow is a first-class part of the app, not a PDF alongside the system. Status, content and proof of submission are all captured in the audit trail.
Do you work with LLMs for case law search? And how do you handle hallucinations?
Yes. We work with fine-tuned or retrieval-augmented language models on public case law (rechtspraak.nl) plus your own precedents. Every answer comes with source citations and confidence scores, and without a citation there is no answer. That is a design choice, not a setting. We always build in a human-in-the-loop step for advice to clients. Under the AI Act, this falls into the high-risk category; we supply the governance documentation with it.
Do you replace BaseNet, Cleverdesk, Splunk or Microsoft Sentinel?
Usually not. BaseNet, Cleverdesk and the major SIEM platforms are good at what they do. We complement them where your way of working, your customer portal approach or your reporting requirements don't fit an off-the-shelf package. For a new project, we start by asking openly whether replacing them would genuinely be better. Often it wouldn't, and we'll tell you so.
Do you work with our current IT supplier or in-house IT team?
More often than not. We hand over the codebase, build instructions, infrastructure as code, an architecture overview and a runbook so that an external party can take over. This is a deliberate design choice to avoid vendor lock-in. Knowledge transfer is part of the final sprint. Some clients keep us on under a maintenance contract; others hand maintenance to their own team after go-live.
What about data residency and sub-processors?
For security and legal work, we host in the EU by default (often in the Netherlands), on infrastructure whose sub-processor list we know and can share. A data processing agreement is a standard part of delivery, including a sub-processor annex. For clients where exposure to the US CLOUD Act is an issue, we choose infrastructure without a US parent company.
What determines the cost?
The biggest cost drivers are the number of app types you combine (a single SOC portal versus a SOC portal with vulnerability management and a CISO dashboard), the depth of the integrations, the weight of the compliance layer (NIS2 plus the AI Act plus NOvA rules is more work than any one of them), and the choice between cloud and on-prem. We work with fixed sprint budgets, so you stay in control of each sprint and can steer the scope.
What if we want to add a new standard or a new type of case file along the way?
That is why we build workflow and compliance controls as data, not as code. An administrator can set up an extra case type, a new control framework or a new NIS2 category themselves. For a new standard with its own risk classification, we run a short follow-on development sprint in which we map the rules, build integrations and deliver templates.

Ready to give your security or legal tech practice its own platform?

An introductory call of half an hour. We listen to your cases, ask questions about your compliance and architecture requirements, and give you useful direction, even if the outcome is that your existing SIEM, GRC suite or sector-specific package is a better fit than a custom build. For the broader context, see our app development overview page.

Fabian van DijkBusiness developer · Appfront · fabian.vandijk@appfront.nl
Share LinkedIn Email

Edit content