Administration
Roles and permissions in Network Access Control
Each role in Network Access Control: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Network Access Control 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 Network Access Control. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Cisco ISE as part of the managed service.
Roles
Network engineer
Network engineer, infrastructure manager, network architect. Owns the network equipment and design that ISE works with.
- Sees: ISE policy, node health and authentication activity; Switch and wireless configuration changes raised by Moraph; Stage plans and enforcement status by location
- Does: Approves configuration changes on switches and wireless controllers; Works with Moraph on network design for segmentation; Agrees maintenance windows for enforcement stages and upgrades; Investigates network faults found during triage
- Cannot: Approve access policy changes without the security officer; Release a quarantined clinical device without clinical engineering
- Approvals: Network changes they request go through your change advisory process.
- Notified about: Changes needing approval, node health problems and enforcement stages scheduled.
Security officer
Chief information security officer, security operations manager, HIPAA security officer. Owns network access policy and accepts the risk of exceptions.
- Sees: Access policy and its change history; Quarantine, authentication failure and exception reports; Security alerts shared from ISE to your SIEM; The audit trail of administrative changes
- Does: Approves access policy and changes to it; Approves exceptions and their end dates; Leads security incidents involving network access; Reviews the monthly service report; Decides when a device should stay restricted
- Cannot: Approve their own exception request; Edit the audit trail
- Approvals: Policy changes in clinical areas also need clinical engineering sign-off.
- Notified about: Exception requests, policy changes for approval, security-relevant alerts and incidents.
Clinical engineering
Clinical engineering manager, biomedical engineer, healthcare technology manager. Makes sure medical devices are identified correctly and that enforcement never puts patient care at risk.
- Sees: Medical devices seen on the network by location and profile; Unknown devices awaiting identification; Enforcement stage plans for clinical areas
- Does: Identifies unknown devices and confirms their owner; Keeps the medical device inventory reconciled with what ISE sees; Signs off enforcement in clinical areas; Approves release of quarantined medical devices; Brings new medical devices through onboarding before they connect
- Cannot: Change access policy directly; Approve exceptions that the security officer has not accepted
- Approvals: Their sign-off is required before enforcement in any clinical area.
- Notified about: Unknown devices in clinical areas, quarantined medical devices and enforcement stages planned for clinical areas.
Service desk
IT service desk analyst, clinical IT support. Takes reports from staff whose devices cannot connect and routes them to the right team.
- Sees: Connection status of a device by port or address; Whether a device is in the restricted network and why; Open triage tickets
- Does: Looks up a device's connection status; Raises tickets to Moraph for triage; Tells staff what will happen next
- Cannot: Release a device from the restricted network; Change policy or profiles
- Approvals: Nothing they do needs approval; releases are decided by device owners and the security officer.
- Notified about: Updates on tickets they raised.
Moraph service team
Moraph network security engineer, service manager. Designs, configures and runs ISE and triages what it sees, within your approvals.
- Sees: ISE configuration, policy, profiles and logs; Node health and capacity; Platform notices and support cases with Cisco
- Does: Designs and maintains authentication, profiling and authorization policy; Triages quarantined devices, failures and new profiles daily; Runs enforcement stages with rollback plans; Applies patches and upgrades in agreed windows; Opens and follows support cases with Cisco; Prepares the monthly service review
- Cannot: Change policy, enforce a new location or release a quarantined clinical device without the required approvals; Change switch or wireless configuration outside your change process; Access ISE outside the scope your organization authorizes
- Approvals: Policy changes are approved by the security officer, network changes by your change process, and clinical enforcement by clinical engineering.
- Notified about: Alerts, quarantined devices, node health issues, approved changes and Cisco security advisories.
Auditor (read-only)
Internal auditor, risk assessor, external assessor under temporary access. Reviews network access control without being able to change it.
- Sees: Access policy and its change history; Exceptions and their approvals; Enforcement status and reports
- Does: Reads policy, reports and exceptions; Exports evidence within scope, with each export logged; Records review notes where enabled
- Cannot: Change anything
- Approvals: Access is approved by the security officer, with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Network eng. | Security | Clinical eng. | Service desk | Moraph | Auditor |
|---|---|---|---|---|---|---|
| View device and session status | View | View | View | View | Full | View |
| Identify and classify devices | View | View | Full | – | Own work | – |
| Change access policy | View | Approves | View | – | Full | View |
| Enable enforcement at a location | Approves | Approves | Approves | – | Full | – |
| Release a quarantined device | – | Approves | Approves | – | Full | – |
| Approve an exception | – | Approves | View | – | – | View |
| Change switch and wireless settings | Approves | View | – | – | Own work | – |
| Raise triage tickets | Full | Full | Full | Full | Full | – |
| Apply patches and upgrades | Approves | View | – | – | Full | – |
| Manage ISE administrator accounts | – | Approves | – | – | Full | – |
| View audit trail | View | View | – | – | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Moraph carries out changes but does not decide them: access policy is approved by your security officer, network changes go through your change process, and clinical areas need clinical engineering sign-off before enforcement.
- A quarantined medical device is released only with clinical engineering and security approval, and an urgent clinical need is handled through an agreed emergency path that is recorded and reviewed afterward.
- ISE administrator accounts are named, sign in through your identity provider, and are reviewed periodically; nobody shares an administrator login.
- Moraph staff work within the scope your organization authorizes, every administrative change is logged, and changes are reported in the monthly service review.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.