Skip to content

Administration

Roles and permissions in Vulnerability Management

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

Applies to Vulnerability 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. Information security officer
  3. Remediation owner
  4. Service owner
  5. Moraph vulnerability analyst
  6. Auditor or examiner (read-only)
  7. Executive viewer
  8. Permissions at a glance
  9. How access is controlled

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

Roles

Information security officer

Information security officer, CISO, IT risk manager. Owns the vulnerability management program and decides how risk is handled when a finding cannot be fixed in time.

  • Sees: All findings, assets and scan results across the institution; Remediation progress against the targets you set; The risk acceptance register; Program reporting for management and examiners
  • Does: Sets remediation targets by severity; Approves or rejects risk acceptances; Approves changes to scan scope that remove assets; Decides escalation of overdue findings; Presents program results to management and the board
  • Cannot: Approve a risk acceptance they requested themselves without a second approver; Delete findings or scan history; Edit the audit trail
  • Approvals: Approves risk acceptances, remediation targets and reductions in scan scope.
  • Notified about: Critical findings on exposed systems, risk acceptance requests, acceptances expiring, and findings past their target.

Remediation owner

Server administrator, network engineer, desktop engineering lead, application owner. Fixes the vulnerabilities on the systems their team is responsible for.

  • Sees: Findings and tickets for assets their team owns; How to fix each finding and which hosts are affected; Their team's progress against remediation targets
  • Does: Applies patches and configuration changes; Updates tickets with progress and the change made; Requests a rescan to verify a fix; Requests a risk acceptance with the reason and compensating controls; Reports suspected false positives with evidence
  • Cannot: Close a finding without a verifying rescan; Approve a risk acceptance; Change scan scope, schedules or policies
  • Approvals: Risk acceptances they request are approved by the security officer.
  • Notified about: New tickets for their assets, findings approaching or past their target, and verification results.

Service owner

IT manager, infrastructure manager, IT director. Manages the service day to day with Moraph and keeps the scan scope matched to the network.

  • Sees: Scan schedules, scope, coverage and scan health; Open findings and remediation progress; The monthly service review; Licence use against asset counts
  • Does: Approves scan schedules and scan windows; Adds new networks and assets to scope; Assigns asset ownership to teams; Attends the monthly service review and agrees actions; Approves Moraph administrative access to Tenable
  • Cannot: Remove assets from scope without the security officer; Approve risk acceptances; Delete scan history
  • Approvals: Approves scan schedules and additions to scope; removals from scope also need the security officer.
  • Notified about: Scan failures not fixed before the next run, unknown assets found, licence limits approaching and vendor service notices.

Moraph vulnerability analyst

Moraph vulnerability analyst, security operations engineer. Runs Tenable for you: keeps scans healthy, triages findings, routes them and verifies fixes.

  • Sees: Tenable configuration, scan results and scan health; Findings, tickets and risk acceptances; Asset inventory and ownership
  • Does: Configures scan policies, schedules, scanners and agents; Checks every scan run and fixes credential or coverage failures; Triages new findings, removes duplicates and verifies suspected false positives; Raises remediation tickets and escalates critical findings; Rescans to verify fixes and prepares service and program reports
  • Cannot: Approve risk acceptances or suppress a finding without a recorded reason and approval; Change systems on your network to apply fixes, unless that is separately agreed; Reduce scan scope without your approval
  • Approvals: Scope and schedule changes are approved by your service owner, and risk acceptances by your security officer.
  • Notified about: Scan failures, critical new findings, verification requests and vendor notices.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews scanning coverage, findings and remediation without being able to change anything.

  • Sees: Scan history and coverage; Findings, remediation tickets and their dates; The risk acceptance register with approvals; Program reports
  • Does: Reads and exports records within their scope, with each export logged; Requests further evidence through the security officer; Leaves review notes where your institution enables them
  • Cannot: Change, approve, close or delete anything; Run scans
  • Approvals: Their access is approved by the security officer, with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.

Executive viewer

Chief information officer, chief risk officer, board risk committee members. Follows the program's results at a summary level.

  • Sees: Coverage and open findings by severity and age; Remediation trends against targets; Number and age of risk acceptances
  • Does: Reads dashboards and summary reports; Receives scheduled reports; Asks the security officer for detail
  • Cannot: See host-level detail unless granted; Change or approve anything in the service
  • Approvals: Their access is approved by the security officer.
  • Notified about: Scheduled summary reports.

Permissions at a glance

ActionSecurityRemediationService ownerMoraph analystAuditorExecutive
Set scan scope and schedulesApproves–ApprovesFullView–
Run an ad hoc scanFull–FullFull––
View findingsFullOwn workFullFullView–
Triage and prioritize findingsView–ViewFullView–
Update remediation ticketsFullOwn workFullFull––
Close a finding after rescanView–ViewFullView–
Request a risk acceptanceFullOwn workFullFull––
Approve a risk acceptanceApproves–––View–
Set remediation targetsFullViewViewViewViewView
View summary dashboardsFullOwn workFullFullViewView
View audit trailView–ViewViewView–
Manage users and rolesApproves–Full–––

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

How access is controlled

  • Moraph analysts can triage, route and verify findings, but suppressing a finding or accepting a risk always needs a recorded reason and your security officer's approval.
  • Remediation owners see only the findings on assets their team owns. Asset ownership is set during implementation and maintained by your service owner.
  • Every change to scope, schedules, findings and acceptances is recorded with who made it and when, and access is reviewed periodically by the security officer.
  • Staff sign in through your identity provider, and roles can follow its groups. Auditors and examiners get temporary read-only access with a 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.