KorvaJoin the waitlist
Startups

A Failed Hacking Test Can Kill a Salesforce Deal

Security is the one check among 14 that can veto a deal on its own.

AI image
The a16z Show · Inside Salesforce’s $100 Billion M&A Playbook | John Somorjai

The hackers kept going. First they slipped into the startup's source code, the basic instructions behind its product.

Then they got into the chief executive's laptop. Then they found information about employees.

The hackers worked for Salesforce. John Somorjai, the company's corporate development chief, said his team runs its own break in attempt on almost every acquisition target.

Security is the one check that can kill a Salesforce deal on its own. Fourteen separate teams review a target, but only security can hold up a red flag and stop everything.

That power usually comes into play after both sides have agreed on a price and major terms. Then Salesforce begins deep diligence, and the technology gets tested.

In one case, the test reached all the company's source code, the chief executive's laptop, and employee information. Somorjai said the flaws were some of the worst the team had ever seen.

Salesforce told the startup what it had found and tried to help it fix the problems, as it always does. This time, Somorjai said, the problem was unrecoverable.

Lesser flaws do not always doom a deal. Salesforce ranks them as P0, P1, and P2 problems, and can require the worst to be fixed before signing and the rest before closing.

Somorjai's advice to founders is blunt: hack yourself first. Run a red team exercise, in which friendly attackers probe for weaknesses, and find the vulnerabilities before Salesforce does.

A clean process moves quickly and painlessly, he said. A messy one is when deals can die.

Questions people ask

What is a penetration test?

A penetration test is a simulated cyberattack, carried out with permission, to find weaknesses before real attackers do. Testers try to slip past passwords, misuse software flaws, and move from one system to another, then report what they reached.

What do P0, P1, and P2 problems mean?

Software teams often rank bugs as P0, P1, and P2, with P0 the most urgent. A P0 might be a flaw that exposes customer data and must be fixed immediately, while a P2 might be a smaller weakness with a workaround. In a deal, a buyer can demand that P0s be fixed before signing.

More in Startups