Governance · 03 · Technology due diligence

What a buyer, investor or insurer needs to know, established independently.

Short, evidence-led reviews of a company’s security, infrastructure, data and AI posture, delivered in the time a transaction allows, and sell-side readiness for the firms about to be examined.

Engagement shapes

Scoped to the transaction.

ShapeScope
Buy-side diligenceTwo to four weeks. Security posture, infrastructure resilience, data obligations, AI use, key-person and vendor dependencies, technical debt. Report written for an investment committee or a board.
Sell-side readinessFour to eight weeks before a process begins. Find and fix what a buyer’s advisers will find; assemble the evidence room.
Insurance evidenceCyber insurance applications and renewals: the controls underwriters now require, documented so premiums reflect reality.
Post-acquisition integrationFirst 100 days: control alignment, access consolidation, continuity of monitoring and evidence.

Capabilities

What it covers.

01 / Capability

Buy-side technology and security diligence

Buy-side technology and security diligence gives an acquirer or investor an independent, evidence-led view of a target’s security posture, infrastructure resilience, data obligations, AI use, key dependencies and technical debt, in the time a transaction allows and in the form an investment committee or board can use.

Learn more →
02 / Capability

Sell-side readiness review

A sell-side readiness review prepares a company for the technology and security diligence a buyer’s advisers will perform: it finds what they will find, fixes what can be fixed in time, documents what cannot, and assembles the evidence room so that diligence confirms rather than discovers.

Learn more →
03 / Capability

Cyber insurance evidence preparation

Cyber insurance evidence preparation assembles and verifies the controls evidence that underwriters now require for an application or renewal, so that answers are accurate, supported and consistent with what an underwriter’s own scan or a post-incident review would find.

Learn more →
04 / Capability

Post-acquisition control integration

Post-acquisition control integration brings an acquired company’s security, identity, infrastructure and data controls under the acquirer’s standards in the first hundred days without breaking the business that was just bought: access consolidation, monitoring coverage, policy alignment, evidence continuity and the closure of the risks diligence identified.

Learn more →
05 / Capability

Key-person and vendor dependency review

A key-person and vendor dependency review identifies the individuals, suppliers, platforms and licenses without which the organization’s technology would stop working or could not be maintained, and assesses how exposed the business is to each.

Learn more →
06 / Capability

Technical debt and resilience assessment

A technical debt and resilience assessment establishes how much accumulated shortcut, obsolescence and fragility sits in an organization’s technology, what it would cost to address, and how it affects the ability to keep operating and to grow.

Learn more →
07 / Capability

Diligence report for boards and lenders

A diligence report for boards and lenders presents technology and security findings in the form a board, an investment committee, a lender or an underwriter can act on: what was examined, what was found, what it means for the decision at hand, what should be reflected in terms, and what must happen afterward.

Learn more →

How it is delivered

Observe. Fortify. Verify. Evidence. Sustain.

The method →
  1. Observe

    Understand the environment, the risks, the obligations, and the operational constraints.
  2. Fortify

    Strengthen practical safeguards without disrupting essential workflows.
  3. Verify

    Test whether controls perform as intended.
  4. Evidence

    Document the results clearly for leadership, auditors, clients, and partners.
  5. Sustain

    Keep controls operating through reporting, review, remediation, and continuous improvement.

Tell us what must be proven.

Discuss a Requirement →