Solutions · Risk · Mergers & acquisitions
Questionnaires and data-room documents tell you what a target says about its security. ioSENTRIX tests what is actually there: the core product, cloud, identity and internet-facing systems. Your deal team gets proven findings to weigh before signing, and a retest of fixes after close is included.
01The short answer
Testing the target, not just reading its answers. Cybersecurity due diligence examines how a company you plan to acquire or invest in protects its information assets: its governance, processes and controls, and whether those controls hold up when tested. For an acquirer it means knowing which security issues you inherit, which ones change the integration plan, and which ones the target should fix before or after closing.
Proven findings on the systems that carry the deal's value: the product, its data and its cloud.
Testing is agreed with the target and fits the access and dates the deal allows.
Connections between the two companies are tested before they go live, and fixes are retested.
M&A cybersecurity due diligence is the security part of deal diligence: a review of the target's security program plus hands-on testing of its most important systems. Findings, what drives the effort to fix them and their effect on integration can then be weighed before the deal is final. Read cybersecurity due diligence before business transactions.
No. ioSENTRIX provides technical testing and evidence. Your legal, financial and insurance advisers decide how findings affect valuation, representations, warranties or indemnities. Public-company acquirers may also have SEC cybersecurity disclosure obligations, adopted in July 2023, that their counsel will consider.
02See it in action
How one diligence question is tested like an attacker would, proven, fixed, retested and answered for the deal team.
We start from what the deal team needs to know and test the systems that answer it, instead of grading a questionnaire.
Each finding carries evidence, business impact and what drives the effort to fix it, so your advisers can weigh it.
A retest of your fixes is included, before close or inside the integration plan.
Illustrative example. The question, endpoint and statuses are a composite for explanation only and do not describe any client or transaction. Testing of a target uses access, accounts and dates agreed with the target.
03Question to evidence
The questions deal teams most often need answered, how ioSENTRIX tests each one, and the evidence you receive.
| Acquirer question | What it asks | What ioSENTRIX tests | Evidence for the deal team |
|---|---|---|---|
| External exposureFrom the internet | What can an attacker reach today: forgotten hosts, admin panels, unpatched services? | External network penetration test and attack-surface review | Exposed services list and proven external findings |
| Core productApplication security | Is the product the deal is paying for secure? | Web app and API testing of access control, tenant isolation and business logic | Application findings with proof and fix guidance |
| Cloud postureAWS · Azure · GCP | Is the cloud estate configured safely? | Cloud configuration review of the accounts in scope | Misconfiguration findings ranked by risk |
| IdentityAD and SSO | Who can become an administrator, and how easily? | Internal and Active Directory testing, SSO and privileged-access review | Privilege paths found and how to close them |
| Data handlingSensitive data | Where does sensitive data live and who can read it? | Data-flow review, access-control testing and secrets checks in code and pipelines | Data exposure findings and data-flow notes |
| Open findingsRemediation | What is already known, and what will fixing it involve? | Review of the target's prior reports and open findings; each new finding rated by severity and fix effort | Fix-effort drivers per finding, for your advisers to cost |
| IntegrationAfter close | What changes when the two environments are connected? | Review of trust links, shared identity and network paths, then an integration test | Integration risks and a retest plan |
Coverage is agreed per transaction in the written scope and with the target's consent. ioSENTRIX provides technical testing and evidence, not legal, financial or valuation advice.
04Timing
Diligence windows are short, so testing is scoped to the deal timeline. This is how it usually fits.
Agree scope and access with the target as part of the diligence request list.
ScopingProgram review and hands-on testing of the systems that matter most. A web application test typically takes 1–2 weeks.
TestingProven findings with impact and fix-effort drivers, written for the deal team and advisers.
Deal team summaryYour advisers decide how findings shape terms; agreed fixes become pre- or post-close items.
Your decisionTest trust links, identity and network connections before and as systems are joined.
IntegrationRetest the agreed fixes within the first 100 days after close.
Retest includedTest the target's product, cloud and exposure inside the diligence window, with the target's consent, so findings reach the deal team before signing.
Test your own systems before going to market and fix what is found, so you can answer buyers' security questions with a recent report and retest results.
05Diligence report
What the deal team, advisers and integration leads need, in one place.
Scope, method and results in plain language for the deal team, investment committee and advisers.
Systems, dates, testers, the access the target agreed to and the standards followed.
Each finding with evidence, severity, business impact and the steps to reproduce it.
What a fix involves for each finding, so your advisers can estimate the effort and cost.
Fixes retested and recorded, so findings are tracked to closure.
Risks to address before networks, identities and data are connected.
Share it with confidence. The report comes from a CREST-accredited firm that is itself ISO/IEC 27001 certified and SOC 2 Type 2 attested. See our trust center.
06Independently verified
“We were impressed with ioSENTRIX's ability to independently validate the security of our customer-facing product.”
“The team at ioSENTRIX is professional and highly skilled at their craft.”
07How we help
Described by engagement type. Clients are never named.
08Insights
09FAQ
Short answers to what deal teams and security leaders ask us most.
Ask us something elseCybersecurity due diligence is the review of how a company you plan to acquire or invest in secures its information assets: its governance, processes and controls. ioSENTRIX adds hands-on testing of the target's most important systems, so the deal team sees proven findings rather than only questionnaire answers. Read cybersecurity due diligence before business transactions.
Usually the target's external exposure, the security of its core product, its cloud configuration, identity and administrator access, how it handles sensitive data, its open findings and past reports, and the risks of connecting it to your environment. The scope depends on what the deal is paying for and the access the target agrees to.
Yes, with the target's written consent and within the access, accounts and dates agreed in the rules of engagement. Testing before signing usually focuses on the systems that carry the deal's value, such as the product and its cloud, and a fuller test can follow after close.
A web application penetration test typically takes 1–2 weeks and a red team exercise typically 4–6 weeks, depending on scope. You receive a written scope and timeline before testing starts, so it can be planned inside the diligence window.
Findings that are not fixed before closing become part of the integration plan. ioSENTRIX can test trust links, shared identity and network paths before systems are joined, and a retest of your fixes is included, usually planned within the first 100 days after close.
No. ioSENTRIX provides technical security testing and evidence. Your legal, financial and insurance advisers decide how findings affect valuation, terms, representations or indemnities. For public-company acquirers, counsel may also consider the SEC cybersecurity disclosure rules adopted in July 2023.
Yes. Sell-side testing lets you find and fix issues before buyers do, and answer their security questions with a recent report and retest results from a CREST-accredited firm.
Ready when you are
Tell us the target's main systems, the access you expect and your diligence dates. We will help you scope testing that fits the deal timeline.
Takes about a minute.
