Damian Maggio: Why Cybersecurity Has Become a Core Diligence Question

When I look at a technology company today, I ask about cybersecurity early, not at the end. A few years ago it was often treated as an IT topic. Now it touches revenue, reputation, contracts and, for public companies, required disclosure.

The disclosure side changed in 2023. In July of that year, the SEC adopted rules requiring public companies to disclose material cybersecurity incidents on a new Item 1.05 of Form 8-K, generally within four business days after the company determines an incident is material. The same rules added an annual requirement, in the Form 10-K, to describe how the company assesses and manages cybersecurity risk and how its board oversees that risk.

Private companies are not covered by those public-company rules. But many of them plan to go public someday, and many sell to large customers who ask hard security questions before signing. That makes cybersecurity a fair diligence topic at almost any stage.

Governance. Who owns security inside the company? Is there a named leader, and does that person report to the board or a committee? A company that can answer clearly tends to have thought about the issue.

Incident history. Has the company had a breach or a material incident? How did it find out, how long did it take to respond, and what changed afterward? A past incident is not automatically a red flag. How it was handled often matters more.

Customer requirements. Enterprise and government customers often require security reviews, certifications or contract terms. If a company sells to those buyers, its security program can affect how fast it closes deals.

Third parties. Most software companies rely on cloud providers, open-source code and outside vendors. Each is a possible point of failure. Knowing how a company tracks and reviews those dependencies tells you how much of its risk it actually controls.

Readiness for public disclosure. A company that hopes to list will eventually need processes to decide quickly whether an incident is material and to describe its risk management in its annual report. Building that late is harder than building it early.

There are limits to what an outside reviewer can learn. Security programs are hard to measure from the outside, companies share only so much, and a strong program today does not rule out an incident tomorrow. Diligence can reduce uncertainty. It cannot remove it.

What has changed is the weight of the question. Cybersecurity is now part of how a company is run and, for public companies, part of what it must tell investors. That is reason enough to ask about it early.

Damian Maggio writes about private markets and technology. This article is for informational purposes only and is not an offer or recommendation to buy or sell any security.

Originally published at damianmaggio.com

Comments

Popular posts from this blog

Damian Maggio on Tender Offers: How Late-Stage Private Companies Create Liquidity

Damian Maggio on Direct Listings vs. IPOs: Two Ways a Private Company Goes Public