Administration
Roles and permissions in Endpoint Detection & Response
Each role in Endpoint Detection & Response: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Endpoint Detection & Response 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 Endpoint Detection & Response. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in CrowdStrike as part of the managed service.
Roles
Security lead
Chief information security officer, information security officer, IT risk manager. Owns endpoint security for the institution, sets the rules Moraph works within, and decides on incidents.
- Sees: All detections, incidents and hunts; Coverage, policies and exclusions by host group; Incident reports and timelines; Monthly service reviews
- Does: Approves prevention, update and containment policies; Approves exclusions and tuning changes; Decides on response actions outside the pre-approved rules; Decides, with legal and compliance, whether an incident must be notified to regulators; Names on-call contacts and the escalation order
- Cannot: Delete detections or incident records; Change the audit record of actions taken
- Approvals: Approves policies, exclusions and the containment rules. Actions outside those rules need their approval or the on-call contact's.
- Notified about: High and critical incidents straight away, other incidents under the agreed scheme, coverage gaps and the monthly review.
On-call contact
IT manager on call, deputy information security officer, operations duty manager. Represents the institution when an incident needs a decision out of hours.
- Sees: Incidents escalated to them, with evidence and recommended actions; The containment policy and what Moraph has already done
- Does: Answers escalations and authorizes or declines proposed actions; Brings in IT, branch operations or leadership as needed; Records their decisions with Moraph's analyst
- Cannot: Change standing policies or exclusions; Close an incident without the security lead's review where severity requires it
- Approvals: Their decisions on an incident are recorded and reviewed by the security lead.
- Notified about: Escalations under the agreed severity scheme, by phone and email.
Client IT administrator
Desktop and server administrators, branch IT support, infrastructure team. Keeps sensors deployed and machines healthy, and restores machines after an incident.
- Sees: Sensor status and coverage gaps; Incidents affecting their machines; Planned sensor updates and policy changes
- Does: Deploys sensors to new and rebuilt machines; Keeps the asset inventory current; Fixes machines with missing or stale sensors; Restores or rebuilds machines after an incident; Tells Moraph about software that may trigger false detections
- Cannot: Remove a sensor or change prevention policy without the security lead; Lift network containment on a machine without the analyst's confirmation
- Approvals: Changes to their systems follow your own change process; sensor removals need the security lead.
- Notified about: Coverage gaps, incidents on their machines and planned updates.
Moraph security analyst
Moraph security operations analysts and threat hunters. Watches your endpoints, investigates detections and hunts, and acts within the rules you approved.
- Sees: Falcon detections, telemetry and host details for your estate; The containment policy, escalation contacts and incident history; Threat intelligence relevant to financial institutions
- Does: Triages detections and records each decision with evidence; Raises incidents and escalates by severity; Contains machines, stops processes or quarantines files under the pre-approved rules; Runs hunts and investigates findings; Drafts incident reports and proposes tuning
- Cannot: Take actions outside the containment policy without your approval; Add exclusions or change prevention policy without your approval; Access machines beyond what the investigation needs
- Approvals: Actions beyond the containment policy and every policy or exclusion change need your security lead's or on-call contact's approval.
- Notified about: Falcon detections, coverage alerts and requests from your team.
Moraph service manager
Named Moraph service manager. Owns the service relationship, change process and reporting.
- Sees: All service reports, incidents and changes; CrowdStrike platform notices and support cases
- Does: Runs the monthly service review; Manages change requests and their approvals; Follows platform issues with CrowdStrike support; Assembles evidence packs on request
- Cannot: Approve changes on your behalf; Change the record of incidents or actions
- Approvals: Changes they manage are approved by your security lead.
- Notified about: High-severity incidents, platform notices and service issues.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Checks that endpoint monitoring and response work as the institution's program says.
- Sees: Coverage, detection and incident reports; Policies, exclusions and their approvals; Incident timelines within the scope granted
- Does: Reviews evidence packs and reports; Requests additional detail through the security lead
- Cannot: Change or delete anything
- Approvals: Their access is approved by the security lead, with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Security lead | On-call | Client IT | Moraph analyst | Moraph SM | Auditor |
|---|---|---|---|---|---|---|
| Triage and close detections | Full | View | – | Full | View | View |
| Raise and escalate incidents | Full | View | – | Full | View | View |
| Contain hosts under agreed rules | Full | Approves | – | Full | – | – |
| Take actions outside agreed rules | Approves | Approves | – | Own work | – | – |
| Lift network containment | Approves | Approves | Own work | Full | – | – |
| Change prevention policies | Approves | – | View | Full | View | View |
| Add or remove exclusions | Approves | – | View | Full | View | View |
| Deploy or remove sensors | Approves | – | Full | View | – | – |
| Run threat hunts | View | – | – | Full | View | View |
| Decide on regulatory notification | Full | – | – | – | – | View |
| Manage console users and roles | 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
- The containment policy is the heart of the service. It lists which actions Moraph analysts may take on which host groups at which severities without waiting for you, and it is approved by your security lead and reviewed regularly.
- Core banking, payment and other critical servers are usually excluded from automatic containment, so a decision to isolate them is always made by a person at your institution.
- Console access for your staff and Moraph's follows single sign-on with multi-factor authentication, and every action taken in Falcon is recorded with the person and time.
- Auditors and examiners receive temporary read-only evidence for a defined scope and period, approved by your security lead, rather than console accounts.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.