Fair TPRM & GRC Platform — Version 2.6.1
Fair TPRM is a unified platform built around two integrated modules:
Both modules share the same database, the same permission model, and the same audit log — eliminating data silos and duplicate work.
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. |
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 Feature | What It Does | Who It’s For |
|---|---|---|
| Language settings | Use the platform in 8 languages. Each person picks their own language; admins choose which languages are available. | Everyone |
| Procurement Onboarding & Vendor ID | A 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 vendors | A dedicated review status for vendors whose services use AI, plus a “Force AI Review” action. | Cyber TPRM, Admins |
| Procurement Cyber Status | A 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 integration | Automatically discover SaaS apps used across your organization and pull them into the Shadow SaaS list. | Admins |
| Zscaler blocking | Block an unsanctioned app’s web domain directly in Zscaler with one click. | Admins |
| In-app upgrades | Check your registry for a newer version and upgrade from inside the Admin Portal. | Admins |
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.
| Language | Shown in the menu as |
|---|---|
| English | English |
| Spanish | Español |
| Italian | Italiano |
| Ukrainian | Українська |
| Chinese (Simplified) | 中文(简体) |
| Hindi | हिन्दी |
| French | Français |
| Portuguese | Português |
Administrators control the organization-wide default language and the list of languages users may choose from. Go to → and use the Default Language and Enabled Languages settings. English is always enabled.
GRC stands for Governance, Risk & Compliance. The GRC module helps your organization:
Follow this five-step workflow to complete your first GRC compliance assessment:
| 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. |
The unified assessment contains 170+ questions organized across the following 14 security domains:
| Code | Domain | Questions |
|---|---|---|
| GOV | Governance & Leadership | 12 |
| IAM | Identity & Access Management | 14 |
| DSP | Data Security & Privacy | 12 |
| EPS | Endpoint Security | 8 |
| NET | Network Security | 12 |
| APS | Application Security | 9 |
| OPS | Security Operations | 12 |
| INC | Incident Management | 8 |
| SCM | Supply Chain Management | 7 |
| PHY | Physical Security | 6 |
| HRS | Human Resources Security | 8 |
| BCP | Business Continuity & DR | 11 |
| CRY | Cryptography | 9 |
| CMP | Compliance & Audit | 8 |
Based on the maturity rating you select, the system determines a Conformity Status for each mapped framework requirement:
Evidence files support your assessment responses and demonstrate compliance to auditors.
All uploaded evidence is also accessible from the (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.
Requirements marked as “Not Applicable” are excluded from the denominator, ensuring your score reflects only relevant requirements.
| Framework | Version | Mapped Questions |
|---|---|---|
| NIST Cybersecurity Framework (CSF) | 2.0 | 170+ |
| ISO/IEC 27001 | 2022 | 170+ |
| SOC 2 Type II | 2017 | 170+ |
| PCI DSS | 4.0 | 132 |
| CMMC / NIST 800-171 | v2.0 | 97 |
| CIS Controls | v8 | 95 |
| NIST SP 800-171 | Rev 2 | 90 |
| HIPAA Security Rule | 2013 | 61 |
| NIST AI Risk Management Framework (AI RMF) | 1.0 | 48 |
The compliance report lists every requirement for the selected framework. Each requirement card displays:
The CSF Maturity Score dashboard displays:
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.
Internal controls document the security measures your organization has in place. Controls can be mapped to requirements across multiple frameworks simultaneously.
The crosswalk tool lets you compare coverage between any two supported frameworks to identify gaps and overlaps.
The Evidence Library provides a centralized view of all compliance evidence uploaded across the platform.
| 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. |
The Policy Management feature lets you create, review, approve, and publish organizational policies with version tracking and periodic review scheduling.
Draft → Review → Approved → Published → Retired
The Audits feature supports your internal and external audit processes from planning through remediation and closure.
| 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. |
The Risk Register tracks organizational risks with quantified likelihood and impact scoring.
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 run automated compliance checks on a scheduled basis to demonstrate ongoing compliance to auditors.
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.
The GRC Dashboard provides a single-pane-of-glass view across your entire compliance program. It displays:
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.
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).
Every vendor follows a defined lifecycle from initial request through offboarding. The status flow is:
Draft → Pending Review → In Review → Approved / Rejected → Active → Annual Review → Offboarded
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.
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.
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 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.
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 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.
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).
| Status | What it means |
|---|---|
| Draft | The request is being filled in. It has not been sent for review yet. |
| Submitted | The request passed the submission checks and has been sent to the cyber team. |
| In Review | The cyber team is reviewing the vendor. |
| AI Review | The vendor’s services use AI and it is in the dedicated AI review stage (see AI Review). |
| Evaluation | The vendor is being trialled or evaluated. |
| Approved | The vendor has been approved and is onboarded. |
| Rejected | The vendor was not approved. |
| Inactive | The vendor is no longer active. |
Go to → → . 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.
Open a vendor and look at the Vendor Information card. Two fields control whether the vendor can be submitted for cyber review:
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.
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.
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 → → . It is available to Procurement, Cyber TPRM, and Administrator users.
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.
A scheduled job emails procurement a weekly digest summarizing vendors in review and their latest updates. Administrators manage it from → via the Procurement Update Digest job.
“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 → .
/public/saas, for example https://acme.dep.grip.security/public/saas).
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.
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 → , on the Zscaler Connection card.
.zslogin.net).https://api.zsapi.net), ZIdentity Vanity Domain, Client ID, Client Secret, and the URL Category name.
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.
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.
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.
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.
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.
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.
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.
Setup overview:
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.
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.
Administrators can check for and apply new versions from inside the platform. Navigate to → .
| Term | Definition |
|---|---|
| ACL | Access Control List — defines which permissions are granted to each user group. |
| AI Review | A dedicated vendor review status (new in v2.6.1) for vendors whose services use artificial intelligence; entered via the “Force AI Review” action. |
| Assessment | A structured evaluation of security maturity using the 170+ unified questions across 14 domains. |
| CIS Controls | Center for Internet Security Controls — a set of prioritized cybersecurity best practices (v8 supported). |
| CMMC | Cybersecurity Maturity Model Certification — a US Department of Defense framework for contractor security. |
| Conformity Status | The compliance state of a requirement: Conforming, Partial, Non-Conforming, or Not Applicable. |
| Control | A security measure implemented to mitigate risk, mapped to one or more framework requirements. |
| Crosswalk | A mapping between two compliance frameworks showing how requirements in one correspond to requirements in another. |
| CSF | Cybersecurity Framework — refers to the NIST Cybersecurity Framework used for maturity scoring. |
| Domain | One of 14 security categories (e.g., GOV, IAM, DSP) that organize the unified assessment questions. |
| Evidence | Documents, screenshots, or artifacts uploaded to support assessment responses and demonstrate compliance. |
| FAIR | Factor Analysis of Information Risk — a methodology developed by the FAIR Institute for quantifying cyber risk in financial terms. |
| FairScore | The overall weighted maturity score (1.0–4.0) calculated from assessment responses across all 14 domains. |
| Finding | A gap or deficiency identified during an audit that requires remediation. |
| Framework | A compliance standard (e.g., SOC 2, ISO 27001) with a defined set of requirements that the platform maps to unified questions. |
| GRC | Governance, Risk & Compliance — the module for managing internal compliance across multiple frameworks. |
| Grip Security | A 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. |
| HIPAA | Health Insurance Portability and Accountability Act — US healthcare data privacy and security regulation. |
| ISO 27001 | International standard for information security management systems (2022 edition supported). |
| Maturity Rating | A 1–4 score assigned to each assessment question: 1 (Initial), 2 (Developing), 3 (Defined), 4 (Managed/Optimized). |
| NIST 800-171 | NIST Special Publication 800-171 — security requirements for protecting Controlled Unclassified Information (CUI). |
| NIST AI RMF | NIST AI Risk Management Framework — a framework for managing risks associated with artificial intelligence systems throughout their lifecycle. |
| PCI DSS | Payment Card Industry Data Security Standard — requirements for organizations handling credit card data (v4.0 supported). |
| PII | Personally Identifiable Information — data that can identify an individual (name, email, SSN, etc.). |
| Procurement Onboarding | A 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. |
| Requirement | A specific control objective or security measure defined by a compliance framework. |
| Shadow SaaS | Cloud applications used within an organization that were never formally approved or onboarded; discoverable via the Shadow SaaS page and the Grip integration. |
| SOC 2 | Service Organization Control 2 — an auditing framework for service providers based on Trust Services Criteria. |
| SPII | Sensitive Personally Identifiable Information — a subset of PII that requires heightened protection (SSN, financial data, health records). |
| TPRM | Third-Party Risk Management — the module for managing vendor risk throughout the vendor lifecycle. |
| Unified Question | One 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. |
| Zscaler | A 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. |
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.