Palo Alto cuts hundreds of job after $25b CyberArk deal

Palo Alto Networks has laid off hundreds of CyberArk employees worldwide, including dozens in Israel, shortly after completing its US$25 billion acquisition of CyberArk.

The company employs around 4,000 staff, with about 1,000 based in Israel, and more than 10% of its workforce is affected.

The company said the organizational changes are part of the integration process and mainly target roles with overlapping responsibilities.

Palo Alto emphasized its commitment to business continuity and continued investment in technology and teams.

The acquisition is one of the largest involving an Israeli company. It was finalized shortly after Google’s US$32 billion purchase of Wiz neared completion.

🔗 Source: Calcalist

🧠 Food for thought

Implications, context, and why it matters.

Palo Alto’s high-stakes promises meet post-merger tradeoffs

Palo Alto agreed to pay $25 billion, valuing CyberArk at 19.2 times trailing revenue, which raised the bar for cost cuts that justify the premium 1.
That push for savings sits beside pledges of continuity, including “no disruption” for customers and “business as usual until July 31, 2026” for partners 2 3.
Layoffs land awkwardly with CEO Nikesh Arora’s remarks about Israel’s role in Palo Alto Networks’ innovation and plans to deepen its presence there, yet the company is also preparing a secondary listing on the Tel Aviv Stock Exchange (TASE) under the ticker “CYBR,” which signals a longer-term bet on the region 3.

Cybersecurity’s platform era turns integration bumps into routine

Analysts describe the deal as part of a shift toward bundled security platforms, which tightens competition with Microsoft’s identity-led strategy and puts pressure on specialists like Okta 4.
For organizations running CyberArk privileged access tools alongside Palo Alto Networks’ wider security stack, the job cuts underline execution risk in the “one-stop shop” pitch, plus concerns about vendor lock-in and churn from interface or licensing changes in complex setups 4.
Removing duplicate positions also exposes a common merger strain when teams must align culture and product roadmaps, which can add transition friction and slow delivery 4.