Skip to content

Administration

Roles and permissions in Database Security

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

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

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

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

Roles

Information security officer

CISO, information security officer, IT risk manager. Owns the database monitoring policy and the decisions on what is monitored, alerted on and blocked.

  • Sees: All alerts, reports and service reviews; The policy baseline and every change to it; Coverage gaps and exceptions
  • Does: Approves the policy baseline and change requests; Decides on escalated alerts or delegates to security operations; Approves any blocking policy; Grants auditors and examiners read-only access; Accepts coverage exceptions
  • Cannot: Edit or delete captured audit data; Apply policy changes directly without the change process
  • Approvals: Approves policy changes, blocking, coverage exceptions and auditor access.
  • Notified about: Escalated alerts, changes waiting for approval, coverage gaps and the monthly service review.

Security operations analyst

SOC analyst, security engineer, incident responder. Investigates escalated database alerts alongside other security signals.

  • Sees: Escalated alerts with Moraph's triage notes; Audit data for the users and databases involved in an investigation; Database alerts in your SIEM
  • Does: Investigates escalated alerts; Requests additional audit data or searches; Records the outcome of each investigation; Opens incidents under your incident procedure
  • Cannot: Change monitoring policies; See unmasked values unless your institution grants it
  • Approvals: Incident decisions follow your incident procedure.
  • Notified about: Alerts escalated by Moraph.

Data owner

Business data owner, application owner, head of lending or deposit operations. Confirms which data is sensitive and who should have rights to it.

  • Sees: Classification results for their databases; User rights on their databases; Summary access reports for their data
  • Does: Confirms or corrects classification results; Reviews and certifies user rights; Requests rights changes through your database team
  • Cannot: Change monitoring policies; See detailed audit data outside an approved investigation
  • Approvals: Rights changes they request are applied by your database team under your access process.
  • Notified about: Classification reviews and user rights reviews due.

Database administrator

Database administrator, database engineer. Supports deployment and explains database activity, while their own privileged activity is monitored.

  • Sees: Agent status on their database servers; Questions from Moraph about activity on their databases
  • Does: Installs or permits agent installation under change control; Confirms the purpose of jobs, hosts and service accounts; Applies user rights changes after review
  • Cannot: Change monitoring policies or stop monitoring; View or alter audit data about their own activity
  • Approvals: Agent installations and database changes follow your change process.
  • Notified about: Agent health issues on their servers and questions raised during triage.

Moraph service engineer

Moraph database security engineer, Moraph service manager. Deploys, tunes and operates Imperva and triages its alerts for you.

  • Sees: Alerts, audit data needed for triage, and coverage; Policies and configuration; Moraph service portal records for your service
  • Does: Triages alerts and escalates those it cannot explain; Proposes and applies approved policy changes; Monitors agent, gateway and server health; Manages vendor support cases; Runs user rights reviews and the monthly service review
  • Cannot: Decide that an alert is or is not an incident; Apply policy changes or blocking without approval; Access your databases directly
  • Approvals: Every change needs your approval; emergency actions are limited to those agreed in advance and reported afterwards.
  • Notified about: Imperva alerts, agent and gateway health issues and vendor notices.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews database monitoring controls and evidence without being able to change anything.

  • Sees: Policies, coverage and change history; Reports on privileged activity and sensitive data access within scope; User rights review results
  • Does: Reads and exports reports within their scope, with each export logged; Requests specific audit extracts through the information security officer
  • Cannot: Change anything; See unmasked values
  • Approvals: Access is granted by the information security officer with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionSecurity leadSOC analystData ownerDBAMoraph opsAuditor
View alertsViewView––FullView
Triage and close alertsFullFull––Full–
Decide an alert is an incidentFullFull––––
Search audit dataViewView––View–
Confirm data classificationView–Own work–Full–
Change audit and security policiesApproves–––Full–
Enable a blocking policyApproves–––Full–
Install and update agentsApproves––Own workFull–
Certify user rightsView–Own work––View
View reports and service reviewsViewViewOwn work–ViewView
Grant auditor accessApproves–––––

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

How access is controlled

  • Database administrators are monitored, not monitoring: they cannot change policies, stop monitoring or see audit data about their own activity.
  • Moraph triages, but your institution decides. Only your security team can treat an alert as an incident, and blocking is enabled only on policies your information security officer approves.
  • Roles are configured with you during implementation and can follow your identity provider's groups. Access to unmasked query values is granted separately and only where needed.
  • Every policy change, triage decision and report export is recorded, and auditors receive temporary read-only access with a defined 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.