Skip to content

Administration

Roles and permissions in Privileged Access Management

Each role in Privileged Access Management: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Privileged Access Management 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. Privileged user
  3. Safe owner
  4. Information security officer
  5. Security operations analyst
  6. Moraph service engineer
  7. Auditor or examiner (read-only)
  8. Platform owner
  9. Permissions at a glance
  10. How access is controlled

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

Roles

Privileged user

System administrator, core banking administrator, database administrator, network engineer. Uses privileged accounts to administer systems, through CyberArk rather than with standing passwords.

  • Sees: The accounts in safes they are a member of; Their own requests and approvals; Their own session history
  • Does: Requests access to an account with a reason or ticket number; Connects to systems through brokered sessions; Retrieves a password where the policy allows it; Reports accounts that are missing or not working
  • Cannot: Approve their own access requests; Change safe membership or platform policies; Turn off session recording
  • Approvals: Access to accounts under dual control needs a safe owner's approval each time.
  • Notified about: Requests approved, rejected or about to expire.

Safe owner

System owner, platform lead, infrastructure manager. Decides who may use the accounts in their safe and approves access where dual control applies.

  • Sees: Accounts in their safes and their rotation status; Pending and past access requests for their safes; Safe membership and recent session activity
  • Does: Approves or rejects access requests; Certifies safe membership during access reviews; Requests membership changes through a change request; Names the owner of each onboarded account
  • Cannot: Approve their own request; Change platform policies or rotation schedules
  • Approvals: Membership changes they request are applied by Moraph after information security approval where your policy requires it.
  • Notified about: Access requests waiting for approval, access reviews due and rotation failures on their accounts.

Information security officer

CISO, information security officer, IT risk manager. Owns the privileged access policy and the decisions that shape the platform's configuration.

  • Sees: All reports, alerts and service reviews; The configuration baseline and every change to it; Exceptions and their compensating controls; Session records, when reviewing an alert or incident
  • Does: Approves the configuration baseline and change requests; Approves onboarding waves; Accepts or rejects exceptions; Decides on alerts escalated as possible incidents; Grants auditors and examiners read-only access
  • Cannot: Retrieve credentials from safes they are not a member of; Edit or delete audit records
  • Approvals: Approves changes, waves, exceptions and auditor access; their own access requests follow the same dual control as anyone else's.
  • Notified about: Escalated alerts, changes waiting for approval, baseline differences and the monthly service review.

Security operations analyst

SOC analyst, security engineer, incident responder. Investigates privileged activity that Moraph's triage has escalated, alongside other security signals.

  • Sees: Escalated alerts with Moraph's triage notes; CyberArk audit events in your SIEM; Session recordings when investigating an alert
  • Does: Investigates escalated alerts; Requests containment actions such as rotating a credential or suspending a user; Records the outcome of each investigation
  • Cannot: Change platform configuration; Retrieve credentials from safes for their own use without the normal request
  • Approvals: Containment actions follow your incident procedure; Moraph applies urgent platform-side actions on request from authorized contacts.
  • Notified about: Alerts escalated by Moraph.

Moraph service engineer

Moraph privileged access engineer, Moraph service manager. Implements and operates the platform for you under approved changes.

  • Sees: Platform health, rotation status and alerts; Platform policies, safes and connector configuration; Moraph service portal records for your service
  • Does: Onboards accounts and verifies rotation; Prepares and applies approved changes; Triages alerts and escalates those that need your decision; Works rotation exceptions with system owners; Manages vendor support cases; Runs the monthly service review
  • Cannot: Retrieve credentials from your safes without explicit authorization; Apply changes without approval, except agreed emergency actions; Accept exceptions on your behalf
  • Approvals: Every change needs your approval; emergency actions are limited to those agreed in advance and reported afterwards.
  • Notified about: Platform health alerts, rotation failures, security alerts and vendor notices.

Auditor or examiner (read-only)

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

  • Sees: Policies, the configuration baseline and change history; Access reviews and their results; Reports on accounts, rotation, requests and sessions within scope
  • Does: Reads and exports reports within their scope, with each export logged; Requests session recordings through the information security officer
  • Cannot: Retrieve credentials or start sessions; Change anything
  • Approvals: Access is granted by the information security officer with a scope and an end date.
  • Notified about: Nothing by default.

Platform owner

IT security manager, identity and access manager. Your day-to-day contact for the service, who coordinates onboarding and changes inside your institution.

  • Sees: The service portal, onboarding tracker and change requests; Reports and service reviews; Vendor notices passed on by Moraph
  • Does: Raises change and onboarding requests; Coordinates system owners on blocked accounts; Schedules access reviews; Attends the monthly service review
  • Cannot: Approve changes that need information security sign-off; Retrieve credentials outside their own safe memberships
  • Approvals: Their requests are approved by the information security officer where the change affects policy.
  • Notified about: Change status, onboarding blockers, vendor notices and service review packs.

Permissions at a glance

ActionPriv. userSafe ownerSecurity leadSOC analystMoraph opsAuditorPlatform owner
Request access to an accountOwn workOwn workOwn workOwn work––Own work
Approve access under dual control–Approves–––––
Use brokered sessionsOwn workOwn workOwn workOwn work––Own work
View session recordingsOwn workViewViewView–––
Onboard accounts––Approves–Full––
Change safes and platform policies––Approves–Full––
Accept a rotation exception––Approves––––
Triage platform alerts––ViewViewFull–View
Certify safe membership–FullView––ViewView
View reports and service reviews–Own workViewViewViewViewView
View audit trail––ViewViewViewViewView
Grant auditor access––Approves––––

"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 their own access request, and administering the vault is kept separate from membership of the safes that hold your credentials, including for Moraph engineers.
  • Roles are configured with you during implementation and can follow your identity provider's groups, so joiners, movers and leavers are handled by your existing process.
  • Every permission change, credential retrieval and session is recorded by CyberArk, and every change request and approval is recorded in Moraph's service portal.
  • Auditors and examiners receive temporary read-only access with a defined scope and an end date, granted by your information security officer.

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.