Decide what leaves, and how
Data Loss
Prevention
We build the policy and program behind your DLP tools: what counts as sensitive, which channels it may travel through, and what gets blocked, warned or allowed. Rules run quietly in test mode first, so you learn what would have been stopped before anyone's work is interrupted.
Policy before blocking
Block what matters,
allow the work.
We design to CIS Controls v8.1 Control 3 and the data security outcomes in NIST CSF 2.0, then write rules with your administrators in the platform you own, such as Microsoft Purview or Google Workspace. Every rule runs in test mode first, and the results decide what moves to enforcement.
Phase 01 · Sensitive data
Agree what you are trying to protect.
A short list of sensitive data types, each with the patterns, labels or fingerprints that detect it.
- Data types drawn from your classification scheme and obligations.
- Detection method chosen for each: patterns, sensitivity labels or exact data match.
Phase 02 · Channels & flows
Map where that data legitimately moves.
A map of the channels sensitive data uses today, sanctioned and not.
- Email, cloud storage, endpoints, USB, web uploads and AI tools reviewed.
- Legitimate business flows recorded so rules do not break them.
Phase 03 · Policy design
Decide what is blocked, warned or allowed.
A DLP policy stating the action for each data type and channel, approved by data owners.
- Actions set by sensitivity: allow, warn, require a justification, or block.
- An exception path for teams with a real business need.
- Alert ownership and triage steps written for your team.
Phase 04 · Test mode
Run the rules quietly and read the results.
Evidence of what each rule would have caught, with false positives tuned out.
- Rules deployed in test or simulation mode by your administrators.
- Matches reviewed for noise and for missed cases.
- Thresholds and exceptions adjusted before enforcement.
Phase 05 · Enforce & hand off
Turn on enforcement in stages, then hand over the program.
Enforced rules, a triage runbook and a tuning record your team can maintain.
- Enforcement switched on by channel and group, starting small.
- User notices written so a block explains itself.
- Runbook and tuning log handed to the team that owns alerts.
Agree what you are trying to protect.
A short list of sensitive data types, each with the patterns, labels or fingerprints that detect it.
- Data types drawn from your classification scheme and obligations.
- Detection method chosen for each: patterns, sensitivity labels or exact data match.
Map where that data legitimately moves.
A map of the channels sensitive data uses today, sanctioned and not.
- Email, cloud storage, endpoints, USB, web uploads and AI tools reviewed.
- Legitimate business flows recorded so rules do not break them.
Decide what is blocked, warned or allowed.
A DLP policy stating the action for each data type and channel, approved by data owners.
- Actions set by sensitivity: allow, warn, require a justification, or block.
- An exception path for teams with a real business need.
- Alert ownership and triage steps written for your team.
Run the rules quietly and read the results.
Evidence of what each rule would have caught, with false positives tuned out.
- Rules deployed in test or simulation mode by your administrators.
- Matches reviewed for noise and for missed cases.
- Thresholds and exceptions adjusted before enforcement.
Turn on enforcement in stages, then hand over the program.
Enforced rules, a triage runbook and a tuning record your team can maintain.
- Enforcement switched on by channel and group, starting small.
- User notices written so a block explains itself.
- Runbook and tuning log handed to the team that owns alerts.
Key benefits
Stop the leak without stopping the work.
Policies start from how your people actually move data. Legitimate flows are recorded first, so enforcement stops risky transfers without blocking the payroll export your finance team sends every cycle.
Every rule runs in test mode before it blocks anything. Noise is tuned out on evidence, so the alerts your team receives are worth opening.
A DLP license with no policy behind it does little. We give the tool clear rules, an owner and a triage process, so it protects data instead of producing unread reports.
What you get
What lands on
your desk.
Three handoffs that let your team run DLP after we step back.
The document
The DLP policy
Sensitive data types, detection methods, channel rules and actions, exceptions and alert ownership. Written so leadership can approve it and administrators can build it without guessing at intent.
The working file
The rule and tuning log
Each rule with its data type, channel, mode, match volume, false positive notes and change history. The record your administrators keep as rules change, so nobody has to rediscover why a threshold was set.
The conversation
The enforcement review
A session with IT, security and data owners to review test results, approve which rules move to enforcement and agree how blocked users get help.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
DLP questions
Before anything
gets blocked.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
That is the risk this method is built to avoid. Legitimate flows are mapped first, rules run in test mode, and enforcement starts with a small group. When a rule does block something, the user sees why and how to request an exception.
Your team. ForgePath does not run a monitoring service. We write the triage runbook, set alert ownership and tune volumes so the people who receive alerts can handle them as part of their normal work.
Often you already own one. Microsoft 365 and Google Workspace both include DLP in many of their licensing tiers. We start with what you have and say plainly if a gap needs another product.
DLP inspects content against rules as it moves, which can raise privacy and employment law questions. We design with HR and counsel involved, and set rules so reviewers see only what a match requires.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








