- Capability
- Due Diligence & Reviews
- Lead
- Joey Victorino — personally led
- Basis
- Written scope · scoped after intake
- Contact
- joey@victori.no
Independent evidence, before the decision is priced.
Capital or accountability depends on technical claims nobody independent has tested — an acquisition, an incident the board is asked to close, a consequential recommendation. Everyone else at the table has a stake in the answer. I don’t.
A Transaction technical due diligence
Technical and cybersecurity diligence for private equity, strategic acquirers, investment committees, and boards. The engagement tests technical reality against the investment thesis. Before capital moves, I answer:
When AI is material to the valuation — a proprietary platform, a transformation plan, a cost model built on GPUs — the claim gets the same treatment. I build and secure this class of system in my own operating work; claims are tested against how these systems behave, not against the demo.
Deliverables: an investment-committee memo with the independent conclusion, the technical findings behind it, and the management questions to ask before you wire. depending on scope; expedited timelines available. For sponsors, a standing program covers the portfolio: baseline, periodic reviews, a diligence allocation for live deals, partnership-level reporting.
I performed acquisition-related security testing and technical examination at NCC Group before doing this work independently. Employers are not clients; confidential matters stay confidential.
B Incident closure review
Before the board accepts closure, before regulators or customers are told, and before the insurance narrative hardens, an independent review tests whether the evidence supports contained, eradicated, closed. I examine the investigation record, the containment and eradication evidence, the scoping decisions, and what was not looked at. The written conclusion states whether closure holds, holds only with named conditions, or does not hold. depending on scope.
C Executive decision review
One consequential decision — a committed contract, an architecture, a vendor claim — tested independently and answered in a signed memorandum: what the evidence supports, what it does not, and what to do next. , normally 3 to 5 business days. The same discipline covers a single technical claim before it is priced into a deal.
