Platform Documentation

Fair TPRM & GRC Platform — Version 2.6.1

Platform Overview

Fair TPRM is a unified platform built around two integrated modules:

  • TPRM Module — Third-Party Risk Management for tracking, assessing, and scoring vendor relationships throughout their entire lifecycle.
  • GRC Module — Governance, Risk & Compliance for managing your organization’s compliance posture across multiple industry frameworks including SOC 2, ISO 27001, PCI DSS, NIST CSF, CMMC, HIPAA, CIS Controls, NIST 800-171, and the NIST AI Risk Management Framework.

Both modules share the same database, the same permission model, and the same audit log — eliminating data silos and duplicate work.

Key Concept — Unified Assessment: The GRC module uses a single set of 170+ security questions organized across 14 domains. Each question is mapped to requirements in all 9 supported compliance frameworks simultaneously, including the NIST AI Risk Management Framework. Answer once, and Fair TPRM calculates your compliance posture across every framework automatically.

User Roles & Permissions

Fair TPRM uses role-based access control (RBAC) with seven default ACL groups. Each user is assigned to one or more groups that determine which modules and actions they can access.

Group Access Level
Administrator Full access to all modules, settings, and administrative functions across the entire platform.
Cyber TPRM Full access to all TPRM module operations including vendor management, assessments, FAIR analysis, and SRS scoring.
Cyber GRC Full access to all GRC module operations including compliance assessments, controls, evidence, policies, audits, and the risk register.
GRC Contributors Limited access — can complete assigned tasks, provide evidence, and respond to assessment questions delegated to them.
Auditor Read-only access to both TPRM and GRC modules for audit and review purposes.
Procurement Access to vendor onboarding, contract management, and procurement documents within the TPRM module.
Stakeholder Access limited to vendors they own or have been assigned, including the ability to submit vendor requests.
Note: To see the GRC module in the sidebar, a user must belong to the Administrator, Cyber GRC, or Auditor group. Users outside these groups will not see GRC navigation items.

Your First Login

  1. Open your browser and navigate to your organization’s Fair TPRM URL (provided by your administrator).
  2. Enter your Username and Password on the login screen.
  3. If TOTP two-factor authentication is enabled for your account, enter the six-digit code from your authenticator app.
  4. After successful authentication you will land on the Dashboard page.
  5. In the sidebar, click GRC Module to expand its sections and begin working with compliance features.
The Fair TPRM platform dashboard after logging in
The platform dashboard after logging in, showing the TPRM and GRC modules.

What’s New in Version 2.6.1

Version 2.6.1 adds several features focused on vendor onboarding, procurement collaboration, multi-language support, and shadow-SaaS discovery. If you have used an earlier version (2.5.8), here is what is new. Each item links to its full walkthrough later in this guide.

New FeatureWhat It DoesWho It’s For
Language settingsUse the platform in 8 languages. Each person picks their own language; admins choose which languages are available.Everyone
Procurement Onboarding & Vendor IDA vendor must be onboarded through procurement and have a valid Vendor ID (VID) before it can be submitted for cyber review.Procurement, Stakeholders
AI Review for vendorsA dedicated review status for vendors whose services use AI, plus a “Force AI Review” action.Cyber TPRM, Admins
Procurement Cyber StatusA live page showing vendors in review, with a running history of updates the cyber team shares with procurement, plus a weekly email digest.Procurement, Cyber TPRM
Grip Security integrationAutomatically discover SaaS apps used across your organization and pull them into the Shadow SaaS list.Admins
Zscaler blockingBlock an unsanctioned app’s web domain directly in Zscaler with one click.Admins
In-app upgradesCheck your registry for a newer version and upgrade from inside the Admin Portal.Admins
How do I know which version I’m on? Administrators can go to AdminVersion to see the installed version. This guide describes v2.6.1. See Updating the Platform.

Changing Your Language New in 2.6.1

The platform interface can be displayed in 8 languages. Every person chooses their own language — changing it only affects your screen, not anyone else’s. Your choice is remembered every time you log in.

Languages available

LanguageShown in the menu as
EnglishEnglish
SpanishEspañol
ItalianItaliano
UkrainianУкраїнська
Chinese (Simplified)中文(简体)
Hindiहिन्दी
FrenchFrançais
PortuguesePortuguês
Only the languages your administrator has turned on will appear in your list. English is always available and cannot be turned off.

How to change your language

  1. Click Profile in the top-right corner of any page.
  2. On the Profile page, scroll down to the Language Preference card.
  3. Click the Language drop-down and choose your language. To go back to the language your administrator set for everyone, choose System default.
  4. Click Update Language. The page reloads and the menus, buttons, and labels now appear in your chosen language.
Language Preference card on the Profile page
Profile → Language Preference card.

For administrators: choosing which languages are available

Administrators control the organization-wide default language and the list of languages users may choose from. Go to AdminGeneral and use the Default Language and Enabled Languages settings. English is always enabled.

Default Language and Enabled Languages settings in Admin General
Default Language and Enabled Languages settings in Admin → General.

GRC Module Overview

GRC stands for Governance, Risk & Compliance. The GRC module helps your organization:

  • Assess security maturity across 14 domains using the unified questionnaire
  • Track compliance posture against 9 industry frameworks simultaneously
  • Manage internal controls and map them to framework requirements
  • Collect and encrypt compliance evidence with expiry tracking
  • Manage policies through their full lifecycle from draft to retirement
  • Plan and execute audits with finding tracking and remediation
  • Maintain a risk register with likelihood and impact scoring
  • Run continuous monitors to demonstrate ongoing compliance
Unified Questions: The GRC assessment engine contains 170+ questions organized across 14 security domains. Each question is mapped to requirements in multiple compliance frameworks. When you answer a question, your response automatically contributes to compliance scores for every mapped framework — no duplicate questionnaires required.

Getting Started with GRC — Quick Start

Follow this five-step workflow to complete your first GRC compliance assessment:

  1. Create an Assessment — Define the scope and select the assessment type.
  2. Answer Questions — Work through the 170+ unified questions across 14 security domains.
  3. Upload Evidence — Attach supporting documents and artifacts to your responses.
  4. View Compliance Scores — Review automatically calculated compliance percentages for each framework.
  5. Generate Reports — Export framework-specific compliance reports for stakeholders and auditors.
Prerequisites: You must belong to the Administrator or Cyber GRC group to create and manage assessments. Members of the GRC Contributors group can respond to questions assigned to them but cannot create new assessments.

Step 1: Create Your First Assessment

  1. In the sidebar, expand GRC ModuleAssessment & Audit → click Assessment Questionnaire.
  2. Click the Create Assessment button.
  3. Fill in the required fields:
  • Title — A descriptive name for the assessment (e.g., “Q1 2026 Annual Compliance Assessment”).
  • Assessment Type — Choose from five options: Initial Assessment, Annual Review, Gap Analysis, Remediation Validation, or Ad-Hoc Assessment.
  • Scope — Describe what the assessment covers (e.g., “Enterprise-wide security posture”).
  • Lead Auditor — Select the user who will lead the assessment.
  • Start Date and End Date — Define the assessment period.
Example:
Title: Q1 2026 Annual Compliance Assessment
Type: Annual Review
Scope: Enterprise-wide security posture across all business units
Lead Auditor: Jane Smith
Start Date: 2026-01-15
End Date: 2026-03-31

Assessment Statuses

Status Description
Draft Assessment has been created but questions have not been started.
In Progress Questions are actively being answered by the assessment team.
Under Review All questions answered; the lead auditor is reviewing responses.
Completed Assessment has been reviewed and finalized. Scores are locked.
Archived Assessment retained for historical reference. Read-only.
Assessment list on the Assessment Questionnaire page
The assessment list on the Assessment Questionnaire page.

Step 2: Answer Assessment Questions

The unified assessment contains 170+ questions organized across the following 14 security domains:

Code Domain Questions
GOVGovernance & Leadership12
IAMIdentity & Access Management14
DSPData Security & Privacy12
EPSEndpoint Security8
NETNetwork Security12
APSApplication Security9
OPSSecurity Operations12
INCIncident Management8
SCMSupply Chain Management7
PHYPhysical Security6
HRSHuman Resources Security8
BCPBusiness Continuity & DR11
CRYCryptography9
CMPCompliance & Audit8
Answering questions in the assessment questionnaire
Answering questions in the assessment questionnaire, organized by security domain.

Answering a Question

  1. Open the assessment and select a domain to begin answering questions.
  2. For each question, select a Maturity Rating from the four-tier scale:
  • 1 — Initial / Ad Hoc: Processes are reactive, undocumented, and inconsistently applied.
  • 2 — Developing: Processes are partially documented but not consistently followed.
  • 3 — Defined: Processes are fully documented and consistently implemented across the organization.
  • 4 — Managed / Optimized: Processes are measured, continuously improved, and aligned with industry best practices.

Conformity Status

Based on the maturity rating you select, the system determines a Conformity Status for each mapped framework requirement:

  • Conforming — The requirement is fully met (typically maturity 3 or 4).
  • Partial — The requirement is partially met (typically maturity 2).
  • Non-Conforming — The requirement is not met (typically maturity 1).
  • Not Applicable — The requirement does not apply to your organization’s scope.
How it works: The maturity rating you select drives the conformity status automatically. Higher maturity ratings produce “Conforming” statuses, while lower ratings produce “Partial” or “Non-Conforming” statuses. You can override the conformity status manually if needed.
Cross-Framework Mapping: Each question maps to requirements in multiple frameworks. When you rate a question, the conformity status is applied to every mapped requirement across all frameworks simultaneously. This means a single response can affect compliance scores for SOC 2, ISO 27001, PCI DSS, and others at the same time.

Step 3: Upload Evidence

Evidence files support your assessment responses and demonstrate compliance to auditors.

  1. While answering a question, click the Attach Evidence button next to the question.
  2. Select a file from your computer (supported formats include PDF, images, and documents).
  3. Add a Description and set the Expiry Date for the evidence.
  4. Click Upload to attach the evidence to the question.
Encryption: All uploaded evidence files are encrypted at rest using AES-256-CBC. Files are protected in transit by TLS 1.3 with post-quantum resistant cipher suites.

Evidence Library

All uploaded evidence is also accessible from the Evidence Library (sidebar → GRC Module → Evidence & Monitoring → Evidence Library). The library provides a centralized view of all evidence across the platform, with filtering by status, expiry date, and linked control or question.

Step 4: View Compliance Scores

  1. Navigate to GRC ModuleComplianceDashboard.
  2. The dashboard displays a card for each supported framework showing a donut chart with the current compliance percentage.
  3. Click any framework card to drill into its detailed compliance report.

Compliance Formula

Compliance % = (Conforming + Partial × 0.5) ÷ Applicable Requirements × 100

Requirements marked as “Not Applicable” are excluded from the denominator, ensuring your score reflects only relevant requirements.

Supported Frameworks

Framework Version Mapped Questions
NIST Cybersecurity Framework (CSF)2.0170+
ISO/IEC 270012022170+
SOC 2 Type II2017170+
PCI DSS4.0132
CMMC / NIST 800-171v2.097
CIS Controlsv895
NIST SP 800-171Rev 290
HIPAA Security Rule201361
NIST AI Risk Management Framework (AI RMF)1.048

Step 5: Generate a Framework Compliance Report

  1. From the Compliance Dashboard, click the framework card you want to report on.
  2. Click the Generate Report button at the top of the framework detail page.
  3. The report is generated and displayed in-browser. Use the Export PDF button to download a copy.

What Each Requirement Card Shows

The compliance report lists every requirement for the selected framework. Each requirement card displays:

  • Reference — The framework requirement identifier (e.g., CC6.1 for SOC 2, A.8.2 for ISO 27001).
  • Title — The requirement name or description.
  • Status Badge — Conforming, Partial, Non-Conforming, or Not Applicable.
  • Mapped Questions — Each linked unified question showing its maturity rating, conformity status, validation notes, and attached evidence.

CSF Maturity Score Dashboard

  1. In the sidebar, navigate to GRC ModuleAssessment & AuditCSF Maturity Score.
  2. Select an assessment from the dropdown to view its maturity scoring.

The CSF Maturity Score dashboard displays:

  • Overall FAIR Score — A single weighted score (1.0–4.0) representing your organization’s overall security maturity.
  • Radar Chart — A visual comparison of maturity scores across all 14 security domains.
  • Domain Score Cards — Individual maturity scores for each of the 14 domains with color-coded tier indicators.
  • Framework Compliance Bars — Horizontal bar charts showing compliance percentages for each supported framework.
  • Gap Analysis Summary — A breakdown of domains where maturity falls below your target threshold, with recommendations for improvement.
CSF Maturity Score dashboard with radar chart
The CSF Maturity Score dashboard with the radar chart across all 14 security domains.

Frameworks Page

  1. Navigate to GRC ModuleComplianceFrameworks.
  2. Select a framework from the list to view its requirement tree.

The Frameworks page displays the full requirement hierarchy for each supported framework. Requirements are organized in a tree view with expandable sections, domains, and individual requirements. Each requirement shows its conformity status and linked assessment questions.

Compliance Frameworks page with per-framework compliance cards
The Frameworks page with per-framework compliance cards.

Internal Controls

Internal controls document the security measures your organization has in place. Controls can be mapped to requirements across multiple frameworks simultaneously.

  1. Navigate to GRC ModuleComplianceControls.
  2. Click Add Control to create a new control.
  3. Fill in the control details:
  • Title — A descriptive name for the control.
  • Description — What the control does and how it is implemented.
  • Type — Preventive, Detective, or Corrective.
  • Category — Technical, Administrative, or Physical.
  • Status — Not Implemented, Partially Implemented, or Fully Implemented.
  • Effectiveness — Effective, Partially Effective, or Ineffective.
  • Risk Level — Low, Medium, High, or Critical.
  • Owner — The user responsible for maintaining this control.
  • Test Frequency — How often the control is tested (e.g., Monthly, Quarterly, Annually).
  • Framework Mapping — Select which framework requirements this control satisfies.
Cross-Framework Mapping: A single control can be mapped to requirements in multiple frameworks. For example, an access review control might satisfy SOC 2 CC6.1, ISO 27001 A.9.2.5, and PCI DSS 7.1 simultaneously.

Framework Crosswalk

The crosswalk tool lets you compare coverage between any two supported frameworks to identify gaps and overlaps.

  1. Navigate to GRC ModuleComplianceCrosswalk.
  2. Select a Source Framework from the first dropdown (e.g., SOC 2).
  3. Select a Target Framework from the second dropdown (e.g., ISO 27001).
  4. The crosswalk displays a side-by-side mapping showing which source requirements map to target requirements, and highlights any gaps where the target framework has requirements not covered by the source.

Evidence Library

The Evidence Library provides a centralized view of all compliance evidence uploaded across the platform.

  1. Navigate to GRC ModuleEvidence & MonitoringEvidence Library.
  2. Click Upload Evidence to add a new evidence file.
  3. Fill in the Title, Description, Expiry Date, and optionally link the evidence to a control or assessment question.
  4. Select the file and click Upload.

Evidence Statuses

Status Description
Current Evidence is valid and within its expiry date.
Expired Evidence has passed its expiry date and needs to be renewed.
Superseded Evidence has been replaced by a newer version.
Draft Evidence has been uploaded but not yet approved or finalized.

Policy Management

The Policy Management feature lets you create, review, approve, and publish organizational policies with version tracking and periodic review scheduling.

  1. Navigate to GRC ModulePolicy ManagementPolicies.
  2. Click Create Policy to add a new policy.
  3. Fill in the policy details:
  • Title — The policy name (e.g., “Acceptable Use Policy”).
  • Category — The policy category (e.g., Information Security, Access Control, Data Privacy).
  • Review Frequency — How often the policy should be reviewed (e.g., Annually, Semi-Annually).
  • Content — The full policy text, entered in the rich text editor.

Policy Lifecycle

DraftReviewApprovedPublishedRetired

Audits & Findings

The Audits feature supports your internal and external audit processes from planning through remediation and closure.

  1. Navigate to GRC ModuleAssessment & AuditAudits.
  2. Click Create Audit to start a new audit.
  3. Define the audit scope, assign the audit lead, and set the timeline.
  4. During fieldwork, record findings using the Add Finding button. Each finding includes a title, description, severity rating, affected control, and recommended remediation.
  5. Assign remediation tasks to responsible parties and track progress through to closure.

Audit Statuses

Status Description
Planning Audit scope and resources are being defined.
Fieldwork Audit testing and evidence collection are underway.
Reporting Findings are being documented and the audit report is being drafted.
Remediation Findings have been reported and remediation tasks are in progress.
Closed All findings have been resolved and the audit is finalized.

Risk Register

The Risk Register tracks organizational risks with quantified likelihood and impact scoring.

  1. Navigate to GRC ModuleAssessment & AuditRisk Register.
  2. Click Add Risk to create a new risk entry.
  3. Fill in the risk details:
  • Title — A concise name for the risk.
  • Description — A detailed description of the risk scenario.
  • Category — The risk category (e.g., Operational, Technical, Compliance, Strategic).
  • Likelihood — Probability of occurrence on a 1–5 scale.
  • Impact — Severity of consequences on a 1–5 scale.
  • Treatment Strategy — Accept, Mitigate, Transfer, or Avoid.

The Inherent Risk Score is calculated as Likelihood × Impact (range 1–25) before controls are applied. The Residual Risk Score is recalculated after treatment controls are linked, reflecting the remaining risk after mitigation measures are in place.

Continuous Monitors

Continuous monitors run automated compliance checks on a scheduled basis to demonstrate ongoing compliance to auditors.

  1. Navigate to GRC ModuleEvidence & MonitoringContinuous Monitors.
  2. Click Create Monitor to define a new monitor.
  3. Fill in the monitor details:
  • Title — A descriptive name for the monitor.
  • Check Type — The type of check to perform (e.g., Certificate Expiry, DNS Configuration, Policy Review Due).
  • Frequency — How often the monitor runs (Hourly, Daily, Weekly, or Monthly).
  • Collector Configuration — The technical configuration for the data collection method, including target endpoints and thresholds.

Task Inbox

The Task Inbox shows all GRC tasks assigned to the currently logged-in user. Tasks are generated when assessment questions or remediation items are delegated to you.

  1. Navigate to GRC ModuleAssessment & AuditTask Inbox.
  2. Review your assigned tasks, which include the task type, due date, and priority.
  3. Click a task to open it, complete the required action (answer a question, upload evidence, or confirm remediation), and mark it as done.

GRC Dashboard

The GRC Dashboard provides a single-pane-of-glass view across your entire compliance program. It displays:

  • Framework Compliance Heatmap — Color-coded compliance scores for all 9 frameworks at a glance.
  • Control Implementation Progress — Percentage of controls that are fully implemented, partially implemented, and not implemented.
  • Evidence Freshness — Visual indicator of how many evidence items are current, approaching expiry, or expired.
  • Open Findings — Count of unresolved audit findings grouped by severity (Critical, High, Medium, Low).
  • Policy Review Status — Policies due for review, overdue, and recently reviewed.
  • Monitor Health — Pass/fail status of all continuous monitors with trend indicators.
  • Risk Register Summary — Distribution of risks by treatment strategy and current risk levels.

TPRM Module Overview

The TPRM (Third-Party Risk Management) module provides end-to-end vendor risk management. It allows you to track and assess vendors, assign risk tiers, send security assessments, perform FAIR risk quantification, monitor 4th party dependencies, and discover Shadow SaaS applications across your organization.

For detailed information about TPRM capabilities, visit the Vendor Lifecycle and FAIR Analysis pages.

Adding a New Vendor

To add a vendor, navigate to the TPRM Module in the sidebar and click Add Vendor. Complete the required fields including Vendor Name, Domain, Type, Tier, contact information, and data handling details such as PII Count and SPII Count (the number of personally identifiable and sensitive personally identifiable information records the vendor will access).

Vendor Tiers: Vendors are classified into three tiers based on risk. Tier 1 vendors are critical (highest risk, most oversight), Tier 2 vendors are significant (moderate risk), and Tier 3 vendors are low-risk (minimal data access or business impact).

Vendor Lifecycle

Every vendor follows a defined lifecycle from initial request through offboarding. The status flow is:

DraftPending ReviewIn ReviewApproved / RejectedActiveAnnual ReviewOffboarded

Each transition is logged in the audit trail, and automated notifications can be configured for status changes. See the Vendor Lifecycle page for full details.

Vendor Assessments

Security assessments can be sent directly to vendors through the platform. The vendor receives an email with a secure link to complete the questionnaire. Responses are automatically scored and integrated into the vendor’s risk profile. Assessments can be customized by tier, and follow-up assessments can be triggered based on scoring results.

Security Risk Scorecard (SRS)

The SRS provides an external security score for each vendor based on automated scanning of their public-facing infrastructure. Scoring categories include DNS configuration, SSL/TLS certificate health, email security (SPF, DKIM, DMARC), and open port exposure. Signal weights are fully configurable by administrators. See the Monitoring page for details.

FAIR Analysis

Fair TPRM implements the FAIR (Factor Analysis of Information Risk) quantitative risk model to estimate the financial impact of vendor-related security incidents. The analysis produces an Annualized Loss Expectancy (ALE) and recommended cyber insurance coverage. All multipliers and thresholds are configurable. Visit the FAIR Analysis page for a complete overview.

4th Party Risk

Fourth-party risk tracking lets you identify and monitor your vendors’ vendors — the downstream dependencies that could affect your organization. The platform maps these sub-service relationships and flags concentration risk when multiple vendors rely on the same fourth party.

Shadow SaaS Discovery

Shadow SaaS discovery identifies unapproved SaaS applications in use across your organization. The feature detects cloud services that have not been formally onboarded through the TPRM process, enabling your security team to assess risk, enforce governance, and bring shadow applications under management. In v2.6.1, discovery can be automated with the Grip Security integration, and unsanctioned apps can be blocked through Zscaler.

Shadow SaaS list page
The Shadow SaaS list with discovered apps, risk scores, and per-app actions.

Vendor Onboarding & Procurement Onboarding New in 2.6.1

A vendor onboarding request is how a new vendor enters the platform. It moves through a series of statuses from first draft to final decision. Before the cyber team will review a vendor, the vendor must first be onboarded through your procurement process and have a valid Vendor ID (VID).

The onboarding journey (statuses)

StatusWhat it means
DraftThe request is being filled in. It has not been sent for review yet.
SubmittedThe request passed the submission checks and has been sent to the cyber team.
In ReviewThe cyber team is reviewing the vendor.
AI ReviewThe vendor’s services use AI and it is in the dedicated AI review stage (see AI Review).
EvaluationThe vendor is being trialled or evaluated.
ApprovedThe vendor has been approved and is onboarded.
RejectedThe vendor was not approved.
InactiveThe vendor is no longer active.

Finding your vendor requests

Go to TPRM ModuleStakeholdersVendor Onboarding. You will see a searchable list of vendors with their status, tier, security score (SRS), and quick actions. Use the filter pills at the top (for example All, Approved, Review) to narrow the list, or click + New Request to start a new vendor. The Review pill combines both In Review and AI Review vendors.

Vendor Onboarding Requests list
The Vendor Onboarding list — search, filter pills, and per-vendor actions.

The two things every vendor needs before review

Open a vendor and look at the Vendor Information card. Two fields control whether the vendor can be submitted for cyber review:

  • Procurement Onboarding — a Yes/No field answering “Has this vendor completed Procurement Onboarding?” This must be set to Yes.
  • Vendor ID (VID) — the 4–8 digit identifier assigned to the vendor by your procurement system. This must be a valid 4–8 digit number.
Vendor Information card showing Procurement Onboarding and Vendor ID fields
The Vendor Information card — Vendor ID (VID) and Procurement Onboarding must both be set before the vendor can be submitted.
Upgrading from 2.5.8? On instances upgraded from an earlier release the procurement field may still read “VSU Onboarded”; in v2.6.1 it is labelled Procurement Onboarding — it is the same field.

AI Review for Vendors New in 2.6.1

Some vendors provide services that use artificial intelligence. These vendors can carry different risks, so v2.6.1 adds a dedicated AI Review status to track them separately during the review process.

How a vendor enters AI Review

On the Vendor Information card there is a Services Use AI field. When this is set to Yes, an authorized reviewer (a Cyber TPRM user or Administrator, while editing the vendor) sees a Force AI Review link directly beneath that field.

  1. Open the vendor and confirm Services Use AI is set to Yes.
  2. Click Force AI Review and confirm the prompt: “Force this vendor into AI Review?”
  3. The vendor’s status changes to AI Review.
Vendor dashboard in AI Review status with Services Use AI and Vendor ID fields
A vendor in AI Review — note Services Use AI: Yes, the Vendor ID (VID), and the AI REVIEW status badge.
Why might the link not appear? The Force AI Review link only shows when (1) you have permission to approve, (2) you are in edit mode, (3) Services Use AI is Yes, and (4) the vendor is not already in AI Review. If Services Use AI is “No”, you will see “AI Review can only be forced for vendors whose services use AI.”

Procurement Cyber Status New in 2.6.1

The Cyber Status page gives the procurement team a simple, always-current view of which vendors the cyber team is reviewing and what the latest word is on each one — without needing access to the full security tooling. The cyber team posts short, dated updates; procurement reads them here (and in a weekly email). Open it from TPRM ModuleProcurementCyber Status. It is available to Procurement, Cyber TPRM, and Administrator users.

Procurement Cyber Status page
Procurement → Cyber Status lists every vendor whose status is In Review or AI Review, with the update count and latest update date.

Reading a vendor’s update history

Click a vendor’s name in the Vendors in Review table. The Procurement Update History panel opens, showing every update newest-first: the date and time, who wrote it, the vendor’s status at that time, and the note itself.

Procurement Update History for a vendor in review
A vendor’s Procurement Update History — each entry shows date, author, status badge, and the cyber team’s note.

For cyber reviewers: posting an update to procurement

  1. On the Cyber Status page, tick the checkbox next to each vendor you want to update.
  2. Click Provide Procurement with Update.
  3. Type your note in the Update box.
  4. Optionally use Change status to move the vendor(s) forward (for example to Evaluation, Approved, or Rejected). Leave it on Keep current status to only add a note.
  5. Click Save Update. The update is recorded against every selected vendor.

The weekly procurement digest email

A scheduled job emails procurement a weekly digest summarizing vendors in review and their latest updates. Administrators manage it from AdminScheduler via the Procurement Update Digest job.

Admin Scheduler showing the Procurement Update Digest job
Admin → Scheduler — the Procurement Update Digest job that sends the weekly email.

Grip Security Integration (Shadow SaaS) New in 2.6.1

“Shadow SaaS” means cloud apps that employees use which were never formally approved. Grip Security is a service that discovers these apps. In v2.6.1 you can connect your Grip account so the platform automatically pulls in the apps Grip finds — along with how many people use each one, a risk score, and security alerts — and lists them on your Shadow SaaS page. It is configured by an administrator at AdminShadow SaaS.

Connecting Grip

  1. In Grip, create an API token and note your tenant’s base URL (it ends in /public/saas, for example https://acme.dep.grip.security/public/saas).
  2. In the platform, go to AdminShadow SaaS and find the Grip Security Connection card.
  3. Tick Enable Grip Security integration.
  4. Paste your tenant URL into Server (Tenant Base URL) and your token into API Token.
  5. Click Save Configuration, then Test Connection to confirm.
Grip Security Connection settings
Admin → Shadow SaaS → Grip Security Connection — enter your tenant URL and API token, save, then test.

Keeping it up to date automatically

Use the Scheduled Rehydration card to have the platform refresh Grip data on a schedule. Tick Enable scheduled rehydration via cron and choose a Run frequency (Hourly, Every 6 hours, Every 12 hours, Daily, or Weekly). You can also click Run Now to refresh immediately.

Scheduled Rehydration settings for Grip
Scheduled Rehydration — choose how often Grip data refreshes, or click Run Now for an immediate sync.

Zscaler Blocking Integration New in 2.6.1

Zscaler is a web-security service that can block access to websites. With this integration, when you Deny an unsanctioned app on the Shadow SaaS page, the platform can automatically add that app’s web domain to a blocking list (URL Category) in your Zscaler account — so people can no longer reach it. Clicking Allow later removes the block. It is configured by an administrator at AdminShadow SaaS, on the Zscaler Connection card.

Connecting Zscaler

  1. In Zscaler (ZIdentity), create an API Client and copy its Client ID and Client Secret. Note your vanity domain (the part before .zslogin.net).
  2. In ZIA, create (or pick) a custom URL Category that the blocked domains will be added to, and note its exact name.
  3. In the platform’s Zscaler Connection card, tick Enable Zscaler URL-Category blocking on Deny.
  4. Fill in API URL (default https://api.zsapi.net), ZIdentity Vanity Domain, Client ID, Client Secret, and the URL Category name.
  5. Click Save Configuration, then Test Connection to confirm the credentials work.
Zscaler Connection settings
Admin → Shadow SaaS → Zscaler Connection — the named URL Category must already exist in Zscaler.
If blocking is turned off, denying an app only marks it as denied inside the platform — no change is made in Zscaler.

General Settings

The General Settings page (Admin → Settings → General) allows administrators to configure core platform settings including the Application Name, Company Name, and Support Email address. These values appear throughout the platform interface and in system-generated emails.

Branding & Theme

Customize the platform’s appearance from Admin → Settings → Branding. Upload your organization’s logo, set primary and accent colors, and adjust the sidebar navigation width. Branding changes take effect immediately for all users.

User Management

Manage user accounts from Admin → Users. Administrators can create new users, assign them to one or more ACL groups, enable or disable TOTP two-factor authentication, and deactivate accounts. Group membership determines which modules and actions each user can access.

  1. Navigate to AdminUsers.
  2. Click a user to edit, or click Add User to create a new account.
  3. In the ACL Groups section, check the groups this user should belong to.
  4. Click Save to apply changes.

Email Configuration

Configure outbound email from Admin → Settings → Email. Enter your SMTP server details including host, port, encryption method (TLS/SSL), username, and password. The platform uses email for vendor assessment invitations, task notifications, password resets, and audit reminders.

SAML / SSO

Fair TPRM supports SAML 2.0 single sign-on for enterprise identity providers. Configure SSO from Admin → Settings → SAML. You will need to provide the IdP Entity ID, SSO URL, SLO URL, and X.509 certificate from your identity provider. SCIM 2.0 provisioning is also supported for automated user lifecycle management.

AI Integration

Fair TPRM offers optional AI-powered features for generating executive risk summaries, suggesting control descriptions, and analyzing assessment gaps. Configure AI integration from Admin → Settings → AI. The platform supports integration with compatible AI services, and all AI features can be enabled or disabled individually.

Recommended: Self-Host OpenWebUI or LibreChat

For full control over your AI integration, we recommend self-hosting OpenWebUI or LibreChat alongside Fair TPRM. Both are free, open-source AI front-ends that run as a single Docker container and are compatible with Fair TPRM’s AI integration settings.

Why self-host AI? Your vendor risk data, FAIR analyses, and compliance assessments stay on your infrastructure. No data is sent to third-party services unless you explicitly configure an external LLM provider. You can even run fully local models via Ollama for a completely air-gapped setup.

Setup overview:

  1. Deploy OpenWebUI or LibreChat — Run the Docker image on the same server as Fair TPRM or on a separate host. Both support Docker Compose for easy deployment.
  2. Configure an LLM provider — Connect to OpenAI, Anthropic, a local Ollama instance, or any OpenAI-compatible API endpoint.
  3. Point Fair TPRM to your AI service — In Admin → Settings → AI, enter the URL of your self-hosted AI instance and your API key.
  4. Enable AI features — Toggle individual AI capabilities: executive summaries, control suggestions, and gap analysis.

Cost: $0 for self-hosted OpenWebUI or LibreChat. If using a cloud LLM provider, costs depend on your API usage (typically a few dollars per month for moderate use). Fully local models via Ollama are completely free.

Security Rating Services: Shodan API

For continuous external security scoring, Fair TPRM integrates with the Shodan API. A Shodan membership (approximately $59/month) gives Fair TPRM automated Security Rating Scores for your entire vendor portfolio — including TLS analysis, CVE detection, network security, and application hardening.

Configure the Shodan API key in Admin → Settings → SRS. Shodan is automatically provisioned for free during the hosted demo.

Total cost of ownership: Fair TPRM ($0) + self-hosted AI ($0) + Shodan API (~$59/month) = a complete TPRM & GRC platform with AI-powered analysis and continuous security monitoring for under $60/month. Compare that to commercial TPRM platforms that charge $50,000–$200,000+ per year.

Updating the Platform New in 2.6.1

Administrators can check for and apply new versions from inside the platform. Navigate to AdminVersion.

  1. The Current Status card shows your Installed Version and whether a newer one is available.
  2. Confirm the Registry Hostname is correct (your image registry), then click Check for Updates.
  3. If a newer version is listed, follow the on-screen Upgrade action to apply it.
Version Management page showing installed version 2.6.1
Admin → Version — here the installed version is v2.6.1 and the platform reports it is up to date. This is also where you confirm which version this guide applies to.

Glossary

Term Definition
ACLAccess Control List — defines which permissions are granted to each user group.
AI ReviewA dedicated vendor review status (new in v2.6.1) for vendors whose services use artificial intelligence; entered via the “Force AI Review” action.
AssessmentA structured evaluation of security maturity using the 170+ unified questions across 14 domains.
CIS ControlsCenter for Internet Security Controls — a set of prioritized cybersecurity best practices (v8 supported).
CMMCCybersecurity Maturity Model Certification — a US Department of Defense framework for contractor security.
Conformity StatusThe compliance state of a requirement: Conforming, Partial, Non-Conforming, or Not Applicable.
ControlA security measure implemented to mitigate risk, mapped to one or more framework requirements.
CrosswalkA mapping between two compliance frameworks showing how requirements in one correspond to requirements in another.
CSFCybersecurity Framework — refers to the NIST Cybersecurity Framework used for maturity scoring.
DomainOne of 14 security categories (e.g., GOV, IAM, DSP) that organize the unified assessment questions.
EvidenceDocuments, screenshots, or artifacts uploaded to support assessment responses and demonstrate compliance.
FAIRFactor Analysis of Information Risk — a methodology developed by the FAIR Institute for quantifying cyber risk in financial terms.
FairScoreThe overall weighted maturity score (1.0–4.0) calculated from assessment responses across all 14 domains.
FindingA gap or deficiency identified during an audit that requires remediation.
FrameworkA compliance standard (e.g., SOC 2, ISO 27001) with a defined set of requirements that the platform maps to unified questions.
GRCGovernance, Risk & Compliance — the module for managing internal compliance across multiple frameworks.
Grip SecurityA SaaS-discovery service that can be connected (new in v2.6.1) to automatically populate the Shadow SaaS list with apps used across your organization.
HIPAAHealth Insurance Portability and Accountability Act — US healthcare data privacy and security regulation.
ISO 27001International standard for information security management systems (2022 edition supported).
Maturity RatingA 1–4 score assigned to each assessment question: 1 (Initial), 2 (Developing), 3 (Defined), 4 (Managed/Optimized).
NIST 800-171NIST Special Publication 800-171 — security requirements for protecting Controlled Unclassified Information (CUI).
NIST AI RMFNIST AI Risk Management Framework — a framework for managing risks associated with artificial intelligence systems throughout their lifecycle.
PCI DSSPayment Card Industry Data Security Standard — requirements for organizations handling credit card data (v4.0 supported).
PIIPersonally Identifiable Information — data that can identify an individual (name, email, SSN, etc.).
Procurement OnboardingA Yes/No vendor field (new in v2.6.1, formerly “VSU Onboarded”) confirming a vendor has been onboarded through procurement before it can be submitted for cyber review.
RequirementA specific control objective or security measure defined by a compliance framework.
Shadow SaaSCloud applications used within an organization that were never formally approved or onboarded; discoverable via the Shadow SaaS page and the Grip integration.
SOC 2Service Organization Control 2 — an auditing framework for service providers based on Trust Services Criteria.
SPIISensitive Personally Identifiable Information — a subset of PII that requires heightened protection (SSN, financial data, health records).
TPRMThird-Party Risk Management — the module for managing vendor risk throughout the vendor lifecycle.
Unified QuestionOne of 170+ security questions in the assessment engine, each mapped to requirements across multiple compliance frameworks.
Vendor ID (VID)A 4–8 digit identifier assigned to a vendor by your procurement system. A valid VID (new requirement in v2.6.1) is required before a vendor can be submitted for cyber review.
ZscalerA web-security service that can be connected (new in v2.6.1) so that denying a Shadow SaaS app automatically blocks its domain via a Zscaler URL Category.

Free & Open Source

Fair TPRM is free software for the world to download and self-host. Security teams with limited budgets can deploy full TPRM and GRC capabilities at no cost. Try the live demo or clone the repository and deploy on your own infrastructure.

Demo Download Source