[](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)

* 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-device-security?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)

* 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)
  * [XMDR Partners](https://www.paloaltonetworks.com/partners/managed-security-service-providers/xmdr?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.deploybravely.com)  
  [](https://www.paloaltonetworks.com/?ts=markdown)

1. [Cyberpedia](https://www.paloaltonetworks.com/cyberpedia?ts=markdown)
2. [Network Security](https://www.paloaltonetworks.com/cyberpedia/network-security?ts=markdown)
3. [Quantum-Safe IoT Security: Preparing for the Quantum Threat](https://www.paloaltonetworks.com/cyberpedia/quantum-safe-iot-security?ts=markdown)  
   Table of contents

* [Why are IoT devices especially vulnerable to quantum threats?](#why-are-iot-devices-especially-vulnerable-to-quantum-threats)
* [Why post-quantum cryptography matters for IoT systems](#why-post-quantum-cryptography-matters-for-iot-systems)
* [What makes quantum-safe IoT design so technically challenging?](#what-makes-quantum-safe-iot-design-so-technically-challenging)
* [When should IoT devices adopt post-quantum cryptography?](#when-should-iot-devices-adopt-post-quantum-cryptography)
* [What does a quantum-resilient IoT architecture actually look like?](#what-does-a-quantum-resilient-iot-architecture-actually-look-like)
* [Key standards and timelines that shape quantum-safe IoT security](#key-standards-and-timelines-that-shape-quantum-safe-iot-security)
* [Quantum-safe IoT security FAQs](#quantum-safe-iot-security-faqs)

# Quantum-Safe IoT Security: Preparing for the Quantum Threat

8 min. read  
Table of contents

* [Why are IoT devices especially vulnerable to quantum threats?](#why-are-iot-devices-especially-vulnerable-to-quantum-threats)
* [Why post-quantum cryptography matters for IoT systems](#why-post-quantum-cryptography-matters-for-iot-systems)
* [What makes quantum-safe IoT design so technically challenging?](#what-makes-quantum-safe-iot-design-so-technically-challenging)
* [When should IoT devices adopt post-quantum cryptography?](#when-should-iot-devices-adopt-post-quantum-cryptography)
* [What does a quantum-resilient IoT architecture actually look like?](#what-does-a-quantum-resilient-iot-architecture-actually-look-like)
* [Key standards and timelines that shape quantum-safe IoT security](#key-standards-and-timelines-that-shape-quantum-safe-iot-security)
* [Quantum-safe IoT security FAQs](#quantum-safe-iot-security-faqs)

1. Why are IoT devices especially vulnerable to quantum threats?

* [1. Why are IoT devices especially vulnerable to quantum threats?](#why-are-iot-devices-especially-vulnerable-to-quantum-threats)
* [2. Why post-quantum cryptography matters for IoT systems](#why-post-quantum-cryptography-matters-for-iot-systems)
* [3. What makes quantum-safe IoT design so technically challenging?](#what-makes-quantum-safe-iot-design-so-technically-challenging)
* [4. When should IoT devices adopt post-quantum cryptography?](#when-should-iot-devices-adopt-post-quantum-cryptography)
* [5. What does a quantum-resilient IoT architecture actually look like?](#what-does-a-quantum-resilient-iot-architecture-actually-look-like)
* [6. Key standards and timelines that shape quantum-safe IoT security](#key-standards-and-timelines-that-shape-quantum-safe-iot-security)
* [7. Quantum-safe IoT security FAQs](#quantum-safe-iot-security-faqs)

Quantum-safe IoT security protects connected devices from cryptographic threats posed by quantum computers.

It replaces vulnerable algorithms with post-quantum standards that can run on constrained systems. Achieving it requires crypto-agile design or preemptive deployment based on the device's lifecycle, update path, and role in the system.

## Why are IoT devices especially vulnerable to quantum threats?

[Cryptographically relevant quantum computers (CRQCs)](https://www.paloaltonetworks.com/cyberpedia/crqcs-cryptographically-relevant-quantum-computers) don't exist yet---but their future impact on [IoT security](https://www.paloaltonetworks.com/cyberpedia/what-is-iot-security) is already a concern.

The issue isn't just theoretical. It's structural. Most IoT systems weren't designed to handle the cryptographic changes that quantum computing will eventually force.

Why?

Because most IoT devices are built with hard limits on power, memory, and bandwidth.  
"IoT devices may be deployed with embedded cryptography that is expected to function securely, in the field, for many years. If there is no easy or feasible way to update this cryptography during the lifecycle of a device... the embedded cryptography may fail to retain the intended security properties in the face of unanticipated emerging threats."  
[-GSMA, Post Quantum Cryptography in IoT Ecosystem](https://www.gsma.com/solutions-and-impact/technologies/security/gsma_resources/pq-04-post-quantum-cryptography-in-iot-ecosystem/)

That's what makes them affordable and scalable. But it also means they can't support cryptographic upgrades that require more power, memory, or bandwidth. Many don't even have the resources to validate firmware signatures using stronger algorithms.

And even if they could?

Most of them have no reliable way to receive updates at all.

These devices are often installed in remote or embedded environments with limited network access. Once deployed, they tend to stay deployed---with the same cryptography---for 10 to 20 years. That's far longer than today's cryptographic standards are expected to hold up against a CRQC.

This creates a major mismatch. Long device lifecycles. Short cryptographic lifecycles.

Which means:

Any IoT device deployed today with vulnerable cryptography could be exposed in the future.

Even if quantum attacks aren't practical yet. Adversaries can simply capture encrypted data now and decrypt it later. This [harvest now, decrypt later](https://www.paloaltonetworks.com/cyberpedia/harvest-now-decrypt-later-hndl) model makes even low-priority devices, like smart meters, a potential risk over time.

The scale of the problem also matters.

There are billions of deployed IoT endpoints, many embedded in [critical infrastructure](https://www.paloaltonetworks.com/cyberpedia/what-is-critical-infrastructure). If they can't be updated in time, they can't be protected.

That's why quantum resilience for IoT isn't just about choosing new algorithms. It starts with understanding the long-term exposure built into how these devices are deployed.

## Why post-quantum cryptography matters for IoT systems

![A clean table-style graphic displays three columns labeled Algorithm, Function, and IoT relevance, with rows for ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205), each accompanied by a circular key icon, a brief functional description such as key encapsulation or digital signature, and a concise statement about resource use, tradeoffs, or suitability for stateless systems.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/quantum-safe-iot-security/How-NISTs-post-quantum-standards-apply-to-IoT-systems.png "A clean table-style graphic displays three columns labeled Algorithm, Function, and IoT relevance, with rows for ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205), each accompanied by a circular key icon, a brief functional description such as key encapsulation or digital signature, and a concise statement about resource use, tradeoffs, or suitability for stateless systems.")

Quantum computing poses a clear risk to the public-key cryptography used across IoT systems.

That includes key exchange, firmware signing, and device authentication. These functions often rely on RSA or elliptic curve cryptography. Both of which are vulnerable to future [quantum attacks](https://www.paloaltonetworks.com/cyberpedia/what-is-quantum-computings-threat-to-cybersecurity).

To address this, NIST has finalized three [post-quantum cryptography standards](https://www.paloaltonetworks.com/cyberpedia/what-is-post-quantum-cryptography-pqc). Each replaces a specific cryptographic function:

* [FIPS 203](https://csrc.nist.gov/pubs/fips/203/final) defines ML-KEM, a module-lattice-based key encapsulation mechanism.

* [FIPS 204](https://csrc.nist.gov/pubs/fips/204/final) defines ML-DSA, a module-lattice-based digital signature algorithm.

* [FIPS 205](https://csrc.nist.gov/pubs/fips/205/final) defines SLH-DSA, a stateless hash-based digital signature algorithm.

These aren't experimental options. They're the official NIST-designated successors to widely used public-key algorithms like RSA and ECDSA.

Why this matters for IoT:

Each standard was selected with implementation constraints in mind.

ML-KEM and ML-DSA were chosen in part for their efficiency in terms of code size and memory usage. SLH-DSA provides a fallback option for devices that require stateless signature schemes. These tradeoffs directly impact whether a given algorithm can run on resource-constrained devices. Especially those with limited RAM or update bandwidth.

Important:

Post-quantum cryptography is not the same as [quantum key distribution (QKD)](https://www.paloaltonetworks.com/cyberpedia/quantum-key-distribution-qkd). It's implemented in software and runs on classical networks. That makes it usable today. Even in embedded systems.

For IoT manufacturers, that changes the question. It's no longer about whether PQC is coming. It's about when and how to integrate these NIST standards into real devices.  
| ***Further reading:** [A Complete Guide to Post-Quantum Cryptography Standards](https://www.paloaltonetworks.com/cyberpedia/pqc-standards)*

## What makes quantum-safe IoT design so technically challenging?

Quantum-safe cryptography can't be retrofitted easily. Especially not in IoT systems.

The technical requirements of post-quantum algorithms often exceed what small, embedded devices can support.  
![A central circular gear graphic in layered red and orange segments surrounds a microchip icon, with thin connector lines pointing outward to labeled callouts describing hardware trust anchor limitations, protocol incompatibility, large key and signature sizes, RAM and code footprint limits, and firmware update constraints, each paired with small line icons and concise explanatory text arranged around the circle.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/quantum-safe-iot-security/Quantum-safe-IoT-implementation-challenges.png "A central circular gear graphic in layered red and orange segments surrounds a microchip icon, with thin connector lines pointing outward to labeled callouts describing hardware trust anchor limitations, protocol incompatibility, large key and signature sizes, RAM and code footprint limits, and firmware update constraints, each paired with small line icons and concise explanatory text arranged around the circle.")

**The challenge starts with key and signature sizes.**

The FIPS-approved algorithms require significantly more bandwidth and storage than RSA or ECC. That creates a problem for devices already operating on kilobytes of memory and tight data caps.

**Then there's the issue of RAM and code size.**

Some signature schemes offer reasonable tradeoffs for mid-tier devices. But others demand more computation and storage. In highly constrained systems, that can block adoption altogether, or force a hardware redesign.

**Another major challenge is firmware updates.**

Many IoT devices have immutable bootloaders or no secure update path at all. If cryptography is hardcoded into read-only firmware, it can't be replaced when PQC becomes necessary. And even when updates are possible, they may fail if the device can't handle larger binaries or signature validation overhead.

**Protocols matter too.**

Low-power protocols aren't built for high-entropy payloads or large cryptographic exchanges. Using ML-KEM in these environments often requires significant optimization. Or fallback to crypto-agile hybrid designs.

**Finally, there's hardware security.**

Secure elements and Trusted Platform Modules (TPMs) can help isolate and protect PQC operations. But they have tradeoffs of their own. TPMs are rarely used in low-cost IoT. And secure elements must support the right cryptographic primitives and be compatible with PQC rollout plans.

In other words:

The barriers are not theoretical. They're implementation-specific. Which is why quantum-safe IoT design requires architectural planning, not just cryptographic compliance.

## When should IoT devices adopt post-quantum cryptography?

There's no single answer for when post-quantum cryptography should be implemented in IoT devices.

It depends on the system, its lifecycle, and whether the device can be updated later. Or not at all.  
![A two-column comparison layout is divided by a horizontal line, with the left column titled Deploy PQC now and the right titled Design for crypto-agility, each marked by circular icons, listing contrasting rows of text describing device update capability, operational lifespan, data sensitivity, cryptographic requirements, and ending with shaded example boxes showing smart meters, grid sensors, and defense systems on the left and LPWAN sensors and logistics trackers on the right.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/quantum-safe-iot-security/Choosing-the-right-post-quantum-strategy-for-IoT-devices.png "A two-column comparison layout is divided by a horizontal line, with the left column titled Deploy PQC now and the right titled Design for crypto-agility, each marked by circular icons, listing contrasting rows of text describing device update capability, operational lifespan, data sensitivity, cryptographic requirements, and ending with shaded example boxes showing smart meters, grid sensors, and defense systems on the left and LPWAN sensors and logistics trackers on the right.")

**Some devices need PQC now. These are systems that are difficult or impossible to upgrade once deployed.**

Think smart meters. Grid sensors. Defense applications. If a device will still be running in 10 or 20 years, and it handles [sensitive data](https://www.paloaltonetworks.com/cyberpedia/sensitive-data), waiting isn't a risk worth taking. These deployments benefit from embedding ML-KEM or hybrid certificates now, alongside existing cryptography.

**But many IoT devices don't need to jump straight into PQC. They need to be ready for it.**

That's where cryptographic agility comes in.

Designing a crypto-agile system means building in the flexibility to upgrade algorithms later. That includes having a modular protocol stack, flexible certificate handling, and a firmware architecture that doesn't hardcode cryptographic primitives.

Why not just default to crypto-agility across the board?

Because it depends on what the device can support.

LPWAN devices---like those used in agriculture or logistics---often have extreme power and bandwidth limitations. These devices may need a staged approach, where agility is built in today, and PQC is added only when the protocols and infrastructure are ready.

**Industrial systems may fall somewhere in the middle.**

They often support stronger compute and storage, but also run in fixed infrastructure with long certification cycles. In these cases, hybrid designs---supporting both classical and post-quantum algorithms---may offer the best balance.

Critical point:

None of this works without an update path. Over-the-air update architectures are what make crypto-agile or hybrid approaches viable. Without them, even well-designed systems can't evolve.

That's why the question isn't just about which algorithm to use. It's about how a device will adapt to future cryptographic transitions based on what it's built to do.  
| ***Further reading:***

* [*Cryptographic Agility: The Key to Quantum Readiness*](https://www.paloaltonetworks.com/cyberpedia/what-is-cryptographic-agility)
* [*What Is Hybrid Cryptography? | The Bridge to Post-Quantum Security*](https://www.paloaltonetworks.com/cyberpedia/what-is-hybrid-cryptography)

## What does a quantum-resilient IoT architecture actually look like?

![A wide architecture diagram shows users, IoT devices, a DLT network, and other external systems connected by arrows to a large central block labeled post-quantum secure edge cloud IoT servers containing multiple rectangular modules for device discovery, device management, node optimization, cryptographic software optimization, post-quantum security, configuration management, user management, policy and compliance, authenticated key management, application management, trust engine, edge validation, DLT and smart contracts, and post-quantum cryptography, with databases depicted on the right and a lower section labeled post-quantum secure core IoT server containing additional management, analytics, security, and infrastructure modules connected to distributed core server databases.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/quantum-safe-iot-security/Post-quantum-secure-IoT-system-architecture.png)

Quantum safety isn't just about picking new algorithms.

It's about building systems that can adopt, use, and update those algorithms reliably. Especially under the real-world constraints of IoT.

**Start with public key infrastructure.**

Many organizations will use hybrid certificates that combine a classical algorithm like ECC with ML-KEM, the NIST standard for post-quantum key encapsulation. This allows existing systems to remain compatible, while preparing for quantum risk at the same time.

It also enables gradual migration as protocols evolve.

**Next comes secure identity and firmware validation.**

Devices need to prove who they are and that their code hasn't been tampered with. That's where Trusted Platform Modules or Secure Elements come in.

These hardware components can isolate private keys, validate firmware signatures, and provide attestation. Especially when paired with ML-DSA or SLH-DSA, NIST's new digital signature standards.

**But keys and signatures aren't useful if the protocol stack can't handle them.**

Quantum-resilient IoT systems must support TLS or DTLS profiles that are compatible with post-quantum key exchange and signing.  
![A vertically stacked diagram presents protocol layers from top to bottom with icons and rounded labels, starting with an application layer listing OMA DM, OMA, LwM2M, and OneM2M, followed by a messaging layer showing CoAP and MQTT-SN on one side and MQTT, HTTP, and AMQP on the other, an encryption layer with DTLS and TLS, a transport layer with UDP and TCP, a network layer labeled IPv4 and IPv6, and lower layers illustrating cellular and wireless technologies including 2G, 3G, 4G, 5G, NB-IoT, LTE-M grouped under a 3GPP bar, alongside WiFi, Bluetooth, and LPWAN.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/quantum-safe-iot-security/Protocol-layers-relevant-to-quantum-safe-IoT-communication.png "A vertically stacked diagram presents protocol layers from top to bottom with icons and rounded labels, starting with an application layer listing OMA DM, OMA, LwM2M, and OneM2M, followed by a messaging layer showing CoAP and MQTT-SN on one side and MQTT, HTTP, and AMQP on the other, an encryption layer with DTLS and TLS, a transport layer with UDP and TCP, a network layer labeled IPv4 and IPv6, and lower layers illustrating cellular and wireless technologies including 2G, 3G, 4G, 5G, NB-IoT, LTE-M grouped under a 3GPP bar, alongside WiFi, Bluetooth, and LPWAN.")

This is still evolving, but support for ML-KEM is emerging in hybrid TLS handshakes and draft DTLS proposals. For bandwidth-constrained environments, this requires testing and optimization.

**And none of this works without a way to update devices.**

A resilient architecture assumes cryptographic change is ongoing.

So firmware must be updatable. Certificate trust stores must be rollover-capable. And the update path must work reliably, whether over cellular, LPWAN, or local gateways.

In short:

A quantum-resilient IoT system isn't a device. It's a lifecycle. One that begins at provisioning and stretches through validation, update, rollover, and decommission. And every part of that lifecycle has to be able to adapt.

## Key standards and timelines that shape quantum-safe IoT security

Quantum-safe IoT isn't just a technical challenge. It's a regulatory and compliance one, too.

Global standards bodies and government agencies have already begun issuing guidance, formal requirements, and implementation targets. These shape when and how post-quantum protections must be applied. Especially for firmware signing, device authentication, and secure updates.

Here are the standards and regulations to watch:

* [**CNSA 2.0 (NSA)**](https://media.defense.gov/2025/May/30/2003728741/-1/-1/0/CSA_CNSA_2.0_ALGORITHMS.PDF)
  
  Requires post-quantum digital signatures for firmware signing in national security systems by 2025. While it applies to U.S. federal use cases, many manufacturers use it as a baseline for high-assurance devices.

* [**FIPS 203--205 (NIST)**](https://csrc.nist.gov/news/2024/postquantum-cryptography-fips-approved)
  
  Standardize ML-KEM, ML-DSA, and SLH-DSA. These are the formal replacements for today's asymmetric cryptographic standards. Implementation guidance is still evolving, but the algorithms are now locked.

* [**GSMA PQ.04**](https://www.gsma.com/solutions-and-impact/technologies/security/gsma_resources/pq-04-post-quantum-cryptography-in-iot-ecosystem/)
  
  Provides migration guidance specific to telecom and IoT. Outlines deployment models, protocol considerations, and transition strategies for constrained and long-lived devices.

* [**EU Cyber Resilience Act**](https://eur-lex.europa.eu/eli/reg/2024/2847/oj/)
  
  Establishes cryptographic lifecycle requirements for connected products sold in the EU. Includes mandatory risk assessment, vulnerability handling, and software update policies.

* **IETF standards (e.g. [SUIT](https://datatracker.ietf.org/wg/suit/about/), [hybrid TLS](https://datatracker.ietf.org/doc/draft-ietf-tls-hybrid-design/16/))**
  
  Define how post-quantum cryptography fits into real-world protocols. SUIT applies to firmware update integrity. Hybrid TLS proposals enable quantum-safe key exchange while maintaining backward compatibility.

* **Planning target: 2030+ crypto:**
  
  Even if quantum computers aren't here yet, the lifecycle of most IoT devices means their cryptography must remain secure for 10--20 years. That means adopting or preparing for post-quantum algorithms now.

Key takeaway:

These standards aren't just abstract. They shape what post-quantum resilience actually looks like in deployed systems. And they make it clear that quantum-safe IoT isn't just a design choice. It's a timeline.  
![Quantum assessment icon](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-quantum-security/icon-quantum-readiness.svg)

Get your quantum readiness assessment
The assessment includes:

* Overview of your cryptographic landscape
* Quantum-safe deployment recommendations
* Guidance for securing legacy apps \& infrastructure

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[Get my assessment](https://www.paloaltonetworks.com/resources/ebooks/quantum-security#assessment)

## Quantum-safe IoT security FAQs

### How will quantum computing affect IoT security?

Quantum computing will break widely used public-key algorithms like RSA and ECC. Many IoT devices rely on these for key exchange, authentication, and updates. Without replacement, long-lived devices may become vulnerable to future decryption or signature forgery---even if attacks aren't feasible today.

### What is post-quantum cryptography, and why is it needed for IoT?

Post-quantum cryptography (PQC) refers to cryptographic algorithms designed to resist quantum attacks. It replaces vulnerable public-key systems used in IoT for secure communication and firmware validation. PQC ensures long-term cryptographic resilience without requiring quantum hardware.

### Which post-quantum algorithms are suitable for IoT devices?

NIST's ML-KEM and ML-DSA standards offer efficient tradeoffs for constrained IoT devices. ML-KEM handles key encapsulation; ML-DSA provides digital signatures. SLH-DSA offers a stateless option but with higher computational cost. Selection depends on device resources and lifecycle constraints.

### When should IoT devices adopt PQC?

It depends on lifecycle and updatability. Devices that can't be updated, or must remain secure beyond 2030, should integrate PQC now. Others should be designed for crypto-agility---able to adopt PQC later via firmware updates. Timing depends on use case, lifecycle, and update capability.

### What standards and regulations affect post-quantum IoT security?

Key standards include FIPS 203--205 for algorithm use, CNSA 2.0 for firmware signing by 2025, GSMA PQ.04 for telecom IoT migration, and the EU Cyber Resilience Act for lifecycle compliance. IETF efforts also guide protocol integration and update mechanisms.
Related content  
[YouTube playlist: A CISO's Guide to Quantum Security
Binge a 6-video series breaking down why quantum computing is closer than you think but not as difficult.](https://www.youtube.com/playlist?list=PLqATPiC_Bcl8ZGx_EAxQHq0PKa2ii6pNE)  
[Podcast: Threat Vector | Is the Quantum Threat Closer Than You Think?
Hear how to start your transition to quantum-resistant cryptography now.](https://www.paloaltonetworks.com/resources/podcasts/threat-vector-is-the-quantum-threat-closer-than-you-think)  
[Podcast: Packet Pushers | The Why and How of Making Your Infrastructure Quantum-Safe
Get the facts on making your organization post-quantum safe.](https://packetpushers.net/podcasts/heavy-networking/hn796-the-why-and-how-of-making-your-infrastructure-quantum-safe-sponsored/)  
[Interactive experience: Is Your Organization Ready for a Quantum-Safe Future?
Dive into an immersive overview on quantum threats, PQC, and NIST's new standards.](https://www.paloaltonetworks.com/resources/ebooks/quantum-security)  
![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=Quantum-Safe%20IoT%20Security%3A%20Preparing%20for%20the%20Quantum%20Threat&body=Quantum-safe%20IoT%20security%20protects%20connected%20devices%20from%20cryptographic%20threats%20posed%20by%20quantum%20computers.%20at%20https%3A//www.paloaltonetworks.com/cyberpedia/quantum-safe-iot-security)  
Back to Top  
{#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 © 2025 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