[](https://www.paloaltonetworks.com/?ts=markdown)

* IT
  
  * [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)
  * [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)

* [Entre em contato conosco](https://www.paloaltonetworks.it/contact?ts=markdown)

* [Recursos](https://www.paloaltonetworks.it/resources?ts=markdown)

* [Obtenha suporte](https://support.paloaltonetworks.com/support)

* [Sei sotto attacco?](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)

* Prodotti  
  ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Prodotti  
  [Piattaforma di sicurezza di rete basata su AI](https://www.paloaltonetworks.it/network-security?ts=markdown)
  
  * [AI sicura sin dalla progettazione](https://www.paloaltonetworks.it/precision-ai-security/secure-ai-by-design?ts=markdown)
  
  * [Prisma AIRS](https://www.paloaltonetworks.it/prisma/prisma-ai-runtime-security?ts=markdown)
  
  * [Sicurezza accesso AI](https://www.paloaltonetworks.it/sase/ai-access-security?ts=markdown)
  
  * [Servizi di sicurezza basati su cloud](https://www.paloaltonetworks.it/network-security/security-subscriptions?ts=markdown)
  
  * [Threat Prevention avanzata](https://www.paloaltonetworks.it/network-security/advanced-threat-prevention?ts=markdown)
  
  * [URL Filtering avanzato](https://www.paloaltonetworks.it/network-security/advanced-url-filtering?ts=markdown)
  
  * [Advanced WildFire](https://www.paloaltonetworks.it/network-security/advanced-wildfire?ts=markdown)
  
  * [Sicurezza DNS avanzata](https://www.paloaltonetworks.it/network-security/advanced-dns-security?ts=markdown)
  
  * [Prevenzione della perdita di dati aziendali](https://www.paloaltonetworks.it/sase/enterprise-data-loss-prevention?ts=markdown)
  
  * [Sicurezza IoT aziendale](https://www.paloaltonetworks.it/network-security/enterprise-device-security?ts=markdown)
  
  * [Sicurezza IoT medica](https://www.paloaltonetworks.it/network-security/medical-iot-security?ts=markdown)
  
  * [Sicurezza OT industriale](https://www.paloaltonetworks.it/network-security/industrial-ot-security?ts=markdown)
  
  * [Firewall di nuova generazione](https://www.paloaltonetworks.it/network-security/next-generation-firewall?ts=markdown)
  
  * [Firewall hardware](https://www.paloaltonetworks.it/network-security/hardware-firewall-innovations?ts=markdown)
  
  * [Firewall software](https://www.paloaltonetworks.it/network-security/software-firewalls?ts=markdown)
  
  * [Strata Cloud Manager](https://www.paloaltonetworks.it/network-security/strata-cloud-manager?ts=markdown)
  
  * [SD-WAN per NGFW](https://www.paloaltonetworks.it/network-security/sd-wan-subscription?ts=markdown)
  
  * [PAN-OS](https://www.paloaltonetworks.it/network-security/pan-os?ts=markdown)
  
  * [Panorama](https://www.paloaltonetworks.it/network-security/panorama?ts=markdown)
  
  * [SECURE ACCESS SERVICE EDGE](https://www.paloaltonetworks.it/sase?ts=markdown)
  
  * [Prisma SASE](https://www.paloaltonetworks.it/sase?ts=markdown)
  
  * [Accelerazione delle applicazioni](https://www.paloaltonetworks.it/sase/app-acceleration?ts=markdown)
  
  * [Gestione autonoma dell'esperienza digitale](https://www.paloaltonetworks.it/sase/adem?ts=markdown)
  
  * [DLP aziendale](https://www.paloaltonetworks.it/sase/enterprise-data-loss-prevention?ts=markdown)
  
  * [Prisma Access](https://www.paloaltonetworks.it/sase/access?ts=markdown)
  
  * [Prisma Browser](https://www.paloaltonetworks.it/sase/prisma-browser?ts=markdown)
  
  * [Prisma SD-WAN](https://www.paloaltonetworks.it/sase/sd-wan?ts=markdown)
  
  * [Remote Browser Isolation](https://www.paloaltonetworks.it/sase/remote-browser-isolation?ts=markdown)
  
  * [Sicurezza SaaS](https://www.paloaltonetworks.it/sase/saas-security?ts=markdown)  
    [Security Operations Platform basata su AI](https://www.paloaltonetworks.it/cortex?ts=markdown)
  
  * [Sicurezza del cloud](https://www.paloaltonetworks.it/cortex/cloud?ts=markdown)
  
  * [Cortex Cloud](https://www.paloaltonetworks.it/cortex/cloud?ts=markdown)
  
  * [Sicurezza delle applicazioni](https://www.paloaltonetworks.it/cortex/cloud/application-security?ts=markdown)
  
  * [Sicurezza del livello cloud](https://www.paloaltonetworks.it/cortex/cloud/cloud-posture-security?ts=markdown)
  
  * [Sicurezza del runtime cloud](https://www.paloaltonetworks.it/cortex/cloud/runtime-security?ts=markdown)
  
  * [Prisma Cloud](https://www.paloaltonetworks.it/prisma/cloud?ts=markdown)
  
  * [SOC basati sull'IA](https://www.paloaltonetworks.it/cortex?ts=markdown)
  
  * [Cortex Advanced Email Security](https://www.paloaltonetworks.it/cortex/advanced-email-security?ts=markdown)
  
  * [Cortex Exposure Management](https://www.paloaltonetworks.it/cortex/exposure-management?ts=markdown)
  
  * [Cortex XSIAM](https://www.paloaltonetworks.it/cortex/cortex-xsiam?ts=markdown)
  
  * [Cortex XDR](https://www.paloaltonetworks.it/cortex/cortex-xdr?ts=markdown)
  
  * [Cortex XSOAR](https://www.paloaltonetworks.it/cortex/cortex-xsoar?ts=markdown)
  
  * [Cortex Xpanse](https://www.paloaltonetworks.it/cortex/cortex-xpanse?ts=markdown)
  
  * [Rilevamento e risposta gestiti di Unit 42](https://www.paloaltonetworks.it/cortex/managed-detection-and-response?ts=markdown)
  
  * [XSIAM gestito](https://www.paloaltonetworks.it/cortex/managed-xsiam?ts=markdown)

* Soluzioni  
  ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Soluzioni  
  Sicurezza AI
  
  * [Ecosistema AI sicuro](https://www.paloaltonetworks.it/prisma/prisma-ai-runtime-security?ts=markdown)
  * [Utilizzo sicuro di GenAI](https://www.paloaltonetworks.it/sase/ai-access-security?ts=markdown)  
    Sicurezza di rete
  * [Sicurezza di rete cloud](https://www.paloaltonetworks.it/network-security/software-firewalls?ts=markdown)
  * [Sicurezza del data center](https://www.paloaltonetworks.it/network-security/data-center?ts=markdown)
  * [Sicurezza DNS](https://www.paloaltonetworks.it/network-security/advanced-dns-security?ts=markdown)
  * [Rilevamento e prevenzione delle intrusioni](https://www.paloaltonetworks.it/network-security/advanced-threat-prevention?ts=markdown)
  * [Sicurezza IoT](https://www.paloaltonetworks.it/network-security/enterprise-device-security?ts=markdown)
  * [Sicurezza 5G](https://www.paloaltonetworks.it/network-security/5g-security?ts=markdown)
  * [Protezione di tutte le applicazioni, gli utenti e le posizioni](https://www.paloaltonetworks.it/sase/secure-users-data-apps-devices?ts=markdown)
  * [Trasformazione sicura della filiale](https://www.paloaltonetworks.it/sase/secure-branch-transformation?ts=markdown)
  * [Lavoro sicuro su qualsiasi dispositivo](https://www.paloaltonetworks.it/sase/secure-work-on-any-device?ts=markdown)
  * [Sostituzione VPN](https://www.paloaltonetworks.it/sase/vpn-replacement-for-secure-remote-access?ts=markdown)
  * [Sicurezza Web e phishing](https://www.paloaltonetworks.it/network-security/advanced-url-filtering?ts=markdown)  
    Sicurezza del cloud
  * [Gestione del livello di sicurezza delle applicazioni (ASPM)](https://www.paloaltonetworks.it/cortex/cloud/application-security-posture-management?ts=markdown)
  * [Sicurezza della supply chain del software](https://www.paloaltonetworks.it/cortex/cloud/software-supply-chain-security?ts=markdown)
  * [Sicurezza del codice](https://www.paloaltonetworks.it/cortex/cloud/code-security?ts=markdown)
  * [Gestione del livello di sicurezza del cloud (CSPM)](https://www.paloaltonetworks.it/cortex/cloud/cloud-security-posture-management?ts=markdown)
  * [Gestione delle autorizzazioni dell'infrastruttura cloud (CIEM)](https://www.paloaltonetworks.it/cortex/cloud/cloud-infrastructure-entitlement-management?ts=markdown)
  * [Gestione del livello di sicurezza dei dati (DSPM)](https://www.paloaltonetworks.it/cortex/cloud/data-security-posture-management?ts=markdown)
  * [AI Security Posture Management (AI-SPM)](https://www.paloaltonetworks.it/cortex/cloud/ai-security-posture-management?ts=markdown)
  * [Rilevamento e risposta nel cloud (CDR)](https://www.paloaltonetworks.it/cortex/cloud-detection-and-response?ts=markdown)
  * [Protezione dei carichi di lavoro cloud (CWP)](https://www.paloaltonetworks.it/cortex/cloud/cloud-workload-protection?ts=markdown)
  * [Sicurezza di applicazioni Web e API (WAAS)](https://www.paloaltonetworks.it/cortex/cloud/web-app-api-security?ts=markdown)  
    Operazioni di sicurezza
  * [Rilevamento e risposta nel cloud](https://www.paloaltonetworks.it/cortex/cloud-detection-and-response?ts=markdown)
  * [Automazione della sicurezza di rete](https://www.paloaltonetworks.it/cortex/network-security-automation?ts=markdown)
  * [Gestione dei casi con incidenti](https://www.paloaltonetworks.it/cortex/incident-case-management?ts=markdown)
  * [Automazione SOC](https://www.paloaltonetworks.it/cortex/security-operations-automation?ts=markdown)
  * [Gestione della threat intelligence](https://www.paloaltonetworks.it/cortex/threat-intel-management?ts=markdown)
  * [Rilevamento e risposta gestiti](https://www.paloaltonetworks.it/cortex/managed-detection-and-response?ts=markdown)
  * [Gestione della superficie di attacco](https://www.paloaltonetworks.it/cortex/cortex-xpanse/attack-surface-management?ts=markdown)
  * [Gestione della conformità](https://www.paloaltonetworks.it/cortex/cortex-xpanse/compliance-management?ts=markdown)
  * [Gestione delle operazioni su Internet](https://www.paloaltonetworks.it/cortex/cortex-xpanse/internet-operations-management?ts=markdown)  
    Sicurezza degli endpoint
  * [Protezione degli endpoint](https://www.paloaltonetworks.it/cortex/endpoint-protection?ts=markdown)
  * [Rilevamento e risposta estesi](https://www.paloaltonetworks.it/cortex/detection-and-response?ts=markdown)
  * [Protezione dal ransomware](https://www.paloaltonetworks.it/cortex/ransomware-protection?ts=markdown)
  * [Analisi forense digitale](https://www.paloaltonetworks.it/cortex/digital-forensics?ts=markdown)  
    [Settori](https://www.paloaltonetworks.it/industry?ts=markdown)
  * [Settore pubblico](https://www.paloaltonetworks.com/industry/public-sector)
  * [Servizi finanziari](https://www.paloaltonetworks.com/industry/financial-services)
  * [Produzione](https://www.paloaltonetworks.com/industry/manufacturing)
  * [Sanità](https://www.paloaltonetworks.com/industry/healthcare)
  * [Soluzioni per le piccole e medie imprese](https://www.paloaltonetworks.com/industry/small-medium-business-portfolio)

* Servizi  
  ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Servizi  
  [Servizi di intelligence sulle minacce e risposta agli incidenti](https://www.paloaltonetworks.it/unit42?ts=markdown)
  
  * [Valutazione](https://www.paloaltonetworks.it/unit42/assess?ts=markdown)
  
  * [Valutazione sicurezza AI](https://www.paloaltonetworks.it/unit42/assess/ai-security-assessment?ts=markdown)
  
  * [Valutazione della superficie di attacco](https://www.paloaltonetworks.it/unit42/assess/attack-surface-assessment?ts=markdown)
  
  * [Revisione della preparazione alle violazioni](https://www.paloaltonetworks.it/unit42/assess/breach-readiness-review?ts=markdown)
  
  * [Valutazione della preparazione al BEC](https://www.paloaltonetworks.com/bec-readiness-assessment)
  
  * [Valutazione sicurezza nel cloud](https://www.paloaltonetworks.com/unit42/assess/cloud-security-assessment)
  
  * [Valutazione di compromesso](https://www.paloaltonetworks.it/unit42/assess/compromise-assessment?ts=markdown)
  
  * [Valutazione del rischio informatico](https://www.paloaltonetworks.it/unit42/assess/cyber-risk-assessment?ts=markdown)
  
  * [Due diligence informatica su fusioni e acquisizioni](https://www.paloaltonetworks.it/unit42/assess/mergers-acquisitions-cyber-due-dilligence?ts=markdown)
  
  * [Test di penetrazione](https://www.paloaltonetworks.it/unit42/assess/penetration-testing?ts=markdown)
  
  * [Esercizi Purple Team](https://www.paloaltonetworks.it/unit42/assess/purple-teaming?ts=markdown)
  
  * [Valutazione della preparazione al ransomware](https://www.paloaltonetworks.it/unit42/assess/ransomware-readiness-assessment?ts=markdown)
  
  * [Valutazione SOC](https://www.paloaltonetworks.com/unit42/assess/cloud-security-assessment)
  
  * [Valutazione del rischio della catena di fornitura](https://www.paloaltonetworks.it/unit42/assess/supply-chain-risk-assessment?ts=markdown)
  
  * [Esercizi di simulazione](https://www.paloaltonetworks.it/unit42/assess/tabletop-exercise?ts=markdown)
  
  * [Unit 42 Retainer](https://www.paloaltonetworks.it/unit42/retainer?ts=markdown)
  
  * [Rispondere](https://www.paloaltonetworks.it/unit42/respond?ts=markdown)
  
  * [Risposta agli incidenti cloud](https://www.paloaltonetworks.it/unit42/respond/cloud-incident-response?ts=markdown)
  
  * [Analisi forense digitale](https://www.paloaltonetworks.it/unit42/respond/digital-forensics?ts=markdown)
  
  * [Risposta agli incidenti](https://www.paloaltonetworks.it/unit42/respond/incident-response?ts=markdown)
  
  * [Rilevamento e risposta gestiti](https://www.paloaltonetworks.it/unit42/respond/managed-detection-response?ts=markdown)
  
  * [Ricerca delle minacce gestita](https://www.paloaltonetworks.it/unit42/respond/managed-threat-hunting?ts=markdown)
  
  * [XSIAM gestito](https://www.paloaltonetworks.it/cortex/managed-xsiam?ts=markdown)
  
  * [Unit 42 Retainer](https://www.paloaltonetworks.it/unit42/retainer?ts=markdown)
  
  * [Trasformazione](https://www.paloaltonetworks.it/unit42/transform?ts=markdown)
  
  * [Sviluppo e revisione del piano IR](https://www.paloaltonetworks.it/unit42/transform/incident-response-plan-development-review?ts=markdown)
  
  * [Progettazione del programma di sicurezza](https://www.paloaltonetworks.it/unit42/transform/security-program-design?ts=markdown)
  
  * [CISO virtuale](https://www.paloaltonetworks.it/unit42/transform/vciso?ts=markdown)
  
  * [Zero Trust Advisory](https://www.paloaltonetworks.com/unit42/assess/cloud-security-assessment)  
    [Servizi clienti globali](https://www.paloaltonetworks.it/services?ts=markdown)
  
  * [Istruzione e formazione](https://www.paloaltonetworks.com/services/education)
  
  * [Servizi professionali](https://www.paloaltonetworks.com/services/consulting)
  
  * [Strumenti per il successo](https://www.paloaltonetworks.com/services/customer-success-tools)
  
  * [Servizi di supporto](https://www.paloaltonetworks.com/services/solution-assurance)
  
  * [Successo del cliente](https://www.paloaltonetworks.com/services/customer-success)  
    [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/logo-unit-42.svg)  
    UNIT 42 RETAINER
    Creato su misura per soddisfare le esigenze della tua organizzazione, puoi scegliere di allocare ore di risorse riservate a una qualsiasi delle nostre offerte, inclusi i servizi proattivi di gestione del rischio informatico. Scopri come assicurarti l'accesso rapido al team di risposta agli incidenti Unit 42 di livello mondiale.
    Scopri di più](https://www.paloaltonetworks.it/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  
  Partner NextWave
  
  * [Comunità dei partner NextWave](https://www.paloaltonetworks.com/partners)
  * [Fornitori di servizi cloud](https://www.paloaltonetworks.com/partners/nextwave-for-csp)
  * [Integratori di sistemi globali](https://www.paloaltonetworks.com/partners/nextwave-for-gsi)
  * [Partner tecnologici](https://www.paloaltonetworks.com/partners/technology-partners)
  * [Fornitori di servizi](https://www.paloaltonetworks.com/partners/service-providers)
  * [Fornitori di soluzioni](https://www.paloaltonetworks.com/partners/nextwave-solution-providers)
  * [Fornitori di servizi di sicurezza gestiti (MSSP)](https://www.paloaltonetworks.com/partners/managed-security-service-providers)  
    È ora di agire
  * [Accesso al portale](https://www.paloaltonetworks.com/partners/nextwave-partner-portal)
  * [Programma di servizi gestiti](https://www.paloaltonetworks.com/partners/managed-security-services-provider-program)
  * [Diventa un partner](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerregistration?type=becomepartner)
  * [Richiedi l'accesso](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerregistration?type=requestaccess)
  * [Trova un partner](https://paloaltonetworks.my.site.com/NextWavePartnerProgram/s/partnerlocator)  
    [CYBERFORCE
    CYBERFORCE rappresenta l'1% dei migliori ingegneri partner affidabili per la propria competenza in materia di sicurezza.
    Scopri di più](https://www.paloaltonetworks.com/cyberforce)

* Società  
  ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Società  
  Palo Alto Networks
  
  * [Chi siamo](https://www.paloaltonetworks.it/about-us?ts=markdown)
  * [Team dirigenziale](https://www.paloaltonetworks.com/about-us/management)
  * [Relazioni con gli investitori](https://investors.paloaltonetworks.com)
  * [Sedi](https://www.paloaltonetworks.com/about-us/locations)
  * [Etica e conformità](https://www.paloaltonetworks.com/company/ethics-and-compliance)
  * [Responsabilità d'impresa](https://www.paloaltonetworks.com/about-us/corporate-responsibility)
  * [Militari e veterani](https://jobs.paloaltonetworks.com/military)  
    [Perché Palo Alto Networks?](https://www.paloaltonetworks.it/why-paloaltonetworks?ts=markdown)
  * [Sicurezza Precision AI](https://www.paloaltonetworks.it/precision-ai-security?ts=markdown)
  * [Il nostro approccio alla piattaforma](https://www.paloaltonetworks.it/why-paloaltonetworks/platformization?ts=markdown)
  * [Accelerazione della trasformazione della cybersecurity](https://www.paloaltonetworks.com/why-paloaltonetworks/nam-cxo-portfolio)
  * [Premi e riconoscimenti](https://www.paloaltonetworks.com/about-us/awards)
  * [Testimonianze di clienti](https://www.paloaltonetworks.it/customers?ts=markdown)
  * [Certificazioni globali](https://www.paloaltonetworks.com/legal-notices/trust-center/compliance)
  * [Programma Trust 360](https://www.paloaltonetworks.com/resources/whitepapers/trust-360)  
    Opportunità di lavoro
  * [Panoramica](https://jobs.paloaltonetworks.com/)
  * [Cultura e vantaggi](https://jobs.paloaltonetworks.com/en/culture/)  
    [Nominata da Newsweek come "uno degli ambienti di lavoro più amati"
    "Aziende considerate positivamente dai loro dipendenti"
    Scopri di più](https://www.paloaltonetworks.com/company/press/2021/palo-alto-networks-secures-top-ranking-on-newsweek-s-most-loved-workplaces-list-for-2021)

* Altro  
  ![black arrow pointing left to go back to main navigation](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/arrow-right-black.svg) Altro  
  Risorse
  
  * [Blog](https://www.paloaltonetworks.com/blog/?lang=it)
  * [Blog di ricerca delle minacce di Unit 42](https://unit42.paloaltonetworks.com/)
  * [Community](https://www.paloaltonetworks.com/communities)
  * [Libreria di contenuti](https://www.paloaltonetworks.it/resources?ts=markdown)
  * [Cyberpedia](https://www.paloaltonetworks.it/cyberpedia?ts=markdown)
  * [Tech Insider](https://techinsider.paloaltonetworks.com/)
  * [Knowledge Base](https://knowledgebase.paloaltonetworks.com/)
  * [Palo Alto Networks TV](https://tv.paloaltonetworks.com/)
  * [Prospettive dei leader](https://www.paloaltonetworks.com/perspectives/)
  * [Cyber Perspectives Magazine](https://www.paloaltonetworks.com/cybersecurity-perspectives/cyber-perspectives-magazine)
  * [Sedi regionali di cloud](https://www.paloaltonetworks.it/products/regional-cloud-locations?ts=markdown)
  * [Documentazione tecnica](https://docs.paloaltonetworks.com/)
  * [Valutazione della condizione di sicurezza](https://www.paloaltonetworks.com/security-posture-assessment)
  * [Podcast Threat Vector](https://unit42.paloaltonetworks.com/unit-42-threat-vector-podcast/)  
    Social
  * [LIVE Community](https://live.paloaltonetworks.com/)
  * [Eventi](https://events.paloaltonetworks.com/)
  * [Centro briefing di livello executive](https://www.paloaltonetworks.com/about-us/executive-briefing-program)
  * [Demo](https://www.paloaltonetworks.com/demos)
  * [Contattaci](https://www.paloaltonetworks.it/contact?ts=markdown)  
    [Blog
    Aggiornamenti sulle tendenze e innovazioni più recenti forniti dalle principali aziende di sicurezza informatica a livello mondiale
    Ulteriori informazioni](https://www.paloaltonetworks.com/blog/)

* IT  
  ![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)
  * [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)

* [Entre em contato conosco](https://www.paloaltonetworks.it/contact?ts=markdown)

* [Recursos](https://www.paloaltonetworks.it/resources?ts=markdown)

* [Obtenha suporte](https://support.paloaltonetworks.com/support)

* [Sei sotto attacco?](https://start.paloaltonetworks.com/contact-unit42.html)

* [Introdução](https://www.paloaltonetworks.com/get-started)  
  Ricerca  
  Close search modal
  [](https://www.paloaltonetworks.com/?ts=markdown)

1. [Cyberpedia](https://www.paloaltonetworks.it/cyberpedia?ts=markdown)
2. [Securing Your Kubernetes Cluster: Kubernetes Best Practices and Strategies](https://www.paloaltonetworks.it/cyberpedia/kubernetes-cluster-security?ts=markdown)  
   Table of Contents

* [What Is the Importance of a Secure Kubernetes Cluster?](#importance)
* [Understanding Kubernetes Security](#security)
* [What Are Kubernetes Security Considerations and Security Best Practices?](#practices)
* [What Are Advanced Strategies for Kubernetes Security?](#advanced)
* [Kubernetes Cluster Security FAQs](#faqs)

# Securing Your Kubernetes Cluster: Kubernetes Best Practices and Strategies

Table of Contents

* [What Is the Importance of a Secure Kubernetes Cluster?](#importance)
* [Understanding Kubernetes Security](#security)
* [What Are Kubernetes Security Considerations and Security Best Practices?](#practices)
* [What Are Advanced Strategies for Kubernetes Security?](#advanced)
* [Kubernetes Cluster Security FAQs](#faqs)

1. What Is the Importance of a Secure Kubernetes Cluster?

* [1. What Is the Importance of a Secure Kubernetes Cluster?](#importance)
* [2. Understanding Kubernetes Security](#security)
* [3. What Are Kubernetes Security Considerations and Security Best Practices?](#practices)
* [4. What Are Advanced Strategies for Kubernetes Security?](#advanced)
* [5. Kubernetes Cluster Security FAQs](#faqs)

Kubernetes is an open-source [container orchestration](https://www.paloaltonetworks.com/cyberpedia/what-is-container-security?ts=markdown) platform. It provides capabilities to automate container deployment, scaling, and operation across a cluster base in a Kubernetes environment. The Kubernetes framework is used for running distributed systems resiliently, allowing for scaling and failover for applications to ensure high availability. As a vital tool in the cloud-native ecosystem, [Kubernetes](https://www.paloaltonetworks.com/cyberpedia/what-is-kubernetes?ts=markdown) simplifies container management and orchestration. Given the open and dynamic nature of Kubernetes deployments, security is paramount to protect sensitive data, maintain application integrity, and ensure operational continuity.

## What Is the Importance of a Secure Kubernetes Cluster?

A secure Kubernetes cluster is vital for several reasons. It protects a Kubernetes cluster from unauthorized access, which prevents data breaches and exposure of sensitive data. It also safeguards applications, keeping them from being compromised, such as altering application code or injecting malicious software.

Kubernetes security also helps maintain the availability of a Kubernetes cluster. Cyberattacks, such as ransomware or distributed denial of service (DDoS) attacks, can render a Kubernetes cluster unavailable to users. The resulting application downtime or failure can lead to significant business disruption, lost productivity, and financial losses, especially if the Kubernetes cluster is running critical applications.

A secure Kubernetes environment is also crucial to meet regulatory compliance requirements. Most organizations are subject to government and industry laws and regulations that have specific levels of data protection and security. If a Kubernetes cluster is not secure, it may cause regulatory compliance violations that can lead to penalties and damage to the organization's reputation.

### Five Reasons Securing a Kubernetes Cluster Is Essential

**1. Increased Costs**  
Recovering from security incidents caused by a Kubernetes cluster compromise can be costly. These usually involve extensive incident response efforts, legal fees, potential fines for regulatory noncompliance, and increased insurance premiums.

**2. Network Exposure**  
Misconfigured Kubernetes [network policies](https://www.paloaltonetworks.com/cyberpedia/what-is-cloud-network-security?ts=markdown) can expose internal services to the public internet. This makes them accessible to attackers.

**3. Compromised Customer Trust**  
A Kubernetes security incident that results in [data breaches](https://www.paloaltonetworks.com/cyberpedia/data-breach?ts=markdown) and service disruptions can erode customer trust, which is difficult and costly to rebuild. It is not uncommon for customers to move their business to competitors, resulting in long-term financial impact and reputational damage.

**4. Resource Hijacking**  
Attackers can exploit an insecure Kubernetes cluster to deploy their [containers](https://www.paloaltonetworks.com/cyberpedia/what-is-a-container?ts=markdown). This involves them using the Kubernetes cluster's computing resources for illicit purposes, such as launching additional attacks.

**5. Supply Chain Security**  
A Kubernetes ecosystem is dependent on a complex supply chain of container images, worker nodes, image registries, code, and dependencies. Insecure Kubernetes cluster configurations can lead to the exploitation of vulnerabilities, compromising the integrity of the deployment pipeline and the applications.

## Understanding Kubernetes Security

Kubernetes is widely considered the de facto orchestration system for managing [containerized](https://www.paloaltonetworks.com/cyberpedia/containerization?ts=markdown) applications in [cloud-native](https://www.paloaltonetworks.com/cyberpedia/what-is-cloud-native?ts=markdown) environments. But a Kubernetes cluster introduces unique security risks that stem from its architecture, operational complexity, and the dynamic nature of the processes used to containerize applications.

### What Security Vulnerabilities Does a Kubernete Native Environment Present?

#### Authentication and Authorization

Kubernetes supports multiple authentication mechanisms (e.g., tokens, certificates, basic auth, and anonymous auth). Managing these, along with appropriate authorization privileges through role-based access control (RBAC), can be complex and result in oversights that could expose the Kubernetes cluster.

#### Misconfigurations

Kubernetes operates on a declarative model, meaning the desired state is defined, and Kubernetes works to maintain that state. While this feature simplifies management, it can also lead to Kubernetes security risks if configurations are incorrect or insecure. In a security context, misconfigurations can expose service accounts. These are used to provide an identity for processes that run in a pod, allowing those processes to interact with the Kubernetes API. This can result in unauthorized access to sensitive information and the service mesh or even enable attackers to take control of the Kubernetes cluster.

#### Logging and Monitoring

A Kubernetes cluster generates logs at various levels with data coming from sources, such as a kubelet running on a pod. Carefully monitoring these log files and providing up to date reporting is critical, as not doing so could result in a failure to detect suspicious activities and potential breaches.

#### Pod to Pod Contamination

Because Kubernetes is based on a multitenant architecture, different applications, possibly owned by different entities, can share the same Kubernetes cluster. This can increase the risk of cross-contamination between pods in the event that one tenant's workloads are compromised if proper isolation between tenants has not been implemented.

#### Compromised Containers

Compromised containers can result when they're built from insecure container images or ones containing vulnerabilities. This puts the security of the entire cluster at risk. Vulnerable or malicious containers can serve as entry points for attackers to infiltrate Kubernetes clusters. Once inside, attackers can execute code, steal data, or move laterally within the cluster.

#### Fast-Paced Container Lifecycle

Containers in Kubernetes are often ephemeral, meaning they can be created and destroyed quickly. This can complicate traditional security measures such as intrusion detection and incident response, which may not be able to keep up with the fast-paced lifecycle of containers.

#### Kubernetes APIs

Kubernetes provides a rich set of APIs out of the box to allow users to interact with and manage Kubernetes clusters efficiently. These APIs are accessible via kubectl, Kubernetes' command-line interface, or directly through HTTP requests to the Kubernetes API server (i.e., kube apiserver). If attackers exploit any of these connection points, it can lead to unauthorized access, especially if anonymous auth is not tightly controlled or disabled entirely.

#### etcd Exposure

etcd acts as the primary storage location for all cluster data, including the state and configuration of the Kubernetes cluster, Kubernetes Secrets, and passwords. Given its central role, etcd exposure presents a significant security risk. If etcd is compromised, it could lead to a number of security risks, such as unauthorized access to sensitive data (e.g., Kubernetes Secrets, keys, and tokens) or Kubernetes cluster tampering (e.g., altering the cluster state, deploying malicious containers, or modify configurations to weaken the cluster's security posture).

#### Kubernetes Secrets Leakage

The unauthorized access to sensitive information, such as passwords, tokens, or keys, can be caused by the unintended exposure of [Kubernetes secrets](https://www.paloaltonetworks.com/cyberpedia/kubernetes-secrets?ts=markdown). This leakage can occur due to misconfigurations, inadequate access controls, or insecure handling practices. When Kubernetes secrets are leaked, they can provide attackers with access to internal systems, databases, and other critical resources.

***Related Article:** [Kubernetes Security Posture Management (KSPM)](https://www.paloaltonetworks.com/cyberpedia/kubernetes-security-posture-management-kspm?ts=markdown)*

### What Are Examples of Kubernetes Container Security Risks?

Several significant cybersecurity threats target Kubernetes clusters. A cluster admin should understand these attack vectors, which range from exploiting vulnerabilities in the Kubernetes code itself to taking advantage of misconfigurations or weak security policies. The inherent complexity of Kubernetes means that securing it is a complex task that must take into account the nuances of the multitenant architecture and multicloud environments.

#### Data Breaches

The unauthorized access of sensitive data and subsequent data breaches can occur when Kubernetes Secrets are compromised, and attackers gain access to sensitive data, such as passwords and API keys.

#### Privilege Escalation

Privilege escalation (i.e., an attacker gains higher-level privileges than they should have) can be achieved by exploiting vulnerabilities in Kubernetes or by taking advantage of poorly configured RBAC.

#### Network Attacks

Network attacks can be a significant concern. Without properly implemented Kubernetes network policies, attackers could potentially gain access to a cluster's network and disrupt network traffic or intercept sensitive data.

## What Are Kubernetes Security Considerations and Security Best Practices?

When considering Kubernetes security, take advantage of the collective wisdom earned from experience. The following are commonly cited best practices that address the key security considerations in a Kubernetes environment.

#### Encrypt Sensitive Data

Use the Kubernetes mechanisms to encrypt data at rest. In Kubernetes, encryption keys are defined in a configuration file that is used to encrypt data stored in etcd, the distributed key-value store that Kubernetes uses to persist its state and configurations. This feature enhances the security of a Kubernetes cluster by ensuring that sensitive information (e.g., secrets, passwords, tokens, and SSH keys) in the etcd database is protected. Utilize Kubernetes' built-in support for secrets and consider integrating external secrets management solutions that offer enhanced security features. Regularly rotate encryption keys and manage access to them securely to prevent unauthorized access.

#### Enforce the Principle of Least Privilege

Enforcing [the principle of least privilege](https://www.paloaltonetworks.com/cyberpedia/what-is-least-privilege-access?ts=markdown) involves granting users, applications, and processes only as much access as needed to complete their intended functions. RBAC is a key tool in Kubernetes that allows administrators to define roles with specific permissions and bind those roles to users, groups, or service accounts. Additionally, using namespaces for resource isolation, applying pod security policies, and securely managing Secrets supports the enforcement of the principle of least privilege.

#### Implement Strong Access Controls

Maintain strong authentication and authorization controls to protect the Kubernetes environment. Use RBAC to restrict access to resources within the cluster, tightly coupling roles to users, groups, or service accounts based on their responsibilities. Also, employ namespace-based segmentation to limit access within isolated environments. Additionally, implement strong authentication mechanisms, such as mutual TLS (mTLS), for service-to-service communications. Finally, audit access policies and logs to detect and remediate unauthorized access attempts as well as keeping [access controls](https://www.paloaltonetworks.com/cyberpedia/access-control?ts=markdown) up to date with the principle of least privilege.

#### Install Updates and Patches Regularly

Regularly install updates and patches, including fixes for vulnerabilities, performance improvements, and additional security features that address emerging threats. Monitor sources such as the Kubernetes project's release notes and security advisories to stay informed about new vulnerabilities and available patches. Also, implement a consistent patch management process to ensure that the Kubernetes cluster remains protected against known vulnerabilities. Automation tools can help streamline the update process, minimizing downtime and reducing the risk of human error. Additionally, testing updates in a staging environment before deploying them in production can prevent potential disruptions to the Kubernetes environment.

#### Monitor and Audit the Attack Surface

Leverage Kubernetes native auditing features to conduct continuous logging, monitoring, and auditing of all activities and API calls. These generate detailed audit logs that capture chronological events affecting the cluster to detect suspicious activities or anomalies, trigger a timely response to potential security risks, and provide insights into security-relevant actions. The Audit Policy file should also be configured to define the rules for logging activities related to the Kubernetes API. Additionally, use tools designed for Kubernetes monitoring to continuously scan for misconfigurations, vulnerabilities, and deviations from policies and authorized usage in the Kubernetes environment. Also, integrate threat detection solutions that are specifically designed for a Kubernetes environment to identify potential threats proactively.

## What Are Advanced Strategies for Kubernetes Security?

#### Kubernetes-Native Security Tools

Using Kubernetes native security tools leverages the inherent capabilities of Kubernetes to enhance the security posture of containerized environments. These tools, which are integrated seamlessly into the Kubernetes environment, include network policies to enforce traffic control between pods, role-based access control (RBAC), and Pod Security Policies (PSPs). Also, use [Secrets management](https://www.paloaltonetworks.com/cyberpedia/secrets-management?ts=markdown) to securely store and provide access to sensitive information (e.g., passwords and tokens).

#### Image Policies

Implement image signing and verification to ensure integrity and trustworthiness and adopt a policy of using only trusted base images from reputable sources. In addition, select a base image with the minimal software packages necessary for the application to run. Also, prevent unwanted kernel modules from being loaded into containers using rules in "/etc/modprobe .d/kubernete blacklist .conf" of the node or by uninstalling the unwanted modules from the node.

#### Namespaces

Use namespaces in Kubernetes to limit the scope of resources by creating isolated environments within a single cluster. Namespaces facilitate fine-grained access control by applying RBAC policies specific to each namespace, ensuring users and applications have access only to the resources they require. This isolation allows for better management of resources across different teams or projects, reducing the risk of accidental or malicious interference between workloads.

#### Network Policies

By default, Kubernetes pods are non-isolated and accept traffic from any source. Employ network policies to apply policies to specific pods, restrict the flow of traffic between pod to pod and pod to external services, and control how pods communicate with each other and with other network endpoints. In addition, use network policies to implement a default deny firewall policy for a namespace, ensuring that only explicitly allowed connections are established. Kubernetes network policies should be reviewed regularly and updated to address changes in security risks.

#### Non-Root Isolation

By default, containers run with root privileges. These privileges can be exploited to gain unauthorized access to the host machine or other containers within the cluster. Running containers as non-root users eliminates this vulnerability by preventing an attacker from executing commands as the root user.

#### Read Only Filesystems

Enforce read only filesystems in Kubernetes to prevent unauthorized modifications to running containers. By setting containers to run with a read only root filesystem, the attack surface is reduced by disallowing write operations. This reduces the risk of malicious file modifications or the introduction of unwanted software that can compromise container integrity.

#### Runtime Security

Use [Kubernetes runtime security](https://www.paloaltonetworks.com/cyberpedia/runtime-security?ts=markdown) to protect applications during their execution, ensuring that malicious activities or vulnerabilities do not compromise containerized workloads. Kubernetes runtime security covers monitoring and securing running containers and the Kubernetes orchestration environment against threats. Key aspects of Kubernetes runtime security include implementing network policies to restrict traffic between pods, using security contexts to enforce privilege and access controls at the pod level, and deploying runtime security tools that can detect and prevent unauthorized activities based on behavioral analysis of containers.

#### Scanning

Continuously scan containers, container images, [image registries](https://www.paloaltonetworks.com/cyberpedia/what-is-container-security?ts=markdown), and dependencies for vulnerabilities using automated tools. Regularly rescan images in registries and containers running in the cluster to catch newly discovered vulnerabilities.

#### Secure API Server

Enable transport layer security (TLS) to ensure that all communications with the Kubernetes API server (i.e., kube apiserver) are encrypted, protecting against eavesdropping and tampering. Additionally, build in authentication mechanisms, such as client certificates, tokens, and basic authentication, to verify the identities of users and services interacting with the API server. Also, limit API server exposure to the internet and use network policies. Kubernetes supports multiple options for authorization mode to control access to the API server, ensuring secure operations within the cluster by ensuring that only authorized entities can interact with the cluster's control plane.

#### Service Mesh

Implement a service mesh to enhance security in microservices architectures by introducing a dedicated infrastructure layer that manages secure service-to-service communication. This will enable mutual TLS (mTLS) by default, ensuring encrypted traffic between services and authenticating service identities. A service mesh also provides fine-grained access control policies, allowing administrators to define which services can communicate with each other. In addition, a service mesh facilitates consistent and automated security policies across all services, including secure service discovery and integration with existing security protocols and tools. This delivers a comprehensive security posture without requiring changes to the application code.

## Kubernetes Cluster Security FAQs

### How do I secure my Kubernetes cluster?

Securing a Kubernetes cluster involves several key steps. Start by enabling RBAC to manage who has what kind of access to the system. Use third-party authentication for the API server to ensure only authorized entities can interact with the Kubernetes cluster. Protect the etcd with TLS, a firewall, and encryption. Build network security definitions into workloads. Configure authentication and authorization on the Kubernetes cluster and cluster nodes. Finally, use Kubernetes Secrets for all sensitive data to prevent unauthorized access.

### What are the 4 C's of Kubernetes security?

The 4 C's of Kubernetes security represent a holistic approach to securing containerized environments and include cloud, clusters, containers, and code.

* Cloud security focuses on protecting the infrastructure that hosts a Kubernetes cluster, including the management of access controls and network configurations to safeguard against external threats.
* Cluster security involves securing the Kubernetes cluster by implementing measures such as RBAC, network policies, and secure access to the API server.
* Container security emphasizes scanning container images for vulnerabilities, managing container runtime configurations, and ensuring container isolation.
* Code security entails securing the application code running within containers, addressing issues such as dependency vulnerabilities, and embedding security practices into the development lifecycle.

### What are the two areas of concern for securing Kubernetes?

Effectively securing Kubernetes revolves around two main areas of concern---cluster configuration and workload security. Cluster configuration encompasses the setup and maintenance of the Kubernetes cluster itself, focusing on aspects such as access controls, network policies, and the security of the underlying infrastructure. Workload security focuses on the applications running on Kubernetes, including container security, managing Secrets, scanning for vulnerabilities in container images, and implementing security contexts and policies for running pods.

### Why is Kubernetes more secure?

Kubernetes is considered more secure due to its comprehensive, native security features, including Kubernetes RBAC, Pod Security Policies (PSPs), and support for the principle of least privilege. This open-source solution also benefits from a highly active community that continuously works to identify and patch vulnerabilities.
Related content  
[The Definitive Guide to Container Security
Get the ultimate guide to securing your containers, your essential resource for understanding, implementing and mastering security in a containerized environment.](https://www.paloaltonetworks.com/resources/ebooks/container-security-definitive-guide?ts=markdown)  
[QlikTech Secures Container Development with AWS and Prisma Cloud
Explore how Qlik, a business intelligence company, leverages AWS and Prisma Cloud to secure container-based workloads and protect customer data in their Kubernetes deployments.](https://www.paloaltonetworks.com/resources/videos-customers/qliktech-secures-container-development-with-aws-and-prisma-cloud?ts=markdown)  
[Kubernetes Privilege Escalation: Excessive Permissions in Popular Platforms
To understand the impact of excessive permissions, we analyzed popular Kubernetes platforms --- distributions, managed services, and common add-ons --- to identify infrastructure compo...](https://www.paloaltonetworks.com/resources/whitepapers/kubernetes-privilege-escalation-excessive-permissions-in-popular-platforms?ts=markdown)  
[Guide to Operationalizing Your IaC Security Program
Infrastructure as code (IaC) plays a key role in containerized applications. Get a step-by-step plan to help you choose your IaC security path based on your needs, operationalize a...](https://www.paloaltonetworks.com/resources/whitepapers/guide-to-operationalizing-your-iac-security-program?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=Securing%20Your%20Kubernetes%20Cluster%3A%20Kubernetes%20Best%20Practices%20and%20Strategies&body=%20at%20https%3A//www.paloaltonetworks.it/cyberpedia/kubernetes-cluster-security)  
Torna all'inizio  
{#footer}

## Prodotti e servizi

* [Piattaforma di sicurezza di rete basata su AI](https://www.paloaltonetworks.it/network-security?ts=markdown)

* [AI sicura sin dalla progettazione](https://www.paloaltonetworks.it/precision-ai-security/secure-ai-by-design?ts=markdown)

* [Prisma AIRS](https://www.paloaltonetworks.it/prisma/prisma-ai-runtime-security?ts=markdown)

* [Sicurezza accesso AI](https://www.paloaltonetworks.it/sase/ai-access-security?ts=markdown)

* [Servizi di sicurezza basati su cloud](https://www.paloaltonetworks.it/network-security/security-subscriptions?ts=markdown)

* [Prevenzione avanzata delle minacce](https://www.paloaltonetworks.it/network-security/advanced-threat-prevention?ts=markdown)

* [URL Filtering avanzato](https://www.paloaltonetworks.it/network-security/advanced-url-filtering?ts=markdown)

* [WildFire avanzato](https://www.paloaltonetworks.it/network-security/advanced-wildfire?ts=markdown)

* [Sicurezza DNS avanzata](https://www.paloaltonetworks.it/network-security/advanced-dns-security?ts=markdown)

* [Prevenzione della perdita di dati aziendali](https://www.paloaltonetworks.it/sase/enterprise-data-loss-prevention?ts=markdown)

* [Sicurezza IoT aziendale](https://www.paloaltonetworks.it/network-security/enterprise-iot-security?ts=markdown)

* [Sicurezza IoT nel settore medico](https://www.paloaltonetworks.it/network-security/medical-iot-security?ts=markdown)

* [Sicurezza OT industriale](https://www.paloaltonetworks.it/network-security/industrial-ot-security?ts=markdown)

* [Sicurezza SaaS](https://www.paloaltonetworks.it/sase/saas-security?ts=markdown)

* [Firewall di nuova generazione](https://www.paloaltonetworks.it/network-security/next-generation-firewall?ts=markdown)

* [Firewall hardware](https://www.paloaltonetworks.it/network-security/hardware-firewall-innovations?ts=markdown)

* [Firewall software](https://www.paloaltonetworks.it/network-security/software-firewalls?ts=markdown)

* [Strata Cloud Manager](https://www.paloaltonetworks.it/network-security/strata-cloud-manager?ts=markdown)

* [SD-WAN per NGFW](https://www.paloaltonetworks.it/network-security/sd-wan-subscription?ts=markdown)

* [PAN-OS](https://www.paloaltonetworks.it/network-security/pan-os?ts=markdown)

* [Panorama](https://www.paloaltonetworks.it/network-security/panorama?ts=markdown)

* [Secure Access Service Edge](https://www.paloaltonetworks.it/sase?ts=markdown)

* [Prisma SASE](https://www.paloaltonetworks.it/sase?ts=markdown)

* [Accelerazione delle applicazioni](https://www.paloaltonetworks.it/sase/app-acceleration?ts=markdown)

* [ADEM (Autonomous Digital Experience Management)](https://www.paloaltonetworks.it/sase/adem?ts=markdown)

* [DLP aziendale](https://www.paloaltonetworks.it/sase/enterprise-data-loss-prevention?ts=markdown)

* [Prisma Access](https://www.paloaltonetworks.it/sase/access?ts=markdown)

* [Prisma Browser](https://www.paloaltonetworks.it/sase/prisma-browser?ts=markdown)

* [Prisma SD-WAN](https://www.paloaltonetworks.it/sase/sd-wan?ts=markdown)

* [Remote Browser Isolation](https://www.paloaltonetworks.it/sase/remote-browser-isolation?ts=markdown)

* [Sicurezza SaaS](https://www.paloaltonetworks.it/sase/saas-security?ts=markdown)

* [Piattaforma operazioni di sicurezza basate su AI](https://www.paloaltonetworks.it/cortex?ts=markdown)

* [Sicurezza cloud](https://www.paloaltonetworks.it/cortex/cloud?ts=markdown)

* [Cortex Cloud](https://www.paloaltonetworks.it/cortex/cloud?ts=markdown)

* [Sicurezza delle applicazioni](https://www.paloaltonetworks.it/cortex/cloud/application-security?ts=markdown)

* [Sicurezza del livello cloud](https://www.paloaltonetworks.it/cortex/cloud/cloud-posture-security?ts=markdown)

* [Sicurezza runtime del cloud](https://www.paloaltonetworks.it/cortex/cloud/runtime-security?ts=markdown)

* [Prisma Cloud](https://www.paloaltonetworks.it/prisma/cloud?ts=markdown)

* [SOC basato su AI](https://www.paloaltonetworks.it/cortex?ts=markdown)

* [Cortex XSIAM](https://www.paloaltonetworks.it/cortex/cortex-xsiam?ts=markdown)

* [Cortex XDR](https://www.paloaltonetworks.it/cortex/cortex-xdr?ts=markdown)

* [Cortex XSOAR](https://www.paloaltonetworks.it/cortex/cortex-xsoar?ts=markdown)

* [Cortex Xpanse](https://www.paloaltonetworks.it/cortex/cortex-xpanse?ts=markdown)

* [Rilevamento e risposta gestiti da Unit 42](https://www.paloaltonetworks.it/cortex/managed-detection-and-response?ts=markdown)

* [XSIAM gestito](https://www.paloaltonetworks.it/cortex/managed-xsiam?ts=markdown)

* [Intelligence sulle minacce e servizi di risposta agli incidenti](https://www.paloaltonetworks.it/unit42?ts=markdown)

* [Valutazioni proattive](https://www.paloaltonetworks.it/unit42/assess?ts=markdown)

* [Risposta agli incidenti](https://www.paloaltonetworks.it/unit42/respond?ts=markdown)

* [Trasforma la tua strategia di sicurezza](https://www.paloaltonetworks.it/unit42/transform?ts=markdown)

* [Scopri l'intelligence sulle minacce](https://www.paloaltonetworks.it/unit42/threat-intelligence-partners?ts=markdown)

## Azienda

* [Informazioni](https://www.paloaltonetworks.com/about-us)
* [Offerte di lavoro](https://jobs.paloaltonetworks.com/en/)
* [Contattaci](https://www.paloaltonetworks.it/contact?ts=markdown)
* [Responsabilità aziendale](https://www.paloaltonetworks.com/about-us/corporate-responsibility)
* [Clienti](https://www.paloaltonetworks.it/customers?ts=markdown)
* [Relazioni con gli investitori](https://investors.paloaltonetworks.com/)
* [Sede](https://www.paloaltonetworks.com/about-us/locations)
* [Rassegna stampa](https://www.paloaltonetworks.it/company/newsroom?ts=markdown)

## Link più richiesti

* [Blog](https://www.paloaltonetworks.com/blog/?lang=it)
* [Communities](https://www.paloaltonetworks.com/communities)
* [Libreria di contenuti](https://www.paloaltonetworks.it/resources?ts=markdown)
* [Cyberpedia](https://www.paloaltonetworks.it/cyberpedia?ts=markdown)
* [Centro eventi](https://events.paloaltonetworks.com/)
* [Gestisci le preferenze e-mail](https://start.paloaltonetworks.com/preference-center)
* [Prodotti A-Z](https://www.paloaltonetworks.com/products/products-a-z)
* [Certificazioni di prodotto](https://www.paloaltonetworks.com/legal-notices/trust-center/compliance)
* [Segnala una vulnerabilità](https://www.paloaltonetworks.com/security-disclosure)
* [Mappa del sito](https://www.paloaltonetworks.it/sitemap?ts=markdown)
* [Documenti tecnici](https://docs.paloaltonetworks.com/)
* [Unit 42](https://unit42.paloaltonetworks.com/)
* [Non vendere o condividere le mie informazioni personali](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)
* [Trust Center](https://www.paloaltonetworks.com/legal-notices/trust-center)
* [Condizioni d'uso](https://www.paloaltonetworks.com/legal-notices/terms-of-use)
* [Documenti](https://www.paloaltonetworks.com/legal)

Copyright © 2026 Palo Alto Networks. Tutti i diritti riservati

* [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/youtube-black.svg)](https://www.youtube.com/user/paloaltonetworks)
* [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/twitter-x-black.svg)](https://twitter.com/PaloAltoNtwks)
* [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/facebook-black.svg)](https://www.facebook.com/PaloAltoNetworks/)
* [![](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/linkedin-black.svg)](https://www.linkedin.com/company/palo-alto-networks)
* [![](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/icons/podcast.svg)](https://unit42.paloaltonetworks.com/unit-42-threat-vector-podcast/)
* IT  
  Select your language