Palo Alto Networks: how its security business has expanded
Palo Alto Networks is an enterprise cybersecurity supplier whose scope now extends beyond the network firewall. Understanding that expansion requires separating network protection, security operations, cloud security, identity controls and observability. They address related problems, but they are not interchangeable products.
The company’s current story also includes completed acquisitions. Reporting an acquisition as merely proposed after it has closed, or describing a planned integration as already finished, gives buyers the wrong view of the portfolio.
A firewall heritage with a changing leadership story
The company’s August 2025 announcement identifies Nir Zuk as a founder and dates the business to 2005. It also records his retirement and Lee Klarich’s appointment as CTO. A historical founder credit should therefore not be copied into a current executive listing.
Palo Alto Networks’ company overview frames its business around enterprise security. That positioning is vendor material, rather than proof that one supplier can prevent every attack.
CyberArk is a completed acquisition
Palo Alto Networks completed its CyberArk acquisition on 11 February 2026. The announcement described identity security as a core part of the strategy and said integration work was under way.
Identity security concerns who or what can act inside an organisation. Human accounts, software services and automated agents all need permissions, but their operating patterns differ. A service account with excessive access creates a different management problem from an employee awaiting approval for a temporary role.
The October 2026 proxy statement subsequently identifies the acquired business’s rebrand as Idira. It describes privileged access management and machine identity as important capabilities. Retaining the CyberArk name as acquisition history is accurate; presenting it as a still-independent pending deal is not.
What Chronosphere adds
The Chronosphere transaction closed on 29 January 2026. Its relevance is observability: visibility into the behaviour of applications and infrastructure through operational data.
Security and observability can use overlapping information without having identical purposes. An application slowdown may need investigation even when there is no malicious activity. Conversely, an apparently healthy service can still have an access-control problem.
At closing, Palo Alto Networks described planned integration with Cortex AgentiX. That wording matters. It establishes the stated direction at that date, not a guarantee that every promised workflow was already available to every customer.
Assess the workflow, not just the platform label
The 2026 proxy groups the strategy around network security; security operations, observability and cloud security; and identity security. That is a clearer guide to scope than a list of acquisition names.
For an organisation evaluating these tools, map a concrete incident through the proposed system. Which component detects it? Who approves containment? Which logs are retained? Can investigators reconstruct an automated action? The answers should appear in the design and operating procedures, not only in a demonstration.
South African buyers should also establish the contracted support route, deployment locations, retention settings and responsibilities for operating the service. Procurement should distinguish software licences from the people and processes needed to use them.
A larger integrated portfolio can simplify some relationships while increasing dependence on a single supplier. Evaluate interoperability, export options and renewal terms alongside the security capabilities. This profile describes the business and its disclosed changes; it does not substitute vendor claims for an independent security assessment.
