Skip to content

Administration

Roles and permissions in Zero Trust "Black Cloud" Overlay

Each role in Zero Trust "Black Cloud" Overlay: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Zero Trust "Black Cloud" Overlay 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. Application owner
  3. ISSM or ISSO
  4. Security operations
  5. Moraph service manager
  6. Moraph platform engineer
  7. Help desk
  8. Assessor or inspector (read-only)
  9. Permissions at a glance
  10. How access is controlled

Who can see and do what in Zero Trust "Black Cloud" Overlay. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Zscaler as part of the managed service.

Roles

Application owner

System owner, mission application owner, program office technical lead. Decides who should reach their application and approves the access policy that enforces it.

  • Sees: Their application's onboarding status, segment and policy; Who can reach the application and recent access decisions; Access reviews for their application; Change requests affecting their application
  • Does: Requests onboarding and names the user groups who need access; Approves or returns access policy drafts; Certifies access lists during reviews and requests removals; Raises change requests with the mission justification; Confirms the application works for test users before cutover
  • Cannot: Change policies directly in the platform; Approve changes to other owners' applications; Change the overall architecture or segmentation design
  • Approvals: Approves access policies and changes for their application; architecture-level changes also need the ISSM.
  • Notified about: Policy drafts waiting for approval, access reviews due, changes applied to their application, and alerts involving it.

ISSM or ISSO

Information system security manager, information system security officer, cybersecurity lead. Owns the security posture and authorization evidence of the overlay and approves its design and baseline.

  • Sees: The architecture, configuration baseline and every difference from it; All change requests and their approvals; Alert and incident records; Control mappings and evidence packages
  • Does: Approves the architecture and the configuration baseline; Approves changes that affect segmentation, posture rules or administration; Reviews baseline differences and decides how they are resolved; Uses the evidence package in your authorization and continuous monitoring; Sets which alerts go straight to security operations
  • Cannot: Edit or delete audit records; Make changes in the platform without a recorded change; Waive another application owner's approval for their application
  • Approvals: Approves the baseline and architecture-level changes; their own change requests are approved by a second designated approver.
  • Notified about: Baseline differences found, changes waiting for approval, escalated alerts and vendor service notices.

Security operations

SOC analyst, cyber defense analyst, incident responder. Receives escalated alerts from the overlay and leads the response to any confirmed incident.

  • Sees: Access and connector logs in your SIEM; Alerts Moraph has escalated, with the evidence; Containment actions taken in the overlay
  • Does: Investigates escalated alerts; Decides on containment and response; Directs Moraph to take containment actions the runbook allows, such as suspending a user's access; Records the incident outcome
  • Cannot: Change access policies outside an approved emergency change; Change the configuration baseline
  • Approvals: Emergency containment actions are recorded and reviewed afterward by the ISSM through the change process.
  • Notified about: Alerts escalated by Moraph and vendor notices that affect security.

Moraph service manager

Moraph service delivery manager. Runs the managed service for you: onboarding plan, change process, vendor relationship and monthly service reviews.

  • Sees: The onboarding tracker, baseline and change records; Alert and incident records; Vendor cases and notices; License usage
  • Does: Plans onboarding waves with your program office; Coordinates change requests through your process; Manages Zscaler licensing and vendor cases; Runs monthly service reviews and tracks actions; Prepares reporting and evidence packages
  • Cannot: Approve changes on your behalf; Grant a user access without an approved policy; See your application data
  • Approvals: Their work is governed by the approvals of the application owner and ISSM; nothing in the service is self-approved.
  • Notified about: Changes approved or returned, escalated alerts, vendor notices and overdue actions.

Moraph platform engineer

Moraph zero trust engineer, network security engineer. Configures segments, policies and App Connectors and triages alerts, within the changes your organization approves.

  • Sees: Platform configuration within the service scope; Connector health and access logs needed for triage; Change requests assigned to them
  • Does: Drafts segments and access policies; Deploys, patches and monitors App Connectors; Applies approved changes and confirms the result; Triages alerts and escalates confirmed issues; Compares live configuration with the baseline
  • Cannot: Apply a change that has not been approved, except containment your runbook pre-authorizes; Approve their own change; Delete logs or audit records
  • Approvals: Every change they apply has a recorded approval from your organization.
  • Notified about: Changes approved for their window, connector failures and alerts assigned to them.

Help desk

Service desk analyst, IT support technician. Handles first-line user questions and passes access and connector issues to Moraph.

  • Sees: Whether a user's access attempt was allowed or denied, and the reason; Known service notices
  • Does: Answers user questions about signing in and the client; Raises tickets to Moraph for access or connector issues; Tells users how to request access through the application owner
  • Cannot: Grant or change access; See configuration beyond access decisions
  • Approvals: None; access requests are routed to application owners.
  • Notified about: Service notices and changes to their tickets.

Assessor or inspector (read-only)

Security control assessor, inspector general staff, internal auditor. Reviews the configuration, logs and evidence without being able to change anything.

  • Sees: Architecture, baseline and control mappings; Change, alert and access review records; Exports of access logs within the period granted
  • Does: Reads records within the scope granted; Exports evidence, with each export logged; Records review notes where enabled
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the ISSM with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the ISSM.

Permissions at a glance

ActionApp ownerISSMSecurity opsMoraph SMMoraph engHelp deskAssessor
Request application onboardingOwn workFull–Full–––
Approve an access policyApprovesApproves–––––
Change access policies in the platform––––Full––
Approve architecture and baseline–Approves–––––
Deploy or update App Connectors––––Full––
Triage alerts–ViewFullViewFull––
Order containment of a user's access–ApprovesFull––––
Certify access reviewsOwn workView–View––View
View access decisionsOwn workFullFullViewViewViewView
Manage licenses and vendor cases–View–Full–––
View audit trail and evidence–ViewViewView––View
Manage administrator accounts–Approves–Full–––

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

How access is controlled

  • No one approves their own change: Moraph engineers apply only changes your organization has approved, and an ISSM's own change requests need a second designated approver.
  • Roles are agreed during implementation and can be limited by application, environment or site, so each application owner sees and approves only their own applications.
  • Moraph's administrative accounts are named, role-based and reviewed with you.
  • Assessors and inspectors get temporary read-only access with a defined scope and an end date, rather than shared accounts.

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.