Skip to content

Administration

Roles and permissions in Email Security

Each role in Email Security: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Email Security as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 5 min readReport a problem
On this page
  1. Roles
  2. Security owner
  3. Privacy officer
  4. Messaging administrator
  5. Moraph email security engineer
  6. Moraph security analyst
  7. Auditor (read-only)
  8. Permissions at a glance
  9. How access is controlled

Who can see and do what in Email Security. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Proofpoint as part of the managed service.

Roles

Security owner

CISO, information security officer, IT security manager. Owns the email security program: which policies apply, who is protected, and what Moraph may do on its own.

  • Sees: All policies, protected-people lists and their versions; Incident volumes, outcomes and escalations; Most-targeted people and campaigns; Monthly service reports
  • Does: Approves policy changes and quarantine rules; Approves the list of protected executives and finance staff; Agrees the triage runbook, including what analysts may remove or block without asking; Reviews the monthly service report with Moraph; Decides who may see message content
  • Cannot: Apply policy changes directly; Moraph applies approved changes; Edit or delete incident history or the audit trail
  • Approvals: Approves every policy change, protected-people change and runbook change; changes they propose themselves need a second approver your organization names.
  • Notified about: Escalated incidents, campaigns aimed at protected people, and changes waiting for approval.

Privacy officer

HIPAA privacy officer, chief privacy officer, compliance officer. Decides whether an email incident involving patient information is a reportable breach and what notifications follow.

  • Sees: Incidents flagged as possibly involving PHI; Message details, recipients and actions taken for those incidents; Outbound encryption and PHI rule matches
  • Does: Reviews escalated incidents that may involve PHI; Requests further evidence from Moraph through the incident record; Records the breach risk assessment outcome; Records any notification decision and its date
  • Cannot: Change email policies or quarantine settings; Release quarantined messages
  • Approvals: Their breach determinations follow your organization's own approval process; the service records the outcome.
  • Notified about: Incidents escalated as possibly involving PHI and responses to their evidence requests.

Messaging administrator

Microsoft 365 administrator, Exchange or Google Workspace administrator, DNS administrator. Runs the mail system and DNS that Proofpoint sits in front of, and makes the routing and record changes the service needs.

  • Sees: Routing, connector and DNS change requests; Mail flow health and delivery issues; Quarantine releases for the mailboxes they support
  • Does: Makes approved routing and connector changes in your mail system; Publishes SPF, DKIM and DMARC records; Grants the permissions Proofpoint needs to remove delivered messages; Works delivery problems with Moraph
  • Cannot: Change Proofpoint policies; See the content of incident messages unless granted separately
  • Approvals: Routing and DNS changes follow your organization's change process; policy changes are approved by the security owner.
  • Notified about: Change requests assigned to them and mail flow alerts.

Moraph email security engineer

Moraph email security engineer, messaging security consultant. Configures and maintains the Proofpoint policies that put your decisions into effect.

  • Sees: Policy configuration and its version history; Message classification trends and false positives; Proofpoint release notes and service notices
  • Does: Builds and tunes filtering, impersonation, tagging and encryption rules; Tests proposed changes and reports their expected effect; Applies changes after your approval and records each version; Specifies routing and DNS changes for your administrators; Raises platform issues with Proofpoint support
  • Cannot: Apply a policy change without your approval; Make changes in your mail system or DNS; Decide whether an incident is a breach
  • Approvals: Every policy change they make is approved by your security owner first, except emergency sender blocks allowed by the runbook.
  • Notified about: Approved changes ready to apply, false-positive reports and Proofpoint service notices.

Moraph security analyst

Moraph security analyst, security operations analyst. Works the queue of reported and flagged messages and acts on confirmed threats within the runbook you approve.

  • Sees: Reported messages and messages Proofpoint flags after delivery; Sender, recipient and click information for each incident; Message content only where your organization grants it
  • Does: Triages reported messages and records the outcome; Removes confirmed malicious messages from mailboxes; Blocks senders and domains under the runbook; Escalates incidents with clicks, replies or possible PHI to your team; Releases quarantined messages on service desk requests within policy
  • Cannot: Change policies; Take actions outside the agreed runbook without your approval; Make breach or staff conduct decisions
  • Approvals: Actions outside the runbook, such as removing internal messages, need your security owner's approval.
  • Notified about: New reported messages, post-delivery detections and replies to their escalations.

Auditor (read-only)

Internal auditor, external auditor, compliance reviewer. Reviews email controls, incidents and evidence without being able to change anything.

  • Sees: Policy versions and approval records; Incident records and outcomes within the scope granted; Monthly service reports; The audit trail
  • Does: Searches and reads records within their scope; Exports reports they have been given access to, with each export logged; Leaves review notes where your organization enables them
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the security owner, with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.

Permissions at a glance

ActionSecurity ownerPrivacyMail adminMoraph engineerMoraph analystAuditor
Propose a policy changeFullFullFullFullFull–
Approve a policy changeApproves–––––
Apply policy changes–––Full––
Change the protected-people listApproves––Full––
Triage reported messagesView–––Full–
Remove delivered messagesApproves–––Full–
Release quarantined messagesFull–Own work–Full–
View incident message contentFullOwn work––Own work–
Record a breach determinationViewFull––––
Change mail routing and DNSView–FullView––
View reportsViewViewViewViewViewView
View audit trailViewView–ViewViewView

"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.

How access is controlled

  • Nobody approves a change they proposed: policy and protected-people changes from Moraph are approved by your security owner, and changes the security owner proposes need a second approver you name.
  • The triage runbook sets exactly what Moraph analysts may do without asking, such as removing a confirmed malicious message or blocking an outside sender; anything else is escalated.
  • Access to message content is limited to the roles you choose. By default Moraph analysts work from message headers, links and attachments' verdicts, and see body content only where you grant it.
  • Every permission change is recorded with who made it and when, and access to the Proofpoint console is reviewed with you periodically. Auditors get temporary read-only access with a scope and an end date.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.