Skip to content

Administration

Roles and permissions in Third-Party Risk Scoring

Each role in Third-Party Risk Scoring: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Third-Party Risk Scoring 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. TPRM manager
  3. Relationship owner
  4. Security analyst
  5. Procurement
  6. Moraph service team
  7. Auditor or examiner (read-only)
  8. Permissions at a glance
  9. How access is controlled

Who can see and do what in Third-Party Risk Scoring. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in BitSight as part of the managed service.

Roles

TPRM manager

Head of third-party risk, vendor risk manager, vendor management office lead. Owns the third-party risk program and decides how monitoring results affect each relationship.

  • Sees: The whole vendor portfolio, ratings, findings and tiers; Alerts and Moraph's triage decisions; Open follow-ups, escalations and risk acceptances; Service reports and the monitoring record
  • Does: Approves vendor tiers and alert thresholds; Decides on escalated findings; Accepts risk, or asks for it to be accepted at the right level, when a finding is not resolved; Approves vendors added to or removed from monitoring; Reports to risk committees; Attends the monthly service review
  • Cannot: Edit or delete the monitoring record; Change BitSight's ratings or findings; Accept risk above the authority your policy gives them
  • Approvals: Approves tiers, thresholds, portfolio changes and risk acceptance within their authority.
  • Notified about: Escalated findings, follow-ups overdue under your policy, and rating changes on critical vendors.

Relationship owner

Business relationship owner, vendor manager, service owner. Owns the relationship with a vendor and is accountable for following findings up with it.

  • Sees: Ratings, findings and history for their own vendors; Finding summaries prepared by Moraph; Open follow-ups for their vendors
  • Does: Takes finding summaries to the vendor through the agreed channel; Records the vendor's response and remediation plan; Confirms uncertain vendor matches; Requests escalation or risk acceptance
  • Cannot: See vendors they do not own unless granted; Close a follow-up without a recorded outcome; Change tiers or thresholds
  • Approvals: Closures and risk acceptance on their vendors are approved by the TPRM manager.
  • Notified about: New finding summaries on their vendors and follow-ups coming due.

Security analyst

Information security analyst, third-party security assessor, CISO office. Judges the technical significance of findings and advises the TPRM manager and relationship owners.

  • Sees: Findings and the evidence behind them for all monitored vendors; Moraph's triage notes; Vendor remediation responses
  • Does: Reviews escalated findings and adds a technical assessment; Advises whether a vendor's response is adequate; Suggests changes to alert thresholds
  • Cannot: Approve tiers, thresholds or risk acceptance; Contact vendors directly unless your process allows; Change BitSight's ratings or findings
  • Approvals: Their assessments go to the TPRM manager for decision.
  • Notified about: Findings escalated for technical review.

Procurement

Procurement manager, sourcing lead, contract manager. Brings security posture into vendor selection, contracting and renewal.

  • Sees: Ratings for prospective vendors they requested; Ratings and open findings for vendors at renewal
  • Does: Requests a rating for a prospective vendor; Attaches the rating to the sourcing file; Flags renewals that need a security review
  • Cannot: See detailed findings unless granted; Add vendors to continuous monitoring without TPRM approval; Change tiers or thresholds
  • Approvals: Adding a vendor to continuous monitoring is approved by the TPRM manager.
  • Notified about: Ratings completed for their requests.

Moraph service team

Moraph managed service analyst, Moraph service delivery manager. Runs BitSight and the routine monitoring work on your behalf.

  • Sees: The portfolio, ratings, findings and alerts; Follow-up status and the monitoring record; BitSight administrative settings
  • Does: Loads and maintains the vendor portfolio and matches vendors to BitSight records; Triages alerts and records the classification; Prepares finding summaries for relationship owners; Checks and requests corrections to misattributed findings; Prepares portfolio reports and runs the monthly service review; Raises cases with BitSight support and tracks them
  • Cannot: Accept risk or decide what a finding means for the relationship; Change tiers or thresholds without approval; Contact your vendors except through the channel you agree
  • Approvals: Portfolio, tier and threshold changes follow requests approved by the TPRM manager.
  • Notified about: All BitSight alerts on the portfolio, and BitSight advisories.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access). Checks that vendors are monitored in proportion to their risk and that findings are followed up.

  • Sees: The portfolio, tiers and thresholds within scope; Alerts, triage decisions, follow-ups and risk acceptances; Portfolio reports and the monitoring record
  • Does: Selects vendors and alerts for testing; Reviews the evidence of follow-up; Exports reports within scope, with each export logged
  • Cannot: Change, approve or close anything; See vendors outside the scope granted
  • Approvals: Their access is approved by the TPRM manager, with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.

Permissions at a glance

ActionTPRM managerRel. ownerSecurityProcurementMoraph teamAuditor
View portfolio ratingsFullOwn workViewOwn workViewView
View detailed findingsFullOwn workView–ViewView
Add or remove monitored vendorsApproves––Own workFull–
Set tiers and alert thresholdsApproves–View–FullView
Triage alertsView–––FullView
Prepare finding summariesViewViewView–FullView
Record vendor responsesFullOwn workView–ViewView
Add technical assessmentViewViewFull––View
Accept risk on a findingApproves––––View
Request pre-contract ratingsFullOwn work–Own workFull–
View monitoring recordViewOwn workView–ViewView
Manage users and rolesApproves–––Own work–

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

How access is controlled

  • Moraph triages and prepares, your people decide: classification of an alert is Moraph's work, but escalation outcomes, closures and risk acceptance are your organization's decisions.
  • Relationship owners and procurement see only their own vendors unless your TPRM manager grants more.
  • Contact with vendors follows the channel you agree during implementation, usually through the relationship owner, so vendors hear from you rather than from a third party.
  • Access reviews list each person's role for certification by the TPRM manager, and auditors 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.