[](https://www.paloaltonetworks.com/?ts=markdown) * Sign In * Customer * Partner * Employee * [Login to download](https://www.paloaltonetworks.com/login?ts=markdown) * [Join us to become a member](https://www.paloaltonetworks.com/login?screenToRender=traditionalRegistration&ts=markdown) * EN * [USA (ENGLISH)](https://www.paloaltonetworks.com) * [AUSTRALIA (ENGLISH)](https://www.paloaltonetworks.com.au) * [BRAZIL (PORTUGUÉS)](https://www.paloaltonetworks.com.br) * [CANADA (ENGLISH)](https://www.paloaltonetworks.ca) * [CHINA (简体中文)](https://www.paloaltonetworks.cn) * [FRANCE (FRANÇAIS)](https://www.paloaltonetworks.fr) * [GERMANY (DEUTSCH)](https://www.paloaltonetworks.de) * [INDIA (ENGLISH)](https://www.paloaltonetworks.in) * [ITALY (ITALIANO)](https://www.paloaltonetworks.it) * [JAPAN (日本語)](https://www.paloaltonetworks.jp) * [KOREA (한국어)](https://www.paloaltonetworks.co.kr) * [LATIN AMERICA (ESPAÑOL)](https://www.paloaltonetworks.lat) * [MEXICO (ESPAÑOL)](https://www.paloaltonetworks.com.mx) * [SINGAPORE (ENGLISH)](https://www.paloaltonetworks.sg) * [SPAIN (ESPAÑOL)](https://www.paloaltonetworks.es) * [TAIWAN (繁體中文)](https://www.paloaltonetworks.tw) * [UK (ENGLISH)](https://www.paloaltonetworks.co.uk) * ![magnifying glass search icon to open search field](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/search-black.svg) * [Contact Us](https://www.paloaltonetworks.com/company/contact-sales?ts=markdown) * [What's New](https://www.paloaltonetworks.com/resources?ts=markdown) * [Get Support](https://support.paloaltonetworks.com/SupportAccount/MyAccount) * [Under Attack?](https://start.paloaltonetworks.com/contact-unit42.html) ![x close icon to close mobile navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/x-black.svg) [![Palo Alto Networks logo](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/pan-logo-dark.svg)](https://www.paloaltonetworks.com/?ts=markdown) ![magnifying glass search icon to open search field](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/search-black.svg) * [](https://www.paloaltonetworks.com/?ts=markdown) * Products ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Products [AI-Powered Network Security Platform](https://www.paloaltonetworks.com/network-security?ts=markdown) * [AI Security](https://www.paloaltonetworks.com/precision-ai-security/secure-ai-by-design?ts=markdown) * [Prisma AIRS](https://www.paloaltonetworks.com/prisma/prisma-ai-runtime-security?ts=markdown) * [AI Access Security](https://www.paloaltonetworks.com/sase/ai-access-security?ts=markdown) * [Cloud Delivered Security Services](https://www.paloaltonetworks.com/network-security/security-subscriptions?ts=markdown) * [Advanced Threat Prevention](https://www.paloaltonetworks.com/network-security/advanced-threat-prevention?ts=markdown) * [Advanced URL Filtering](https://www.paloaltonetworks.com/network-security/advanced-url-filtering?ts=markdown) * [Advanced WildFire](https://www.paloaltonetworks.com/network-security/advanced-wildfire?ts=markdown) * [Advanced DNS Security](https://www.paloaltonetworks.com/network-security/advanced-dns-security?ts=markdown) * [Enterprise Data Loss Prevention](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Enterprise Device Security](https://www.paloaltonetworks.com/network-security/enterprise-device-security?ts=markdown) * [Medical Device Security](https://www.paloaltonetworks.com/network-security/medical-device-security?ts=markdown) * [OT Device Security](https://www.paloaltonetworks.com/network-security/ot-device-security?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) * [Next-Generation Firewalls](https://www.paloaltonetworks.com/network-security/next-generation-firewall?ts=markdown) * [Hardware Firewalls](https://www.paloaltonetworks.com/network-security/hardware-firewall-innovations?ts=markdown) * [Software Firewalls](https://www.paloaltonetworks.com/network-security/software-firewalls?ts=markdown) * [Strata Cloud Manager](https://www.paloaltonetworks.com/network-security/strata-cloud-manager?ts=markdown) * [SD-WAN for NGFW](https://www.paloaltonetworks.com/network-security/sd-wan-subscription?ts=markdown) * [PAN-OS](https://www.paloaltonetworks.com/network-security/pan-os?ts=markdown) * [Panorama](https://www.paloaltonetworks.com/network-security/panorama?ts=markdown) * [Secure Access Service Edge](https://www.paloaltonetworks.com/sase?ts=markdown) * [Prisma SASE](https://www.paloaltonetworks.com/sase?ts=markdown) * [Application Acceleration](https://www.paloaltonetworks.com/sase/app-acceleration?ts=markdown) * [Autonomous Digital Experience Management](https://www.paloaltonetworks.com/sase/adem?ts=markdown) * [Enterprise DLP](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Prisma Access](https://www.paloaltonetworks.com/sase/access?ts=markdown) * [Prisma Browser](https://www.paloaltonetworks.com/sase/prisma-browser?ts=markdown) * [Prisma SD-WAN](https://www.paloaltonetworks.com/sase/sd-wan?ts=markdown) * [Remote Browser Isolation](https://www.paloaltonetworks.com/sase/remote-browser-isolation?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) [AI-Driven Security Operations Platform](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cloud Security](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Cortex Cloud](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Application Security](https://www.paloaltonetworks.com/cortex/cloud/application-security?ts=markdown) * [Cloud Posture Security](https://www.paloaltonetworks.com/cortex/cloud/cloud-posture-security?ts=markdown) * [Cloud Runtime Security](https://www.paloaltonetworks.com/cortex/cloud/runtime-security?ts=markdown) * [Prisma Cloud](https://www.paloaltonetworks.com/prisma/cloud?ts=markdown) * [AI-Driven SOC](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cortex XSIAM](https://www.paloaltonetworks.com/cortex/cortex-xsiam?ts=markdown) * [Cortex XDR](https://www.paloaltonetworks.com/cortex/cortex-xdr?ts=markdown) * [Cortex AgentiX](https://www.paloaltonetworks.com/cortex/agentix?ts=markdown) * [Cortex XSOAR](https://www.paloaltonetworks.com/cortex/cortex-xsoar?ts=markdown) * [Cortex Exposure Management](https://www.paloaltonetworks.com/cortex/exposure-management?ts=markdown) * [Cortex Xpanse](https://www.paloaltonetworks.com/cortex/cortex-xpanse?ts=markdown) * [Cortex Advanced Email Security](https://www.paloaltonetworks.com/cortex/advanced-email-security?ts=markdown) * [Unit 42 Managed Detection \& Response](https://www.paloaltonetworks.com/cortex/managed-detection-and-response?ts=markdown) * [Unit 42 Managed XSIAM](https://www.paloaltonetworks.com/cortex/managed-xsiam?ts=markdown) [![](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberark/Seamless_IDs_small.jpg) Identity Security](https://www.paloaltonetworks.com/identity-security?ts=markdown) * Solutions ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Solutions Secure AI by Design * [Secure AI Ecosystem](https://www.paloaltonetworks.com/prisma/prisma-ai-runtime-security?ts=markdown) * [Secure GenAI Usage](https://www.paloaltonetworks.com/sase/ai-access-security?ts=markdown) Network Security * [Cloud Network Security](https://www.paloaltonetworks.com/network-security/software-firewalls?ts=markdown) * [Data Center Security](https://www.paloaltonetworks.com/network-security/data-center?ts=markdown) * [DNS Security](https://www.paloaltonetworks.com/network-security/advanced-dns-security?ts=markdown) * [Intrusion Detection and Prevention](https://www.paloaltonetworks.com/network-security/advanced-threat-prevention?ts=markdown) * [Device Security](https://www.paloaltonetworks.com/network-security/device-security?ts=markdown) * [OT Security](https://www.paloaltonetworks.com/network-security/ot-security-solution?ts=markdown) * [5G Security](https://www.paloaltonetworks.com/network-security/5g-security?ts=markdown) * [Secure All Apps, Users and Locations](https://www.paloaltonetworks.com/sase/secure-users-data-apps-devices?ts=markdown) * [Secure Branch Transformation](https://www.paloaltonetworks.com/sase/secure-branch-transformation?ts=markdown) * [Secure Work on Any Device](https://www.paloaltonetworks.com/sase/secure-work-on-any-device?ts=markdown) * [VPN Replacement](https://www.paloaltonetworks.com/sase/vpn-replacement-for-secure-remote-access?ts=markdown) * [Web \& Phishing Security](https://www.paloaltonetworks.com/network-security/advanced-url-filtering?ts=markdown) Cloud Security * [Application Security Posture Management (ASPM)](https://www.paloaltonetworks.com/cortex/cloud/application-security-posture-management?ts=markdown) * [Software Supply Chain Security](https://www.paloaltonetworks.com/cortex/cloud/software-supply-chain-security?ts=markdown) * [Code Security](https://www.paloaltonetworks.com/cortex/cloud/code-security?ts=markdown) * [Cloud Security Posture Management (CSPM)](https://www.paloaltonetworks.com/cortex/cloud/cloud-security-posture-management?ts=markdown) * [Cloud Infrastructure Entitlement Management (CIEM)](https://www.paloaltonetworks.com/cortex/cloud/cloud-infrastructure-entitlement-management?ts=markdown) * [Data Security Posture Management (DSPM)](https://www.paloaltonetworks.com/cortex/cloud/data-security-posture-management?ts=markdown) * [AI Security Posture Management (AI-SPM)](https://www.paloaltonetworks.com/cortex/cloud/ai-security-posture-management?ts=markdown) * [Cloud Detection \& Response](https://www.paloaltonetworks.com/cortex/cloud-detection-and-response?ts=markdown) * [Cloud Workload Protection (CWP)](https://www.paloaltonetworks.com/cortex/cloud/cloud-workload-protection?ts=markdown) * [Web Application \& API Security (WAAS)](https://www.paloaltonetworks.com/cortex/cloud/web-app-api-security?ts=markdown) Security Operations * [Cloud Detection \& Response](https://www.paloaltonetworks.com/cortex/cloud-detection-and-response?ts=markdown) * [Security Information and Event Management](https://www.paloaltonetworks.com/cortex/modernize-siem?ts=markdown) * [Network Security Automation](https://www.paloaltonetworks.com/cortex/network-security-automation?ts=markdown) * [Incident Case Management](https://www.paloaltonetworks.com/cortex/incident-case-management?ts=markdown) * [SOC Automation](https://www.paloaltonetworks.com/cortex/security-operations-automation?ts=markdown) * [Threat Intel Management](https://www.paloaltonetworks.com/cortex/threat-intel-management?ts=markdown) * [Managed Detection \& Response](https://www.paloaltonetworks.com/cortex/managed-detection-and-response?ts=markdown) * [Attack Surface Management](https://www.paloaltonetworks.com/cortex/cortex-xpanse/attack-surface-management?ts=markdown) * [Compliance Management](https://www.paloaltonetworks.com/cortex/cortex-xpanse/compliance-management?ts=markdown) * [Internet Operations Management](https://www.paloaltonetworks.com/cortex/cortex-xpanse/internet-operations-management?ts=markdown) * [Extended Data Lake (XDL)](https://www.paloaltonetworks.com/cortex/cortex-xdl?ts=markdown) * [Agentic Assistant](https://www.paloaltonetworks.com/cortex/cortex-agentic-assistant?ts=markdown) Endpoint Security * [Endpoint Protection](https://www.paloaltonetworks.com/cortex/endpoint-protection?ts=markdown) * [Extended Detection \& Response](https://www.paloaltonetworks.com/cortex/detection-and-response?ts=markdown) * [Ransomware Protection](https://www.paloaltonetworks.com/cortex/ransomware-protection?ts=markdown) * [Digital Forensics](https://www.paloaltonetworks.com/cortex/digital-forensics?ts=markdown) [Industries](https://www.paloaltonetworks.com/industry?ts=markdown) * [Public Sector](https://www.paloaltonetworks.com/industry/public-sector?ts=markdown) * [Financial Services](https://www.paloaltonetworks.com/industry/financial-services?ts=markdown) * [Manufacturing](https://www.paloaltonetworks.com/industry/manufacturing?ts=markdown) * [Healthcare](https://www.paloaltonetworks.com/industry/healthcare?ts=markdown) * [Small \& Medium Business Solutions](https://www.paloaltonetworks.com/industry/small-medium-business-portfolio?ts=markdown) [![](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberark/Seamless_IDs_small.jpg) Identity Security](https://www.paloaltonetworks.com/identity-security?ts=markdown) * Services ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Services [Threat Intel and Incident Response Services](https://www.paloaltonetworks.com/unit42?ts=markdown) * [Assess](https://www.paloaltonetworks.com/unit42/assess?ts=markdown) * [AI Security Assessment](https://www.paloaltonetworks.com/unit42/assess/ai-security-assessment?ts=markdown) * [Attack Surface Assessment](https://www.paloaltonetworks.com/unit42/assess/attack-surface-assessment?ts=markdown) * [Breach Readiness Review](https://www.paloaltonetworks.com/unit42/assess/breach-readiness-review?ts=markdown) * [BEC Readiness Assessment](https://www.paloaltonetworks.com/bec-readiness-assessment?ts=markdown) * [Cloud Security Assessment](https://www.paloaltonetworks.com/unit42/assess/cloud-security-assessment?ts=markdown) * [Compromise Assessment](https://www.paloaltonetworks.com/unit42/assess/compromise-assessment?ts=markdown) * [Cyber Risk Assessment](https://www.paloaltonetworks.com/unit42/assess/cyber-risk-assessment?ts=markdown) * [M\&A Cyber Due Diligence](https://www.paloaltonetworks.com/unit42/assess/mergers-acquisitions-cyber-due-diligence?ts=markdown) * [Penetration Testing](https://www.paloaltonetworks.com/unit42/assess/penetration-testing?ts=markdown) * [Purple Team Exercises](https://www.paloaltonetworks.com/unit42/assess/purple-teaming?ts=markdown) * [Ransomware Readiness Assessment](https://www.paloaltonetworks.com/unit42/assess/ransomware-readiness-assessment?ts=markdown) * [SOC Assessment](https://www.paloaltonetworks.com/unit42/assess/soc-assessment?ts=markdown) * [Supply Chain Risk Assessment](https://www.paloaltonetworks.com/unit42/assess/supply-chain-risk-assessment?ts=markdown) * [Tabletop Exercises](https://www.paloaltonetworks.com/unit42/assess/tabletop-exercise?ts=markdown) * [Unit 42 Retainer](https://www.paloaltonetworks.com/unit42/retainer?ts=markdown) * [Respond](https://www.paloaltonetworks.com/unit42/respond?ts=markdown) * [Cloud Incident Response](https://www.paloaltonetworks.com/unit42/respond/cloud-incident-response?ts=markdown) * [Digital Forensics](https://www.paloaltonetworks.com/unit42/respond/digital-forensics?ts=markdown) * [Incident Response](https://www.paloaltonetworks.com/unit42/respond/incident-response?ts=markdown) * [Managed Detection and Response](https://www.paloaltonetworks.com/unit42/respond/managed-detection-response?ts=markdown) * [Managed Threat Hunting](https://www.paloaltonetworks.com/unit42/respond/managed-threat-hunting?ts=markdown) * [Managed XSIAM](https://www.paloaltonetworks.com/cortex/managed-xsiam?ts=markdown) * [Unit 42 Retainer](https://www.paloaltonetworks.com/unit42/retainer?ts=markdown) * [Transform](https://www.paloaltonetworks.com/unit42/transform?ts=markdown) * [IR Plan Development and Review](https://www.paloaltonetworks.com/unit42/transform/incident-response-plan-development-review?ts=markdown) * [Security Program Design](https://www.paloaltonetworks.com/unit42/transform/security-program-design?ts=markdown) * [Virtual CISO](https://www.paloaltonetworks.com/unit42/transform/vciso?ts=markdown) * [Zero Trust Advisory](https://www.paloaltonetworks.com/unit42/transform/zero-trust-advisory?ts=markdown) [Global Customer Services](https://www.paloaltonetworks.com/services?ts=markdown) * [Education \& Training](https://www.paloaltonetworks.com/services/education?ts=markdown) * [Professional Services](https://www.paloaltonetworks.com/services/consulting?ts=markdown) * [Success Tools](https://www.paloaltonetworks.com/services/customer-success-tools?ts=markdown) * [Support Services](https://www.paloaltonetworks.com/services/solution-assurance?ts=markdown) * [Customer Success](https://www.paloaltonetworks.com/services/customer-success?ts=markdown) [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/logo-unit-42.svg) UNIT 42 RETAINER Custom-built to fit your organization's needs, you can choose to allocate your retainer hours to any of our offerings, including proactive cyber risk management services. Learn how you can put the world-class Unit 42 Incident Response team on speed dial. Learn more](https://www.paloaltonetworks.com/unit42/retainer?ts=markdown) * Partners ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Partners NextWave Partners * [NextWave Partner Community](https://www.paloaltonetworks.com/partners?ts=markdown) * [Cloud Service Providers](https://www.paloaltonetworks.com/partners/nextwave-for-csp?ts=markdown) * [Global Systems Integrators](https://www.paloaltonetworks.com/partners/nextwave-for-gsi?ts=markdown) * [Technology Partners](https://www.paloaltonetworks.com/partners/technology-partners?ts=markdown) * [Service Providers](https://www.paloaltonetworks.com/partners/service-providers?ts=markdown) * [Solution Providers](https://www.paloaltonetworks.com/partners/nextwave-solution-providers?ts=markdown) * [Managed Security Service Providers](https://www.paloaltonetworks.com/partners/managed-security-service-providers?ts=markdown) Take Action * [Portal Login](https://www.paloaltonetworks.com/partners/nextwave-partner-portal?ts=markdown) * [Managed Services Program](https://www.paloaltonetworks.com/partners/managed-security-services-provider-program?ts=markdown) * [Become a Partner](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerregistration?type=becomepartner) * [Request Access](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerregistration?type=requestaccess) * [Find a Partner](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerlocator) [CYBERFORCE CYBERFORCE represents the top 1% of partner engineers trusted for their security expertise. Learn more](https://www.paloaltonetworks.com/cyberforce?ts=markdown) * Company ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Company Palo Alto Networks * [About Us](https://www.paloaltonetworks.com/about-us?ts=markdown) * [Management Team](https://www.paloaltonetworks.com/about-us/management?ts=markdown) * [Investor Relations](https://investors.paloaltonetworks.com) * [Locations](https://www.paloaltonetworks.com/about-us/locations?ts=markdown) * [Ethics \& Compliance](https://www.paloaltonetworks.com/company/ethics-and-compliance?ts=markdown) * [Corporate Responsibility](https://www.paloaltonetworks.com/about-us/corporate-responsibility?ts=markdown) * [Military \& Veterans](https://jobs.paloaltonetworks.com/military) [Why Palo Alto Networks?](https://www.paloaltonetworks.com/why-paloaltonetworks?ts=markdown) * [Precision AI Security](https://www.paloaltonetworks.com/precision-ai-security?ts=markdown) * [Our Platform Approach](https://www.paloaltonetworks.com/why-paloaltonetworks/platformization?ts=markdown) * [Accelerate Your Cybersecurity Transformation](https://www.paloaltonetworks.com/why-paloaltonetworks/nam-cxo-portfolio?ts=markdown) * [Awards \& Recognition](https://www.paloaltonetworks.com/about-us/awards?ts=markdown) * [Customer Stories](https://www.paloaltonetworks.com/customers?ts=markdown) * [Global Certifications](https://www.paloaltonetworks.com/legal-notices/trust-center/compliance?ts=markdown) * [Trust 360 Program](https://www.paloaltonetworks.com/resources/whitepapers/trust-360?ts=markdown) Careers * [Overview](https://jobs.paloaltonetworks.com/) * [Culture \& Benefits](https://jobs.paloaltonetworks.com/en/culture/) [A Newsweek Most Loved Workplace "Businesses that do right by their employees" Read more](https://www.paloaltonetworks.com/company/press/2021/palo-alto-networks-secures-top-ranking-on-newsweek-s-most-loved-workplaces-list-for-2021?ts=markdown) * More ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) More Resources * [Blog](https://www.paloaltonetworks.com/blog/?ts=markdown) * [Unit 42 Threat Research](https://unit42.paloaltonetworks.com/) * [Communities](https://www.paloaltonetworks.com/communities?ts=markdown) * [Content Library](https://www.paloaltonetworks.com/resources?ts=markdown) * [Cyberpedia](https://www.paloaltonetworks.com/cyberpedia?ts=markdown) * [Tech Insider](https://techinsider.paloaltonetworks.com/) * [Knowledge Base](https://knowledgebase.paloaltonetworks.com/) * [Palo Alto Networks TV](https://tv.paloaltonetworks.com/) * [Perspectives of Leaders](https://www.paloaltonetworks.com/perspectives/?ts=markdown) * [Cyber Perspectives Magazine](https://www.paloaltonetworks.com/cybersecurity-perspectives/cyber-perspectives-magazine?ts=markdown) * [Regional Cloud Locations](https://www.paloaltonetworks.com/products/regional-cloud-locations?ts=markdown) * [Tech Docs](https://docs.paloaltonetworks.com/) * [Security Posture Assessment](https://www.paloaltonetworks.com/security-posture-assessment?ts=markdown) * [Threat Vector Podcast](https://unit42.paloaltonetworks.com/unit-42-threat-vector-podcast/) * [Packet Pushers Podcasts](https://www.paloaltonetworks.com/podcasts/packet-pusher?ts=markdown) Connect * [LIVE community](https://live.paloaltonetworks.com/) * [Events](https://events.paloaltonetworks.com/) * [Executive Briefing Center](https://www.paloaltonetworks.com/about-us/executive-briefing-program?ts=markdown) * [Demos](https://www.paloaltonetworks.com/demos?ts=markdown) * [Contact us](https://www.paloaltonetworks.com/company/contact-sales?ts=markdown) [Blog Stay up-to-date on industry trends and the latest innovations from the world's largest cybersecurity Learn more](https://www.paloaltonetworks.com/blog/) * Sign In ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Sign In * Customer * Partner * Employee * [Login to download](https://www.paloaltonetworks.com/login?ts=markdown) * [Join us to become a member](https://www.paloaltonetworks.com/login?screenToRender=traditionalRegistration&ts=markdown) * EN ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Language * [USA (ENGLISH)](https://www.paloaltonetworks.com) * [AUSTRALIA (ENGLISH)](https://www.paloaltonetworks.com.au) * [BRAZIL (PORTUGUÉS)](https://www.paloaltonetworks.com.br) * [CANADA (ENGLISH)](https://www.paloaltonetworks.ca) * [CHINA (简体中文)](https://www.paloaltonetworks.cn) * [FRANCE (FRANÇAIS)](https://www.paloaltonetworks.fr) * [GERMANY (DEUTSCH)](https://www.paloaltonetworks.de) * [INDIA (ENGLISH)](https://www.paloaltonetworks.in) * [ITALY (ITALIANO)](https://www.paloaltonetworks.it) * [JAPAN (日本語)](https://www.paloaltonetworks.jp) * [KOREA (한국어)](https://www.paloaltonetworks.co.kr) * [LATIN AMERICA (ESPAÑOL)](https://www.paloaltonetworks.lat) * [MEXICO (ESPAÑOL)](https://www.paloaltonetworks.com.mx) * [SINGAPORE (ENGLISH)](https://www.paloaltonetworks.sg) * [SPAIN (ESPAÑOL)](https://www.paloaltonetworks.es) * [TAIWAN (繁體中文)](https://www.paloaltonetworks.tw) * [UK (ENGLISH)](https://www.paloaltonetworks.co.uk) * [Contact Us](https://www.paloaltonetworks.com/company/contact-sales?ts=markdown) * [What's New](https://www.paloaltonetworks.com/resources?ts=markdown) * [Get support](https://support.paloaltonetworks.com/SupportAccount/MyAccount) * [Under Attack?](https://start.paloaltonetworks.com/contact-unit42.html) * [Demos and Trials](https://www.paloaltonetworks.com/get-started?ts=markdown) Search All * [Tech Docs](https://docs.paloaltonetworks.com/search) Close search modal [Deploy Bravely --- Secure your AI transformation with Prisma AIRS](https://www.paloaltonetworks.com/deploybravely?ts=markdown) [](https://www.paloaltonetworks.com/?ts=markdown) 1. [Cyberpedia](https://www.paloaltonetworks.com/cyberpedia?ts=markdown) 2. [Cloud Security](https://www.paloaltonetworks.com/cyberpedia/cloud-security?ts=markdown) 3. [API Security](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1?ts=markdown) 4. [What Is Unsafe Consumption of APIs?](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10?ts=markdown) Table of Contents * [What is Security Misconfiguration?](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8?ts=markdown) * [API8:2023 - Security Misconfiguration Explained](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#explained?ts=markdown) * [Understanding Security Misconfiguration in API Security](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#understanding?ts=markdown) * [How Security Misconfiguration Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#how?ts=markdown) * [The Business Impact of Security Misconfiguration](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#business?ts=markdown) * [Identifying Security Misconfiguration in Your APIs](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#identifying?ts=markdown) * [Preventing Security Misconfiguration: Best Practices](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#preventing?ts=markdown) * [Security Misconfiguration FAQs](https://www.paloaltonetworks.com/cyberpedia/security-misconfiguration-api8#faqs?ts=markdown) * [What Is Broken Object Level Authorization?](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1?ts=markdown) * [API1:2023 - Broken Object Level Authorization Explained](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#explained?ts=markdown) * [Understanding Object-Level Authorization in API Security](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#understanding?ts=markdown) * [How Broken Object Level Authorization Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#how?ts=markdown) * [The Business Impact of Broken Object Level Authorization](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#business?ts=markdown) * [Identifying Broken Object Level Authorization in Your APIs](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#apis?ts=markdown) * [Preventing Broken Object Level Authorization: Best Practices](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#preventing?ts=markdown) * [Broken Object Level Authorization FAQs](https://www.paloaltonetworks.com/cyberpedia/broken-object-level-authentication-api1#faqs?ts=markdown) * [What Is API Security?](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security?ts=markdown) * [API Security Explained](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#api?ts=markdown) * [Definition of an API](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#definition?ts=markdown) * [Why API Security Is Important](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#why?ts=markdown) * [Traditional Approach to Web Application Security](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#traditional?ts=markdown) * [Anatomy of an API Attack](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#anatomy?ts=markdown) * [API Security Risks](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#risks?ts=markdown) * [API Security for SOAP, REST and GraphQL](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#graphql?ts=markdown) * [API Security Best Practices](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#best?ts=markdown) * [Cortex Cloud's API Security Solution](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#prisma?ts=markdown) * [API Security FAQs](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security#faqs?ts=markdown) * What Is Unsafe Consumption of APIs? * [API10:2023 - Unsafe Consumption of APIs Explained](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#explained?ts=markdown) * [Understanding Unsafe Consumption of APIs in API Security](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#understanding?ts=markdown) * [How Unsafe Consumption of APIs Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#how?ts=markdown) * [The Business Impact of Unsafe Consumption of APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#business?ts=markdown) * [Identifying Unsafe Consumption of APIs in Your APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#identifying?ts=markdown) * [Preventing Unsafe Consumption of APIs: Best Practices](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#preventing?ts=markdown) * [Unsafe Consumption of APIs FAQs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#faqs?ts=markdown) * [What Is Server Side Request Forgery?](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7?ts=markdown) * [API7:2023 - Server Side Request Forgery Explained](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#explained?ts=markdown) * [Understanding Server Side Request Forgery in API Security](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#understanding?ts=markdown) * [How Server Side Request Forgery Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#how?ts=markdown) * [The Business Impact of Server Side Request Forgery](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#forgery?ts=markdown) * [Identifying Server Side Request Forgery in Your APIs](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#apis?ts=markdown) * [Preventing Server Side Request Forgery: Best Practices](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#preventing?ts=markdown) * [Server Side Request Forgery FAQs](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7#faqs?ts=markdown) * [What Is Unrestricted Resource Consumption?](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption?ts=markdown) * [API4:2023 - Unrestricted Resource Consumption Explained](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#api4?ts=markdown) * [Understanding Unrestricted Resource Consumption in API Security](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#understanding?ts=markdown) * [How Unrestricted Resource Consumption Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#how?ts=markdown) * [The Business Impact of Unrestricted Resource Consumption](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#consumption?ts=markdown) * [Identifying Unrestricted Resource Consumption in Your APIs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#identifying?ts=markdown) * [Preventing Unrestricted Resource Consumption: Best Practices](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#preventing?ts=markdown) * [Unrestricted Resource Consumption FAQs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-resource-consumption#faqs?ts=markdown) * [What Is Unrestricted Access to Sensitive Business Flows?](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows?ts=markdown) * [API6:2023 - Unrestricted Access to Sensitive Business Flows Explained](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#explained?ts=markdown) * [Understanding Unrestricted Access to Sensitive Business Flows in API Security](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#understanding?ts=markdown) * [How Unrestricted Access to Sensitive Business Flows Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#how?ts=markdown) * [The Business Impact of Unrestricted Access to Sensitive Business Flows](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#flows?ts=markdown) * [Identifying Unrestricted Access to Sensitive Business Flows in Your APIs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#identifying?ts=markdown) * [Preventing Unrestricted Access to Sensitive Business Flows: Best Practices](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#preventing?ts=markdown) * [Unrestricted Access to Sensitive Business Flows FAQs](https://www.paloaltonetworks.com/cyberpedia/unrestricted-access-sensitive-business-flows#faqs?ts=markdown) * [What Is Broken Function Level Authorization?](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization?ts=markdown) * [API5:2023 - Broken Function Level Authorization Explained](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#broken?ts=markdown) * [Understanding Broken Function Level Authorization in API Security](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#understanding?ts=markdown) * [How Broken Function Level Authorization Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#how?ts=markdown) * [The Business Impact of Broken Function Level Authorization](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#business?ts=markdown) * [Identifying Broken Function Level Authorization in Your APIs](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#identifying?ts=markdown) * [Preventing Broken Function Level Authorization: Best Practices](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#preventing?ts=markdown) * [Broken Function Level Authorization FAQs](https://www.paloaltonetworks.com/cyberpedia/broken-function-level-authorization#faqs?ts=markdown) * [What Is Broken Object Property Level Authorization?](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization?ts=markdown) * [API3:2023 - Broken Object Property Level Authorization Explained](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#explained?ts=markdown) * [Understanding Broken Object Property Level Authorization](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#understanding?ts=markdown) * [How Broken Object Property Level Authorization Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#how?ts=markdown) * [The Business Impact of Broken Object Property Level Authorization](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#business?ts=markdown) * [Identifying Broken Object Property Level Authorization in Your APIs](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#identifying?ts=markdown) * [Preventing Broken Object Property Level Authorization: Best Practices](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#preventing?ts=markdown) * [Broken Object Property Level Authorization FAQs](https://www.paloaltonetworks.com/cyberpedia/broken-object-property-level-authorization#faqs?ts=markdown) * [API Security Checklist for Modern Application Teams](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist?ts=markdown) * [Discover and Classify All APIs](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#discover?ts=markdown) * [Apply Core API Security Controls](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#apply?ts=markdown) * [Protect API Data at Every Layer](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#protect?ts=markdown) * [Secure API Endpoints and Runtime Behavior](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#secure?ts=markdown) * [Continuously Monitor, Test, and Improve](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#monitor?ts=markdown) * [Building Resilience Through Systematic Execution](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#resilience?ts=markdown) * [API Security Checklist FAQs](https://www.paloaltonetworks.com/cyberpedia/api-security-checklist#faqs?ts=markdown) * [API Security Monitoring](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring?ts=markdown) * [What to Monitor: Traffic, Sessions, Anomalies, Threats](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#monitor?ts=markdown) * [Services and Tools for Monitoring APIs](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#services?ts=markdown) * [Response Mechanisms: Threat Detection, Response, Remediation for APIs](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#response?ts=markdown) * [Ensuring the Best API Security Posture with Monitoring and Continuous Improvement](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#ensuring?ts=markdown) * [Building a Monitoring-Driven API Security Lifecycle](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#building?ts=markdown) * [API Security Monitoring FAQs](https://www.paloaltonetworks.com/cyberpedia/api-security-monitoring#faqs?ts=markdown) * [What Is API Endpoint Security](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security?ts=markdown) * [Threats Targeting Endpoints](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security#threats?ts=markdown) * [How to Secure API Endpoints](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security#secure?ts=markdown) * [Endpoint Protection Strategies](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security#endpoint?ts=markdown) * [Building Endpoint-Aware API Security Programs](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security#programs?ts=markdown) * [API Endpoint Security FAQs](https://www.paloaltonetworks.com/cyberpedia/api-endpoint-security#faqs?ts=markdown) * [What Is Improper Inventory Management?](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9?ts=markdown) * [API9:2023 - Improper Inventory Management Explained](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#explained?ts=markdown) * [Understanding Improper Inventory Management in API Security](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#understanding?ts=markdown) * [How Improper Inventory Management Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#how?ts=markdown) * [The Business Impact of Improper Inventory Management](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#management?ts=markdown) * [Identifying Improper Inventory Management in Your APIs](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#identifying?ts=markdown) * [Preventing Improper Inventory Management: Best Practices](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#preventing?ts=markdown) * [Improper Inventory Management FAQs](https://www.paloaltonetworks.com/cyberpedia/improper-inventory-management-api9#faqs?ts=markdown) * [Cloud API Security: Strategy for the DevOps Era](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy?ts=markdown) * [The Role of API Keys and Secrets in Cloud APIs --- Risks and Misuses](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#role?ts=markdown) * [The Gateway Layer in Cloud APIs: Why a Web API Security Gateway Is Critical](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#gateway?ts=markdown) * [Monitoring and Protecting APIs in Real Time in Cloud/DevOps Contexts](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#monitoring?ts=markdown) * [Strategy Checklist: Best Practices for Cloud API Security in DevOps](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#strategy?ts=markdown) * [Conclusion: Bridging DevOps Velocity with Secure API Posture](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#conclusion?ts=markdown) * [Cloud API Security FAQs](https://www.paloaltonetworks.com/cyberpedia/cloud-api-security-strategy#faqs?ts=markdown) * [What Is Broken Authentication?](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2?ts=markdown) * [API2:2023 - Broken Authentication Explained](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#API2-2023?ts=markdown) * [Understanding Broken Authentication in API Security](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#understanding?ts=markdown) * [How Broken Authentication Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#broken?ts=markdown) * [The Business Impact of Broken Authentication](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#business?ts=markdown) * [Identifying Broken Authentication in Your APIs](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#identifying?ts=markdown) * [Preventing Broken Authentication: Best Practices](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#preventing?ts=markdown) * [Broken Authentication FAQs](https://www.paloaltonetworks.com/cyberpedia/broken-authentication-api2#faqs?ts=markdown) # What Is Unsafe Consumption of APIs? 3 min. read Table of Contents * * [API10:2023 - Unsafe Consumption of APIs Explained](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#explained?ts=markdown) * [Understanding Unsafe Consumption of APIs in API Security](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#understanding?ts=markdown) * [How Unsafe Consumption of APIs Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#how?ts=markdown) * [The Business Impact of Unsafe Consumption of APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#business?ts=markdown) * [Identifying Unsafe Consumption of APIs in Your APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#identifying?ts=markdown) * [Preventing Unsafe Consumption of APIs: Best Practices](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#preventing?ts=markdown) * [Unsafe Consumption of APIs FAQs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#faqs?ts=markdown) 1. API10:2023 - Unsafe Consumption of APIs Explained * * [API10:2023 - Unsafe Consumption of APIs Explained](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#explained?ts=markdown) * [Understanding Unsafe Consumption of APIs in API Security](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#understanding?ts=markdown) * [How Unsafe Consumption of APIs Manifests in Real-World APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#how?ts=markdown) * [The Business Impact of Unsafe Consumption of APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#business?ts=markdown) * [Identifying Unsafe Consumption of APIs in Your APIs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#identifying?ts=markdown) * [Preventing Unsafe Consumption of APIs: Best Practices](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#preventing?ts=markdown) * [Unsafe Consumption of APIs FAQs](https://www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10#faqs?ts=markdown) Third-party API integrations create attack vectors when developers trust external data sources more than user input. API10:2023 Unsafe Consumption of APIs addresses the security gap that emerges when applications consume data from external APIs without applying defensive coding practices. Organizations face SQL injection, cross-site scripting, data breaches, and service disruption through compromised or malicious third-party services. Inside you'll find technical explanations of how unsafe consumption manifests, real-world attack scenarios, business impact analysis, identification methods, and prevention strategies for securing your API integration architecture. ## API10:2023 - Unsafe Consumption of APIs Explained Unsafe consumption of APIs occurs when developers integrate third-party API data into their applications while treating it with less scrutiny than user-supplied input. Organizations routinely validate, sanitize, and restrict [data flowing](https://www.paloaltonetworks.com/cyberpedia/data-flow-diagram?ts=markdown) directly from end users, yet they often skip identical protections when consuming responses from external APIs. The distinction matters because attackers exploit precisely the asymmetry between rigorous input validation and relaxed third-party data handling. ### The Trust Gap in API Integration Developers extend implicit trust to third-party APIs based on brand reputation rather than security posture. A payment processor's API, a mapping service's geocoding endpoint, or a weather data provider's response all receive preferential treatment during integration. Development teams assume the vendor handles security upstream, which removes the perceived need for defensive coding on the consuming side. The assumption creates exposure because trust replaces verification. [Cloud-native architectures](https://www.paloaltonetworks.com/cyberpedia/what-is-cloud-native?ts=markdown) amplify the risk through service mesh patterns and microservices dependencies. Each service consumes data from multiple upstream APIs, and a single weak integration point cascades across the entire application stack. The attack surface expands geometrically as third-party dependencies multiply. ### A Distinct Risk Category Unlike injection vulnerabilities or broken authentication, unsafe consumption addresses a scenario where you don't control the API delivering data to your system. Traditional [API security](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security?ts=markdown) focuses on protecting your own endpoints from malicious actors. API10:2023 flips the model by examining how your application handles responses from APIs you integrate with but don't operate. The risk sits at the intersection of supply chain security and input validation. ### When Trusted Sources Become Attack Vectors Third-party APIs don't need malicious intent to serve as exploitation channels. Compromised vendor infrastructure, misconfigurations in their deployment pipeline, or vulnerabilities in their upstream dependencies can all inject malicious payloads into otherwise legitimate API responses. An attacker who gains control of a widely used geocoding API can potentially compromise every application consuming its data. The vendor's security incident becomes your security incident when you've built no defensive layers around their responses. ## Understanding Unsafe Consumption of APIs in API Security API integration dependencies create a security model where your defensive posture extends beyond your infrastructure to include every external service your applications consume. ### The Trust Problem in Development Practice Security standards weaken the moment data originates from a recognized third-party API. Teams apply strict input validation, parameterized queries, and content security policies to user-supplied data while exempting API responses from identical scrutiny. The assumption follows a simple logic: if the service provider handles millions of requests daily and serves Fortune 500 clients, their data must be clean. Development velocity pressures compound the problem because additional validation layers slow down integration timelines and add complexity to deployment pipelines. Rate limiting, timeout configurations, and resource allocation controls get deprioritized during third-party API integration. Engineers configure generous timeout windows to accommodate variable response times and skip implementing circuit breakers because service interruptions seem unlikely from established providers. The relaxed standards create openings for resource exhaustion and denial-of-service conditions when third-party responses behave unexpectedly. ### How Third-Party APIs Become Attack Vectors Infrastructure compromise at the vendor level turns legitimate API endpoints into payload delivery mechanisms. An attacker who gains access to a third-party service's database can seed malicious content that your application faithfully retrieves and processes. The enrichment API you use to validate business addresses might return carefully crafted [SQL injection](https://www.paloaltonetworks.com/cyberpedia/sql-injection?ts=markdown) strings embedded in seemingly legitimate address data. Your application executes the payload because it trusts the source. Misconfigurations in third-party API deployments expose exploitation opportunities without requiring full infrastructure compromise. An API that accepts redirects without validation becomes a tool for credential theft. Adversary-in-the-middle attacks succeed when applications consume third-party data over unencrypted channels or skip certificate validation to simplify local development. ### The Downstream Risk Chain Unsanitized third-party data flows through your application stack and interacts with databases, message queues, downstream [microservices](https://www.paloaltonetworks.com/cyberpedia/what-are-microservices?ts=markdown), and frontend components. A malicious payload embedded in an API response executes at each processing stage where validation doesn't occur. SQL injection succeeds when you directly interpolate third-party response fields into database queries. [Cross-site scripting](https://www.paloaltonetworks.com/cyberpedia/xss-cross-site-scripting?ts=markdown) vulnerabilities emerge when frontend components render third-party data without encoding. Following redirects blindly exposes sensitive request data to attacker-controlled infrastructure. An API that faithfully repeats POST requests to redirect destinations leaks authentication tokens, user identifiers, and payload data to unauthorized parties. The attack succeeds because your application treats redirect responses as legitimate instructions rather than potential threats. Resource exhaustion occurs when applications allocate memory or processing capacity based on third-party response sizes without imposing limits. An API that returns unexpectedly large payloads or streaming responses consumes available resources and degrades service availability. ### Your Security Perimeter Extends to Your Dependencies [Supply chain security](https://www.paloaltonetworks.com/cyberpedia/what-is-secure-software-development-lifecycle?ts=markdown) principles apply directly to API consumption patterns. Each third-party integration represents a trust relationship where their security posture directly impacts your risk exposure. Vendor security incidents propagate through integration points and affect every application consuming their services. ## How Unsafe Consumption of APIs Manifests in Real-World APIs Vulnerability patterns emerge consistently across API integration architectures when developers relax defensive coding practices for third-party data sources. Applications frequently pass third-party API responses directly into database queries without applying sanitization or parameterization. An address enrichment service that returns business location data becomes an injection vector when attackers seed the third-party database with SQL payloads. Your application requests enrichment data for a specific business, receives a response containing malicious query fragments, and executes those fragments when constructing local database operations. The attack succeeds because the integration code treats response fields as trusted strings rather than potentially hostile input. Cross-site scripting vulnerabilities follow identical patterns when third-party content reaches frontend components without encoding. Product description APIs, user-generated content aggregators, and social media integration endpoints all deliver HTML and JavaScript that applications render directly in browsers. Malicious script tags embedded in API responses execute in user sessions because validation happens only for data submitted through your own forms. Repository integration services demonstrate how file and project names can carry injection payloads. An attacker creates a Git repository with a name containing SQL commands or shell metacharacters. When your [CI/CD pipeline](https://www.paloaltonetworks.com/cyberpedia/what-is-the-ci-cd-pipeline-and-ci-cd-security?ts=markdown) consumes repository metadata through integration APIs, the malicious naming injects commands into build scripts or database operations that track deployment artifacts. ### Communication Security Gaps Unencrypted channels between your application and third-party APIs expose request and response data to interception. Development teams often configure HTTP connections for local testing and forget to enforce TLS in production deployments. The gap allows adversary-in-the-middle attacks where intercepted responses get modified before reaching your application. Attackers inject payloads into legitimate API traffic without compromising the vendor's infrastructure. Certificate validation skips frequently appear in integration code when developers encounter certificate errors during testing. Disabling verification simplifies troubleshooting but removes the cryptographic assurance that responses originate from legitimate endpoints. ### Redirect Exploitation Applications that follow HTTP redirects automatically expose sensitive data to unauthorized destinations. A compromised third-party API returns 308 Permanent Redirect responses pointing to attacker-controlled servers. Your application faithfully repeats the original request, including authentication headers and POST body data, to the malicious endpoint. Medical records, financial data, and user credentials leak through a blind redirect because integration logic treats redirects as ordinary protocol behavior rather than potential security events. ### Resource Exhaustion Risks Missing constraints on third-party response handling create denial-of-service conditions. APIs that return unbounded streaming responses or unexpectedly large payloads consume available memory and processing capacity. Applications allocate buffers based on Content-Length headers without imposing maximum limits, which allows malicious or compromised third-party services to exhaust system resources. Timeout configurations get omitted entirely or set to excessive values during integration. A third-party service that delays responses indefinitely ties up connection pools, worker threads, and database connections. The resource exhaustion cascades through your application stack as upstream services wait for third-party responses. ### Security Posture Blindness Organizations integrate third-party APIs based on functional requirements and vendor reputation without evaluating security controls. No assessment occurs for the provider's authentication mechanisms, data handling practices, or incident response capabilities. Ongoing monitoring remains absent after initial integration, which means vendor security degradation goes undetected until breaches occur. ## The Business Impact of Unsafe Consumption of APIs Financial and operational consequences from unsafe API consumption extend far beyond technical remediation costs. ### Data Breach Exposure and Regulatory Penalties Compromised third-party integrations leak customer records, payment information, and protected health data to unauthorized parties. Organizations face notification requirements under [GDPR](https://www.paloaltonetworks.com/cyberpedia/gdpr-compliance?ts=markdown), [CCPA](https://www.paloaltonetworks.com/cyberpedia/ccpa?ts=markdown), [HIPAA](https://www.paloaltonetworks.com/cyberpedia/what-is-hipaa?ts=markdown), and sector-specific regulations regardless of where the vulnerability originated. Regulatory bodies assess penalties based on inadequate data protection controls, and outsourcing security to third-party providers doesn't transfer legal liability. Financial penalties reach millions for breaches involving [sensitive personal information](https://www.paloaltonetworks.com/cyberpedia/sensitive-data?ts=markdown). Compliance frameworks require organizations to maintain data processing agreements and conduct vendor risk assessments before integration. Failures in third-party API consumption typically reveal gaps in vendor management programs, which trigger additional scrutiny across the entire vendor portfolio during regulatory investigations. ### Operational Disruption and Availability Loss Resource exhaustion from malicious third-party responses degrades application performance and creates service outages. Customer-facing applications become unresponsive when integration points consume excessive memory or block critical processing threads. Revenue loss accumulates during downtime while engineering teams diagnose whether problems originate internally or from upstream dependencies. Cascading failures propagate through microservices architectures when one compromised integration affects multiple downstream consumers. A single vulnerable API integration point can degrade system-wide performance as timeouts ripple through service meshes and overwhelm circuit breakers. ### Reputational and Market Position Damage Customers attribute security incidents to your brand regardless of third-party involvement in the attack chain. Public disclosure requirements name your organization as the breach source even when attackers exploited vendor infrastructure. Market confidence erodes when incidents reveal inadequate security controls around integration architectures, which affects customer retention and acquisition costs. Competitive positioning suffers when security incidents force organizations to disable third-party integrations that differentiate their product offerings. Features dependent on external APIs become unavailable during incident response, which creates openings for competitors with more resilient integration strategies. ### Legal Liability Beyond Direct Damages Class action litigation follows data breaches involving unsafe API consumption because courts hold organizations responsible for protecting data throughout its lifecycle. Contractual obligations with customers and partners include security representations that become actionable when third-party integration failures cause breaches. Insurance coverage disputes emerge when carriers argue that inadequate vendor management constitutes negligence rather than covered security incidents. ## Identifying Unsafe Consumption of APIs in Your APIs Detection requires systematic analysis of integration patterns, code paths, and runtime behavior across your API consumption surface. Start by enumerating every external API your applications consume. Service mesh telemetry, [API gateway](https://www.paloaltonetworks.com/cyberpedia/what-is-api-gateway?ts=markdown) logs, and dependency management tools reveal active integrations, but legacy code paths and rarely executed functions often hide undocumented third-party dependencies. Network traffic analysis captures actual API calls during runtime, which exposes integrations absent from architecture diagrams. Document data flows for each integration point. Map which sensitive data types travel to third-party services and what response fields your application processes. Payment processing APIs receive transaction details, geocoding services consume addresses, and analytics platforms ingest user behavior data. Understanding data flow patterns reveals where [data breaches](https://www.paloaltonetworks.com/cyberpedia/data-breach?ts=markdown) would cause maximum damage. ### Evaluating Third-Party Security Controls Security questionnaires and vendor documentation provide baseline assessment data. [SOC 2](https://www.paloaltonetworks.com/cyberpedia/soc-2?ts=markdown) Type II reports, ISO 27001 certifications, and [PCI DSS](https://www.paloaltonetworks.com/cyberpedia/pci-dss?ts=markdown) attestations indicate mature security programs, though compliance frameworks don't guarantee secure API implementations. Review the provider's public security advisories and incident disclosure history to understand their vulnerability management and response capabilities. Technical assessment goes deeper than certifications. Verify that third-party APIs enforce TLS 1.2 or higher and reject weak cipher suites. Test whether APIs validate client certificates when mutual TLS applies. Check API documentation for rate limiting, input validation, and error handling specifications. ### Code Review for Integration Vulnerabilities Search codebases for HTTP client instantiation and third-party SDK imports to locate integration points. Trace how response data flows from API calls into database operations, template rendering, and business logic execution. Look for direct string interpolation of response fields into SQL queries or HTML output, which indicates missing sanitization. Redirect handling logic warrants specific scrutiny. Applications using HTTP client libraries with automatic redirect following need explicit configuration to either disable redirects or implement allowlist validation. Review whether sensitive headers and request bodies get included when following redirects. Examine timeout and resource limit configurations around third-party API calls. Missing timeouts create availability risks, while unbounded memory allocation for response bodies enables resource exhaustion attacks. ### Testing Integration Security Controlled testing environments allow injection of malicious payloads into third-party response data. If you manage test instances of third-party services, populate them with SQL injection strings, XSS payloads, and oversized data to verify your application's defensive controls. Dynamic application security testing tools can intercept and modify third-party API responses during functional testing to simulate compromised providers. Redirect exploitation testing requires configuring mock API endpoints that return various redirect status codes pointing to attacker-controlled domains. Verify that your application refuses to follow redirects or validates destinations against allowlists. ### Monitoring Integration Behavior Instrument third-party API client code to emit detailed telemetry about request destinations, response codes, payload sizes, and processing duration. Anomaly detection rules identify unusual patterns like unexpected redirect responses, response sizes exceeding historical norms, or processing times suggesting timeout misconfigurations. Alert when API calls attempt unencrypted connections or certificate validation failures occur. ## Preventing Unsafe Consumption of APIs: Best Practices Mitigation strategies center on extending defensive coding practices uniformly across all data sources, regardless of origin. Third-party API responses require identical validation rigor as user-submitted data. Implement schema validation against expected response structures before processing any fields. Type checking, length constraints, and format validation apply to every field extracted from third-party responses. String fields destined for database queries need parameterized statement handling or prepared statements, even when sourced from trusted providers. Context-specific output encoding prevents injection attacks when third-party data reaches databases, templates, or shell commands. SQL parameterization handles database operations, HTML entity encoding protects against cross-site scripting, and command argument escaping secures shell invocations. Validation occurs at integration boundaries before data enters your processing pipeline, rather than deeper in the call stack where defensive controls get overlooked. ### Enforcing Communication Security TLS 1.3 or TLS 1.2 with strong cipher suites becomes mandatory for every third-party API connection. HTTP client configuration needs explicit TLS enforcement that prevents protocol downgrade attempts. Certificate validation includes hostname verification, chain-of-trust validation, and certificate revocation checking through OCSP or CRL mechanisms. Certificate pinning adds protection against compromised certificate authorities when consuming high-value third-party APIs. Pin to intermediate certificates rather than leaf certificates to accommodate provider certificate rotation. Monitor pinning failures as security events because they indicate potential adversary-in-the-middle attacks or provider infrastructure changes requiring validation. ### Implementing Redirect Controls Disable automatic redirect following in HTTP client libraries and implement explicit redirect handling logic. Maintain allowlists of domains and URL patterns where your application permits redirects. Validate redirect destinations against allowlists before issuing follow-up requests, and strip authentication headers when crossing domain boundaries. Limit redirect chains to two or three hops maximum to prevent redirect loop exploitation and resource exhaustion. Log every redirect encounter with source API, destination URL, and HTTP status code for security analysis. Alert when third-party APIs return redirects to unexpected domains or when redirect rates exceed baseline patterns. ### Managing Resource Allocation Configure connection timeouts between two and five seconds for third-party API calls, depending on expected latency. Read timeouts prevent indefinite waiting when responses stream slowly. Total request timeouts encompass the entire request-response cycle, including connection establishment, data transfer, and processing. Impose maximum response size limits before allocating memory for third-party payloads. Stream large responses to disk or process them incrementally rather than loading complete responses into memory. Circuit breaker patterns detect failing third-party services and prevent cascading failures by rejecting requests after threshold error rates occur. ### Conducting Vendor Security Assessments Security questionnaires during vendor evaluation should cover encryption requirements, authentication mechanisms, rate limiting, logging practices, and incident response procedures. Request recent penetration test results, [vulnerability scan](https://www.paloaltonetworks.com/cyberpedia/vulnerability-scanning?ts=markdown) reports, and compliance audit findings. Review the vendor's public security advisories to understand their disclosure practices and vulnerability remediation timelines. Contractual agreements need explicit security requirements, including data handling standards, breach notification timelines, and liability allocation for security incidents. Annual reassessment ensures vendor security posture remains acceptable as their infrastructure and threat landscape evolve. ### Building Defense Layers Segment third-party integrations into isolated network zones or separate microservices. Service accounts accessing third-party APIs operate with minimum necessary privileges and rotate credentials according to policy schedules. API gateways provide centralized control points for enforcing security policies, logging traffic, and implementing rate limiting across all third-party integrations. Comprehensive logging captures request payloads, response data, processing outcomes, and error conditions for security investigations and forensic analysis. ## Unsafe Consumption of APIs FAQs ### What is Server-Side Request Forgery (SSRF)? Server-Side Request Forgery occurs when attackers manipulate your application into making requests to unintended destinations. Third-party API integrations amplify SSRF risk when applications construct URLs from external data without validation. Attackers exploit vulnerable integrations to probe internal networks, access cloud metadata services, or exfiltrate data through requests your application initiates on their behalf. ### What are Transitive Dependencies? Transitive dependencies represent indirect software components your application relies on through direct dependencies. Third-party APIs consume their own upstream services, creating dependency chains where vulnerabilities propagate across multiple integration layers. A compromised service three levels deep in your dependency graph can inject malicious data that flows through intermediary APIs into your application without direct visibility. ### What is Egress Filtering? Egress filtering controls outbound network traffic from your application infrastructure. Network policies restrict which external domains and IP addresses your services can reach, limiting third-party API destinations to explicitly approved endpoints. Egress controls prevent data exfiltration when compromised third-party integrations attempt redirects or connections to attacker-controlled infrastructure beyond your authorized vendor list. ### What is API Schema Validation? API schema validation enforces structural contracts on request and response payloads using specifications like OpenAPI or JSON Schema. Schema validation verifies third-party response data matches expected types, formats, and field requirements before your application processes values. Validation failures reject malformed or malicious responses at integration boundaries, preventing injection attacks through unexpected data structures. ### What is Webhook Security? Webhook security addresses risks when third-party services push data to your application endpoints rather than responding to your requests. Webhooks require signature verification to authenticate event sources, replay attack prevention through timestamp validation, and rate limiting to prevent resource exhaustion. Unsigned or improperly validated webhooks let attackers inject malicious events into your processing pipeline. ### What is Data Provenance? Data provenance tracks the origin, transformations, and custody chain of information flowing through your systems. Provenance logging records which third-party APIs supplied specific data fields, when ingestion occurred, and which downstream components processed values. Detailed provenance enables rapid incident response when vendor compromises require identifying all data sourced from affected integrations. Related Content [Secure Your Application Programming Interfaces (APIs) API security is critical for application protection. Gain complete visibility, protect against threats, and eliminate blind spots with our tipsheet.](https://www.paloaltonetworks.com/resources/datasheets/tip-sheet-secure-your-apis?ts=markdown) [Securing the API Attack Surface In partnership with the ESG research team, we surveyed IT, cybersecurity and application development professionals to uncover the latest trends in API security.](https://www.paloaltonetworks.com/resources/research/api-security-statistics-report?ts=markdown) [API Security API security involves real-time protection against OWASP Top 10 attacks, DoS, and bot attacks, including SQL injection and cross-site scripting.](https://www.paloaltonetworks.com/cortex/cloud/api-security?ts=markdown) [Secure APIs in the Cloud-Native Era Cloud-native applications rely on APIs to function, and attackers know it. Every connection between microservices is a potential entry point for threat actors without continuous AP...](https://www.paloaltonetworks.com/resources/whitepapers/api-security-in-the-cloud-native-era?ts=markdown) ![Share page on facebook](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/facebook-circular-icon.svg) ![Share page on linkedin](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/linkedin-circular-icon.svg) [![Share page by an email](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/email-circular-icon.svg)](mailto:?subject=What%20Is%20Unsafe%20Consumption%20of%20APIs%3F&body=Unsafe%20Consumption%20of%20APIs%3A%20Third-party%20integrations%20create%20attack%20vectors%20through%20trust%20gaps.%20Learn%20scenarios%2C%20impact%2C%20detection%20methods%2C%20and%20prevention.%20at%20https%3A//www.paloaltonetworks.com/cyberpedia/unsafe-consumption-api-api10) Back to Top [Previous](https://www.paloaltonetworks.com/cyberpedia/what-is-api-security?ts=markdown) What Is API Security? [Next](https://www.paloaltonetworks.com/cyberpedia/server-side-request-forgery-api7?ts=markdown) What Is Server Side Request Forgery? {#footer} ## Products and Services * [AI-Powered Network Security Platform](https://www.paloaltonetworks.com/network-security?ts=markdown) * [Secure AI by Design](https://www.paloaltonetworks.com/precision-ai-security/secure-ai-by-design?ts=markdown) * [Prisma AIRS](https://www.paloaltonetworks.com/prisma/prisma-ai-runtime-security?ts=markdown) * [AI Access Security](https://www.paloaltonetworks.com/sase/ai-access-security?ts=markdown) * [Cloud Delivered Security Services](https://www.paloaltonetworks.com/network-security/security-subscriptions?ts=markdown) * [Advanced Threat Prevention](https://www.paloaltonetworks.com/network-security/advanced-threat-prevention?ts=markdown) * [Advanced URL Filtering](https://www.paloaltonetworks.com/network-security/advanced-url-filtering?ts=markdown) * [Advanced WildFire](https://www.paloaltonetworks.com/network-security/advanced-wildfire?ts=markdown) * [Advanced DNS Security](https://www.paloaltonetworks.com/network-security/advanced-dns-security?ts=markdown) * [Enterprise Data Loss Prevention](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Enterprise IoT Security](https://www.paloaltonetworks.com/network-security/enterprise-device-security?ts=markdown) * [Medical IoT Security](https://www.paloaltonetworks.com/network-security/medical-device-security?ts=markdown) * [Industrial OT Security](https://www.paloaltonetworks.com/network-security/medical-device-security?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) * [Next-Generation Firewalls](https://www.paloaltonetworks.com/network-security/next-generation-firewall?ts=markdown) * [Hardware Firewalls](https://www.paloaltonetworks.com/network-security/hardware-firewall-innovations?ts=markdown) * [Software Firewalls](https://www.paloaltonetworks.com/network-security/software-firewalls?ts=markdown) * [Strata Cloud Manager](https://www.paloaltonetworks.com/network-security/strata-cloud-manager?ts=markdown) * [SD-WAN for NGFW](https://www.paloaltonetworks.com/network-security/sd-wan-subscription?ts=markdown) * [PAN-OS](https://www.paloaltonetworks.com/network-security/pan-os?ts=markdown) * [Panorama](https://www.paloaltonetworks.com/network-security/panorama?ts=markdown) * [Secure Access Service Edge](https://www.paloaltonetworks.com/sase?ts=markdown) * [Prisma SASE](https://www.paloaltonetworks.com/sase?ts=markdown) * [Application Acceleration](https://www.paloaltonetworks.com/sase/app-acceleration?ts=markdown) * [Autonomous Digital Experience Management](https://www.paloaltonetworks.com/sase/adem?ts=markdown) * [Enterprise DLP](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Prisma Access](https://www.paloaltonetworks.com/sase/access?ts=markdown) * [Prisma Browser](https://www.paloaltonetworks.com/sase/prisma-browser?ts=markdown) * [Prisma SD-WAN](https://www.paloaltonetworks.com/sase/sd-wan?ts=markdown) * [Remote Browser Isolation](https://www.paloaltonetworks.com/sase/remote-browser-isolation?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) * [AI-Driven Security Operations Platform](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cloud Security](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Cortex Cloud](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Application Security](https://www.paloaltonetworks.com/cortex/cloud/application-security?ts=markdown) * [Cloud Posture Security](https://www.paloaltonetworks.com/cortex/cloud/cloud-posture-security?ts=markdown) * [Cloud Runtime Security](https://www.paloaltonetworks.com/cortex/cloud/runtime-security?ts=markdown) * [Prisma Cloud](https://www.paloaltonetworks.com/prisma/cloud?ts=markdown) * [AI-Driven SOC](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cortex XSIAM](https://www.paloaltonetworks.com/cortex/cortex-xsiam?ts=markdown) * [Cortex XDR](https://www.paloaltonetworks.com/cortex/cortex-xdr?ts=markdown) * [Cortex XSOAR](https://www.paloaltonetworks.com/cortex/cortex-xsoar?ts=markdown) * [Cortex Xpanse](https://www.paloaltonetworks.com/cortex/cortex-xpanse?ts=markdown) * [Unit 42 Managed Detection \& Response](https://www.paloaltonetworks.com/cortex/managed-detection-and-response?ts=markdown) * [Managed XSIAM](https://www.paloaltonetworks.com/cortex/managed-xsiam?ts=markdown) * [Threat Intel and Incident Response Services](https://www.paloaltonetworks.com/unit42?ts=markdown) * [Proactive Assessments](https://www.paloaltonetworks.com/unit42/assess?ts=markdown) * [Incident Response](https://www.paloaltonetworks.com/unit42/respond?ts=markdown) * [Transform Your Security Strategy](https://www.paloaltonetworks.com/unit42/transform?ts=markdown) * [Discover Threat Intelligence](https://www.paloaltonetworks.com/unit42/threat-intelligence-partners?ts=markdown) ## Company * [About Us](https://www.paloaltonetworks.com/about-us?ts=markdown) * [Careers](https://jobs.paloaltonetworks.com/en/) * [Contact Us](https://www.paloaltonetworks.com/company/contact-sales?ts=markdown) * [Corporate Responsibility](https://www.paloaltonetworks.com/about-us/corporate-responsibility?ts=markdown) * [Customers](https://www.paloaltonetworks.com/customers?ts=markdown) * [Investor Relations](https://investors.paloaltonetworks.com/) * [Location](https://www.paloaltonetworks.com/about-us/locations?ts=markdown) * [Newsroom](https://www.paloaltonetworks.com/company/newsroom?ts=markdown) ## Popular Links * [Blog](https://www.paloaltonetworks.com/blog/?ts=markdown) * [Communities](https://www.paloaltonetworks.com/communities?ts=markdown) * [Content Library](https://www.paloaltonetworks.com/resources?ts=markdown) * [Cyberpedia](https://www.paloaltonetworks.com/cyberpedia?ts=markdown) * [Event Center](https://events.paloaltonetworks.com/) * [Manage Email Preferences](https://start.paloaltonetworks.com/preference-center) * [Products A-Z](https://www.paloaltonetworks.com/products/products-a-z?ts=markdown) * [Product Certifications](https://www.paloaltonetworks.com/legal-notices/trust-center/compliance?ts=markdown) * [Report a Vulnerability](https://www.paloaltonetworks.com/security-disclosure?ts=markdown) * [Sitemap](https://www.paloaltonetworks.com/sitemap?ts=markdown) * [Tech Docs](https://docs.paloaltonetworks.com/) * [Unit 42](https://unit42.paloaltonetworks.com/) * [Do Not Sell or Share My Personal Information](https://panwedd.exterro.net/portal/dsar.htm?target=panwedd) ![PAN logo](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/pan-logo-dark.svg) * [Privacy](https://www.paloaltonetworks.com/legal-notices/privacy?ts=markdown) * [Trust Center](https://www.paloaltonetworks.com/legal-notices/trust-center?ts=markdown) * [Terms of Use](https://www.paloaltonetworks.com/legal-notices/terms-of-use?ts=markdown) * [Documents](https://www.paloaltonetworks.com/legal?ts=markdown) Copyright © 2026 Palo Alto Networks. All Rights Reserved * [![Youtube](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/youtube-black.svg)](https://www.youtube.com/user/paloaltonetworks) * [![Podcast](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/icons/podcast.svg)](https://www.paloaltonetworks.com/podcasts/threat-vector?ts=markdown) * [![Facebook](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/facebook-black.svg)](https://www.facebook.com/PaloAltoNetworks/) * [![LinkedIn](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/linkedin-black.svg)](https://www.linkedin.com/company/palo-alto-networks) * [![Twitter](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/twitter-x-black.svg)](https://twitter.com/PaloAltoNtwks) * EN Select your language