Prove risk reduction.

Testify is the cyber risk platform built for private equity portfolios. It turns real operational data from every company you own into risk reduction you can measure and defend. The board, the fund and each CISO start every conversation from the same evidence.

Earned ≠ re‑estimated
Verified closes and model changes never share a number
Portfolio-native
Parent-child hierarchy from the ground up
Your deployment
Docker container, your cloud, local AI
Fig. 01

Risk trajectory

Three readings, deliberately not merged into one.

Proven Counted
+17

controls verified, trailing 12 months

Evidence landed, procedure passed

Modeled Modeled
−$0.6M

projected annual loss, 12 months

Monthly snapshots, your loss model

Observed Counted
2

incidents, trailing 12 months

Your incident register, the ground truth

Illustrative data. A fictional seven-company portfolio, not customer figures.

Dollar figures are easy. Defending them is not.

  1. Dollar figures nobody can defend

    A risk number that drops because the model changed looks exactly like a risk number that drops because a control got fixed. Boards and LPs can't tell the difference, and most platforms don't show it.

  2. Questionnaire snapshots

    An annual questionnaire captures what a company said once. Posture degrades between reviews, and nobody knows until an incident forces discovery.

  3. Everyone builds the portfolio in their head

    CISOs, advisors and Portfolio Directors each reconstruct the picture from spreadsheets, calls and memory before they can talk about it, and each version differs. When a breach hits, there's no record of whether known gaps were communicated, tracked, or addressed. Liability is undefined.

Read the ledgerTwo companies sit below their calibrated expectation: a combined $5.3M in annualized loss expectancy the fund cannot currently see.

Six screens a board can interrogate.

The same numbers, framed for whoever is asking.

The Executive Brief is screen one. The other five answer the questions that follow it: where the weakness is, whether the tools work, what the model assumes, what a budget buys, and whether the work landed.

Fig. 02

Exposure bridge

Modeled

What moved projected annual loss this quarter, and how much of it was earned rather than re-estimated.

$0$4M$8M$12M$12.0MOpening−$2.6MEarned+$0.6MRe-estimated+$1.4MPortfolio changed$11.4MClosing
Earned
Verified closes and regressions. Evidence landed.
Re-estimated
The loss model changed. Not progress, not regression.
Portfolio changed
Companies acquired or exited.

Illustrative data. Board screens shown with a fictional seven-company portfolio.

See the way in before an attacker does.

Ask about any company and the assistant answers from the evidence already in your register, on a local model inside your own deployment. No API calls, no third-party provider.

  • Observed entry

    An internet-facing service found by your attack-surface connectors (Shodan, GreyNoise, HIBP and crt.sh) becomes the technique an attacker would use. Lookups send only a company's attested domains, and only with that company's consent.

  • Inferred chain

    Open control gaps, mapped from MITRE ATT&CK to CIS Controls, carry that entry through to Impact or Exfiltration.

  • Priced blast radius

    The path's loss range comes from your own loss model.

Observed or inferred, stated on every link. An empty scan is not a clean company.

How attack paths are built
Testify · Assistant Local model

Illustrative: local model output on a sample portfolio company.

Better data. Better conversations.

Portfolio Directors, portfolio CISOs and advisors spend their time rebuilding the portfolio from spreadsheets, calls and memory. Testify does that assembly once, in one register, so every conversation starts from the same evidence. That includes the hard ones, from a configuration change to a leadership change. Testify does not make those decisions. They carry judgment, trust and emotion, and they stay with your people.

Before: assembled by handA Portfolio Director sits at the center of five portfolio companies, Co. A to Co. E, and pulls each one together from a spreadsheet, a call, memory, an email or a questionnaire. CISOs and advisors rebuild it too, and each version differs.Before: assembled by handEvery person rebuilds the portfoliobefore anyone can talk.
After: one shared registerFor one pillar, policy hygiene, five companies are shown against each company's calibrated expectation. Co. B trails its expectation. Co. D leads. The Portfolio Director makes an introduction between Co. B and Co. D.After: one shared registerTestify assembles it once. The Directorputs the right people together.

Assembled

The tedious part, done once

Local AI tracks every assessment, verification campaign, remediation and technology journey over time, in one register. Nobody has to rebuild the picture before a conversation can start.

Surfaced

Who trails, who leads

The Portfolio Director sees, pillar by pillar, which companies trail their calibrated expectation and which lead. The evidence shows where a conversation would help.

Connected

The Director decides what's shared

The Portfolio Director controls what peers see about each other, and decides whether to introduce the CISO of a trailing company to a peer who leads. The CISOs take it from there, by phone or in person.

Reaches people where they work. Slack and Teams deliver findings to the people who'll discuss them. Jira and ServiceNow are included.

Illustrative data. A fictional five-company portfolio, shown for one pillar.

One portfolio. One scale. Every company on it.

Why the earned number holds up.

Dollars only mean something if the controls behind them are measured the same way everywhere. A 20-person SaaS startup and a 20,000-person logistics company are not the same, so Testify holds each to a calibrated expectation, then rolls every company onto one normalized maturity scale. Select a company to see what's underneath the number.

Fig. 09

Live portfolio ledger

Normalized maturity
67portfolio average
Below expectation
2of 6 companies
Shortfall
$5.3Mannualized loss expectancy

Illustrative data. Figures shown are sample portfolio companies, not customers. CME tier reflects organizational complexity; the method is transparent to customers inside the platform.

Your framework. Questions that get evidence.

Most portfolio platforms score every company against one framework, usually NIST CSF. Testify scores against CIS Controls v8, NIST CSF 2.0, or a framework you write. Its local AI helps every assessor give an answer that holds up.

Score against the framework you run

  1. 1Basics
  2. 2Controls
  3. 3Questions
  4. 4Review & Publish

CIS Controls v8, NIST CSF 2.0, or your own framework, built and published in the authoring wizard.

Ask for proof, not a flattering yes

Before

Do you require MFA for externally exposed applications?

After

When did you last review MFA exceptions for your external apps, and where is that list kept?

Illustrative of what the local model drafts.

A coach, not a certifier

Answer

We use MFA everywhere.

Coach

Names no system or exception list. Which apps are covered, and what is excluded?

Illustrative example. The coach suggests; the assessor decides.

Your portfolio data never leaves your infrastructure.

Testify deploys as a Docker container into your own cloud or on-prem environment. No SaaS multi-tenancy. No vendor with access to your portfolio company data. No third-party AI providers.

Your deployment: AWS, Azure, GCP or on-prem TestifyOne Docker containerSame platform on every target Local modelImport, coaching, questions:all inference stays inside Evidence registerEvery control state change logged with source, timestamp and actor Attack-surface connectorscrt.sh, Shodan, HIBP, GreyNoiseOff until a company consents attested domains only findings Third-party AI providerNo calls, no API keys, no egress Third-party AI providerNo calls, no API keys, no egress Your deployment: AWS, Azure, GCP or on-prem TestifyOne Docker container on any target Local modelAll inference stays inside Evidence registerEvery change logged: source, time, actor attested domains only findings Attack-surface connectorscrt.sh, Shodan, HIBP, GreyNoiseOff until a company consents

Your cloud, your rules

AWS, Azure, GCP, or on-prem: same container, same platform. Deploy where your data governance policy requires.

Local AI inference

All AI features (document import, assessment coaching, natural language queries) run on a local model inside your deployment. Zero data transmitted to external providers.

Auditable by design

Every control state change logged with source, timestamp, and actor. Board-ready reports and M&A due diligence packages generated in hours, not weeks.

The six demos to ask any vendor for.

PE security leaders are running the same bake-off. Here is what each ask usually gets, and what Testify shows instead.

The askWhat you'll usually be shownWhat Testify shows
1Onboard a new acquisition in days, with imperfect dataQuestionnaires and a months-long baselineLocal-AI import of the assessments, policies and audit findings a company already has. Keystone Freight is mid-baseline in the ledger. The ledger
2Score a $15M software company and a $400M industrial on one scaleOne score for everyone, or reports you can't compareCalibrated expectations per company, rolled onto one normalized scale. Why the number holds up
3A one-page fund view and an LP appendix, without a week of analyst workConsultant-assembled decksThe Executive Brief and the Exposure Map, generated from the live register. The Board
4Residual risk after the top remediations, in dollarsA dollar figure that moves whenever the model movesEarned versus re-estimated in the exposure bridge, and a capital frontier showing what each dollar retires. The bridge Capital Allocation
5Who owns the evidence, what happens at exit, and whose cloud it lives inVendor SaaS; the evidence lives with the vendorYour deployment, local AI and a portable exit record, from a vendor with no private-equity investors or owners. Data sovereignty Why HoldTrue
6Show what I'd bring to a hard resource decision at one companyAnecdotes and last year's questionnaireThe company's assessment history, verification results, remediation record and technology journey, against its calibrated expectation. Better conversations

Eight questions to ask any vendor

Built for the people who own the risk.

Portfolio Directors and Operating Partners

Portfolio-level oversight

  • Compare security maturity across all portfolio companies with calibrated expectations
  • Identify systemic gaps before they become fund-level risks
  • Generate board-ready reports that demonstrate diligence
  • Track remediation commitments with built-in accountability
  • See which company trails in a pillar and which peer CISO in your portfolio leads it, and decide what's shared

Portfolio company CISOs

Operational security command

  • Run assessments against CIS Controls v8, NIST CSF 2.0, or your own framework
  • Manage incidents with MITRE ATT&CK mapping and automated control degradation
  • Verify control effectiveness with evidence-based campaigns
  • Bring data-backed metrics to every conversation with the fund, your advisors and your portfolio peers

Advisory-grade methodology, distilled into software.

Testify isn't a feature list someone assembled. It's a cybersecurity methodology refined across years of enterprise advisory work (the kind of portfolio assessment large consultancies build over years), systematized so it runs continuously, at portfolio scale, for a fraction of the cost. Founder-led, built by practitioners.

Founder-led. Practitioner-built. No PE investors.

The methodology
Backed by results. The scoring model, the four maturity dimensions, the calibrated CME tiers: built on how the world's best-resourced security programs actually operate, now running across every company in your portfolio.
The engineering
Built to a higher bar. Portfolio-native architecture, a private locally-hosted AI model, and an Overlay SDK for custom frameworks. No SaaS multi-tenancy, no third-party AI, no data leaving your environment.
The ownership
Independent by design. HoldTrue has no private-equity investors or owners. The platform that governs your portfolio doesn't answer to a sponsor you compete with for deals. And because Testify is self-hosted, your portfolio data never sits with us either.
The posture
Early by design. HoldTrue is taking a deliberately small number of founding customers. You work directly with the team who built the methodology and the platform, not a support queue. First movers shape the roadmap.

Common questions about Testify.

More in the full FAQ, or start with What is Testify and how it compares.

What is Testify?

Testify, by HoldTrue, is a cyber GRC platform purpose-built for private equity firms to govern cybersecurity across every portfolio company. It maintains a continuously updated, evidence-backed security posture for each company, prices that posture in dollars, and runs all AI locally so portfolio data never leaves your environment.

How is Testify different from compliance tools like Vanta or Drata?

Vanta and Drata help a single company earn a certification such as SOC 2; Testify governs cybersecurity maturity across an entire portfolio for the investor. A portfolio company can be SOC 2 compliant and still have controls that are not automated or enforced. Firms often run a compliance tool inside individual companies and use Testify on top to measure, compare, and prove control efficacy across the whole portfolio.

Does my portfolio data ever leave my environment?

No. Testify deploys as a Docker container into your own cloud or on-prem environment, and all AI inference runs locally on open-weight models. There is no SaaS multi-tenancy and no third-party AI provider. Portfolio data never leaves your infrastructure.

How does Testify compare security across companies of very different sizes?

Testify calibrates maturity expectations to each company's size, complexity, and data sensitivity, then rolls every company onto one normalized 0–100 maturity scale. A 20-person SaaS startup and a 20,000-person logistics company are held to appropriate expectations and still compared on a common baseline.

What frameworks does Testify support?

Testify assesses against CIS Controls v8 at the safeguard level and NIST CSF 2.0, with a NIST-to-CIS crosswalk, and you can build and score your own framework in the authoring wizard. AI risk is covered through an AI hygiene assessment based on SAFE² with crosswalks to the EU AI Act, NIST AI RMF, ISO 42001, and OWASP-LLM. Testify recommends assessment questions from your incident history, its local AI drafts them to ask for evidence, and an AI coach checks answers against the control's requirements when the assessor asks.

What does Testify show a PE board?

Six Board screens computed from the live register: an Executive Brief whose exposure bridge separates risk reduction earned by verified control closes from model re-estimates and portfolio changes; a Portfolio Exposure Map of claimed versus verified coverage; Spend Efficacy; a Loss Model with every assumption visible; Capital Allocation ranked by what each dollar retires; and a Campaign Rollup that counts the exposure verified work retired.

How is Testify different from CRQ tools that show dollar exposure?

Most cyber risk quantification tools produce a dollar figure. Testify ties that figure to verified control state and shows why it moved: earned by verified closes, re-estimated because an assumption changed, or changed because the portfolio changed. The loss model is visible to customers and theirs to adjust.

Is HoldTrue owned or funded by private equity?

No. HoldTrue has no private-equity investors or owners, so the vendor behind your portfolio governance platform is not backed by a sponsor you compete with. Testify is also self-hosted: portfolio data stays in your deployment.

Does Testify make decisions about my portfolio companies?

No. Testify assembles the evidence: assessments, verification campaigns, remediations and technology journeys, tracked over time. Portfolio Directors, CISOs and advisors make the decisions, from a configuration change to a leadership change. When a model is overridden, the override is recorded with its justification.

Who controls what companies see about each other?

The Portfolio Director. Communication runs among one firm's portfolio companies and never across firms. The Director decides what level of detail peers see about each other, and whether to make an introduction.

See it
live

Testify is accepting early customers. Portfolio Directors and Fund Operating Partners get priority access to a guided walkthrough.

Talk to the people who built it. Reach us directly at info@holdtrue.ai

What you'll see

  • Exposure bridge: earned vs re-estimated
  • Six Board screens, one register
  • Attack paths: observed vs inferred
  • Live portfolio ledger, 7 entities
  • Local AI, zero data egress