Digital Trust Portal
The Digital Trust Portal is the external-facing part of the DigitalXForce platform, with shareable posture dashboards for boards, regulators and customers. The Digital Trust Score is DigitalXForce’s composite score from 300 to 850, computed continuously from live control evidence across seven sub-postures: security, compliance, audit, resilience, third-party, AI and risk. The portal shows that score and its seven sub-postures, so a board, a regulator or a customer reads the same evidence-based picture. It is built for CISOs and risk leaders who report posture outside the security team.
What the portal shows
The portal surfaces the composite score and its seven sub-postures: security, compliance, audit, resilience, third-party, AI and risk. Each one is computed from live control evidence. No sub-posture is scored from self-attestation.
Each sub-posture measures one area of trust.
| Sub-posture | What it measures |
|---|---|
| Security | It covers control validation, attacker exposure, identity, and detection and containment. |
| Compliance | It covers risk assessment maturity, certifications, policy governance and evidence readiness. |
| Audit | It covers SOX and ITGC maturity, evidence lineage, automated audit execution and findings. |
| Resilience | It covers BIA confidence, BCP and DRP recoverability, crisis readiness and testing. |
| Third-party | It covers vendor governance, critical vendor coverage, assessment freshness and contractual enforcement. |
| AI | It covers the AI inventory, model and use-case risk, data sensitivity exposure and human oversight. |
| Risk | It covers residual risk, concentration, velocity and aging, and treatment effectiveness. |
The score sits in one of five bands.
| Band | Score range |
|---|---|
| High Trust | 780 to 850 |
| Trusted, Watchful | 700 to 779 |
| Conditional Trust | 620 to 699 |
| Low Trust | 500 to 619 |
| Trust at Risk | 300 to 499 |
The score updates as the evidence changes, so a posture in the portal is never older than the last evidence the platform read.
Who reads the portal
The portal is built for boards, regulators and customers, and the live FAQ adds insurers. Each of them reads it for a different decision.
- A board or audit committee reads one score and its seven sub-postures where it would otherwise read an anecdotal and stale risk report.
- A regulator is one of the readers the shareable dashboards are built for.
- A customer is another of the readers the shareable dashboards are built for.
- An insurer is a reader the live FAQ names, and the Cyber Risk and Liability Insurance module translates the platform’s posture data into the inputs underwriters require.
What DigitalXForce shares and what it keeps
DigitalXForce never publishes a customer’s score. The weights and the scoring logic are DigitalXForce’s intellectual property and are not published.
XForce GPT is the DigitalXForce generative AI engine that writes: it produces the plain-language risk narratives and board-ready reports, generates policies, standards and plans, and runs the embedded assistant. XForce GPT writes the board-ready risk reports from AI JedAI’s analysis.
How the portal fits the platform
TRiSCM™, or Trust, Risk, Security and Compliance Management, is a category of enterprise software defined by DigitalXForce that converges automated governance, risk and compliance with security posture management into a single real-time system, replacing periodic control validation with continuous control assurance. The Digital Trust Portal is one module of the DigitalXForce platform in that category.
The 15 DigitalXForce modules share one data layer, so a failed control result reaches the compliance view, the posture view and the risk register at the same time. The portal is one of those 15 modules.
X-SPM is Extended Security Posture Management, the DigitalXForce capability that scores security posture across the enterprise and its vendors from the same control data.
X-ROC, the XForce Risk Operations Center, is the operations layer of the DigitalXForce TRiSCM platform, where control failures, risk changes and vendor events are alerted, triaged, escalated and reported. X-ROC never changes a customer’s systems on its own, and the customer’s team makes each change.
Integrations the portal uses
The portal surfaces what the platform already holds. That evidence comes in through 250+ technology integrations, and the integrations page lists the current connectors.
Frameworks the portal supports
The compliance sub-posture covers risk assessment maturity, certifications, policy governance and evidence readiness. The audit sub-posture covers SOX and ITGC maturity, evidence lineage, automated audit execution and findings. DigitalXForce maps each control once across 50+ compliance frameworks.
A shared score earns its place where a framework asks for oversight of cyber risk. NIST CSF 2.0 does this in its Govern function, where GV.OV-03 asks that the organization’s cybersecurity risk management performance is evaluated and reviewed for adjustments needed. A board that reads the same score at each meeting has a record of that review.
Where the portal is not the answer
The portal is not a public trust page. DigitalXForce never publishes a customer’s score, so a company that wants a public web page listing its certifications for any visitor needs a public trust center.
The portal does not rate a company from the outside either. The score is computed from live control evidence, which means the organization’s own evidence has to reach the platform before there is a score to share. The coverage behind a score matters as much as the number, so a buyer can ask in a demo which systems, suppliers and AI assets the score was computed from.
Questions about the Digital Trust Portal
What is the Digital Trust Portal?
The Digital Trust Portal is the external-facing part of the DigitalXForce platform. Boards, regulators and customers read shareable posture dashboards there, including the Digital Trust Score and its seven sub-postures.
What score does the portal show?
It shows the Digital Trust Score, DigitalXForce’s composite score from 300 to 850, computed continuously from live control evidence across seven sub-postures: security, compliance, audit, resilience, third-party, AI and risk. The score sits in one of five bands, from High Trust at 780 and above to Trust at Risk below 500.
Does DigitalXForce publish our score?
It does not. DigitalXForce never publishes a customer’s score.
How current is the score in the portal?
The score updates as the evidence changes, so it is never older than the last evidence the platform read.
Are the weights behind the score published?
They are not. The weights and the scoring logic are DigitalXForce’s intellectual property and are not published.
How is the portal different from a public trust center?
A public trust center lists certifications and documents for any visitor. The portal shows a score computed from live control evidence on shareable dashboards, and DigitalXForce never publishes that score.
Related pages
- The Digital Trust Score is defined on the FAQ, with the methodology page to follow.
- X-ROC, the XForce Risk Operations Center, is where control failures, risk changes and vendor events are alerted, triaged, escalated and reported.
- AI-Powered Enterprise Security Risk and Posture Management (ESRPM) runs the configuration checks, operational insights and deployment benchmarking across the security stack.
- AI-Powered Third-Party Risk Management (TPRM) covers third-party risk, which is one of the seven sub-postures the portal shows.
- Cyber Risk and Liability Insurance translates the platform’s posture data into the inputs underwriters require.
- What is TRiSCM explains the category, and the glossary defines every term on this page.
Sources
- NIST published The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29, on February 26, 2024, at https://csrc.nist.gov/pubs/cswp/29/the-nist-cybersecurity-framework-csf-20/final. Function Govern, outcome GV.OV-03, was read in the published PDF on September 25, 2026.
What this looks like in practice.
Reading about continuous evidence is one thing. Watching a control get tested against live data from your own stack is another. A 30 minute walkthrough on your frameworks shows the difference.
