Solutions
Windows log collection solutions for SOCs & MSSPs
DPLens is a distributed pipeline at the edge for SOCs and MSSPs, with a complete pipeline in every Windows agent. Most teams come in through a job they have today, such as replacing the Splunk Universal Forwarder or Snare, or cutting what reaches the SIEM. The same agent then covers file integrity monitoring, masking of personal data and offline, air-gapped collection.
- Windows Server 2016–2025
- Windows 10 and 11
- x64
- Self-hosted
- No central processing server
- No ingestion pricing
In short
DPLens is a UK-built, self-hosted, distributed security data pipeline at the edge for SOCs and MSSPs, delivered as a log collection agent for Windows. Every agent is a complete pipeline, so there is no central processing server to run, and data is processed, masked and reduced on your own machines before it leaves, and sent only where you choose. Teams come in by replacing the Splunk Universal Forwarder or a Snare agent, cutting SIEM ingest, adding file integrity monitoring, or collecting logs in air-gapped networks. It delivers to Splunk natively, to any SIEM that accepts syslog, Snare or JSON, or to an OpenTelemetry Collector over OTLP/HTTP.
Who it is for
Built for SOCs and MSSPs
The work moves to the edge, so the centre only has to manage, and the price stops following volume.
DPLens for SOCs
A complete pipeline in every Windows agent, with no central processing server to run, every drop counted against its rule, and no ingestion pricing.
Read more →DPLens for MSSPs
Each customer's data processed on their own machines, no processing infrastructure to stand up per customer, and central management with full support for multi-tenant environments.
Read more →How a distributed pipeline works
What changes when the pipeline runs in the agent rather than in a central processing tier.
Read more →Seven jobs, one agent
Start from the job you have today
Each of these is a way in to the same agent and the same pipeline. Each page explains what DPLens does for that job, the outcome you can expect, and where to find the detail in the documentation.
01
Splunk Universal Forwarder replacement
Deliver to your indexers over cooked S2S or HEC with the index and sourcetype your searches expect, and filter noisy events on the host before they count against your ingest licence.
Read more →02
Snare agent replacement
Snare-format output that a collector already configured for Snare records can receive, with TCP or TLS delivery from a disk-backed queue and edge filtering to cut volume.
Read more →03
Windows Event Log collection
Collect Security, System, Sysmon and custom channels with one source, and filter at the source by Event ID, channel, provider or query so only the events you need are collected.
Read more →04
SIEM cost reduction
Filter, aggregate and rate-limit on the host, so the reduction lands on your SIEM licence rather than further downstream. Every drop is counted and attributed to the rule that caused it.
Read more →05
Windows file integrity monitoring
Scheduled change detection for files, folders and wildcards, every 15 minutes, hourly or daily, from the agent you already run. Supports PCI DSS v4.0.1 Requirement 11.5.2.
Read more →06
Log masking and PII redaction
Redact, partially mask, tokenise or hash card numbers, email addresses, UK National Insurance numbers and your own patterns before anything is cached or sent.
Read more →07
Air-gapped log collection
Offline signed licence keys, no telemetry, no licensing service, and updates on your schedule. An air-gapped machine is a normal deployment, not a special mode.
Read more →Whichever you start with
What every solution shares
Every solution is the same agent and the same pipeline, configured differently. Events pass through seven stages in a fixed order (filter, parse, aggregate, optimise, enrich, mask, rate limit) on your own machines, and can be delivered to several destinations at once.
- No central processing server to size, host or patch, because the processing runs in the agents.
- One signed executable and its installer. No .NET, Java or database to install first.
- Disk-backed delivery to every destination, so an outage queues events instead of discarding them.
- Nothing dropped silently: every drop, mask and aggregation is counted and attributed to its rule.
- No ingestion pricing: licensed per agent and per network source with an offline key.
- DPLens Manager, which manages the agents, not the data: central configuration, fleet health monitoring, deployment and upgrades. Self-hosted, air-gap capable and included in every subscription. Agents can also be deployed with Group Policy, Intune or Configuration Manager.
- Five destination types: syslog, Snare, NDJSON, Splunk (S2S and HEC) and OpenTelemetry over OTLP/HTTP.
Both figures are from our lab benchmark: lab figures, not a guarantee, since real throughput depends on hardware, sources and pipeline rules. Request an evaluation licence and measure DPLens on your own servers, with your own pipeline rules.
Not sure where to start?
Three ways in
See how the platform works
The five pillars, sources, the seven pipeline stages and every destination, on one page.
Read more →Compare it with what you run
Dated, sourced comparisons with the agents and pipelines you may be running today.
Read more →Talk it through
Book a demo, or request an evaluation licence and try it on a test host.
Read more →Secure by design
An agent you can defend in a security review.
See it on your own logs
Try DPLens on one Windows server before you talk to anyone.
Book a demo, or request an evaluation licence and install it on a test host. The documentation covers everything from requirements to Group Policy rollout.