Administration
Roles and permissions in Data Loss Prevention
Each role in Data Loss Prevention: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Data Loss Prevention as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Data Loss Prevention. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Forcepoint as part of the managed service.
Roles
DLP policy owner
CISO, information security officer, data protection lead. Owns the DLP program: what is protected, on which channels, and how strictly.
- Sees: All policies, classifiers and their versions; Incident volumes, outcomes and false-positive trends; Agent coverage across the estate; Monthly service reports
- Does: Approves the data types and channels in scope; Approves policy changes and moves from audit to warn or block; Approves allowed routes for legitimate business flows; Reviews the monthly service report with Moraph; Decides who may see incident evidence
- Cannot: Apply policy changes directly; Moraph applies approved changes; Edit or delete incident history or the audit trail
- Approvals: Approves every policy change, allowed route and reviewer role; changes they propose themselves need a second approver your organization names.
- Notified about: Policies ready for approval, high-severity incidents and agent coverage below the level you set.
Compliance or privacy officer
Chief compliance officer, privacy officer, BSA or consumer compliance lead. Decides whether an incident involving customer data needs notification or further action.
- Sees: Escalated incidents and their investigation notes; Incident evidence, where your organization grants it; Incident outcomes and notification decisions
- Does: Reviews incidents escalated as possible exposure of customer information; Records whether an incident is reportable and why; Coordinates notification with legal and the incident response team; Reviews data types in scope with the policy owner
- Cannot: Change policies or classifiers; Close incidents that are still under investigation by another reviewer
- Approvals: Records notification decisions; policy changes go to the policy owner.
- Notified about: Incidents escalated as possible exposure of customer data.
Incident reviewer
Security analyst, insider risk investigator, HR or line-of-business reviewer. Investigates escalated incidents and decides what happened.
- Sees: Incidents assigned to them, with the policy matched and the destination; Incident evidence, where their role allows; Earlier incidents for the same user
- Does: Reviews escalated incidents and the user's justification; Contacts the user or their manager under your procedures; Records the outcome and any follow-up action; Refers incidents to compliance where customer data may have been exposed
- Cannot: Change policies or allowed routes; See incidents outside their assigned business units; Delete incidents or evidence
- Approvals: Their outcomes on possible exposures are reviewed by the compliance or privacy officer.
- Notified about: Incidents assigned to them and incidents reopened by compliance.
IT endpoint administrator
Desktop engineering, endpoint management team. Deploys and maintains the Forcepoint agent on your endpoints.
- Sees: Agent coverage, versions and health; Agent packages and release notes from Moraph
- Does: Deploys agent packages through your software distribution tools; Fixes endpoints missing an agent or not reporting; Schedules agent updates in agreed windows
- Cannot: See incident evidence; Change policies or disable enforcement
- Approvals: Agent removal on any endpoint needs approval from the policy owner.
- Notified about: Coverage gaps, agent health problems and new agent releases ready to deploy.
Moraph DLP engineer
Moraph data protection engineer. Configures, tunes and maintains Forcepoint so policies catch what they should and little else.
- Sees: Policies, classifiers, routes and their version history; Incident statistics and false-positive patterns; Platform and channel health
- Does: Builds and tunes classifiers and policies; Tests changes in audit mode and reports their expected impact; Applies approved changes and records them; Plans and applies platform updates; Works product issues with Forcepoint support
- Cannot: Approve their own changes or move a policy to block without your approval; View incident evidence unless you grant access for a stated task; Close incidents as reviewed on your behalf
- Approvals: Every change is approved by your policy owner and peer-reviewed by a second Moraph engineer before it is applied.
- Notified about: Approved changes ready to apply, channel or server health alerts and Forcepoint product notices.
Moraph security analyst
Moraph security operations analyst. Works the incident queue so your team sees only the incidents that need a decision.
- Sees: Incident metadata: user, policy, channel, destination and justification; Incident evidence, only where your organization permits Moraph triage of it; Triage runbooks and escalation contacts
- Does: Reviews and groups incidents; Closes false positives with a reason; Escalates incidents to your reviewers with a summary; Feeds false-positive patterns back to the DLP engineer
- Cannot: Decide on staff conduct or notification; Change policies; Export incident evidence
- Approvals: Closures are sampled by your policy owner at the monthly review.
- Notified about: New incidents by severity and responses to escalations.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews the DLP program's policies, incidents and decisions without changing anything.
- Sees: Policies in force and their version history; Incident records and outcomes within the scope granted; Monthly service reports and coverage reports
- Does: Reads and searches records within their scope; Exports reports they have been given access to, with each export logged
- Cannot: Change, close or delete anything; See incident evidence unless specifically granted
- Approvals: Their access is approved by the policy owner, with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Policy owner | Compliance | Reviewer | IT admin | Moraph engineer | Moraph analyst | Auditor |
|---|---|---|---|---|---|---|---|
| Propose a policy change | Full | Full | – | – | Full | Full | – |
| Approve a policy change | Approves | – | – | – | – | – | – |
| Move a policy from audit to block | Approves | – | – | – | – | – | – |
| Apply policy changes | – | – | – | – | Full | – | – |
| Approve an allowed business route | Approves | View | – | – | – | – | – |
| Triage and close false positives | View | – | – | – | – | Full | – |
| Investigate escalated incidents | Full | View | Own work | – | – | – | – |
| View incident evidence | Full | Full | Own work | – | – | – | – |
| Record a notification decision | View | Full | – | – | – | – | – |
| Deploy and maintain agents | View | – | – | Full | View | – | – |
| View reports and coverage | View | View | Own work | View | View | View | View |
| View audit trail | View | View | – | – | View | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Moraph proposes and applies policy changes, but only your policy owner can approve them, and nothing moves from audit to block without that approval.
- Incident evidence can contain the Social Security or card numbers that triggered it, so access to it is limited to the roles you name; Moraph analysts triage from incident details unless you choose otherwise.
- Console roles follow groups in your directory, and reviewers can be limited to the business units they are responsible for.
- Every policy change, incident decision and evidence view is recorded with the person and time, and auditors get temporary read-only access with a scope and an end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.