[](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. [AI Cybersecurity](https://www.paloaltonetworks.com/cyberpedia/artificial-intelligence-cybersecurity?ts=markdown) 3. [What Is MLOps? Machine Learning Operations | Starter Guide](https://www.paloaltonetworks.com/cyberpedia/what-is-mlops?ts=markdown) Table of contents * [Why did MLOps emerge in the first place?](#cyberpedia-van-dalen-anchor) * [What challenges do organizations run into when adopting MLOps?](#cyberpedia-van-dalen-anchor) * [Top 7 best practices behind mature MLOps](#margin-top:20px;) * [How MLOps relates to adjacent disciplines (DevOps, DataOps, ModelOps, LLMOps)](#cyberpedia-list) # What Is MLOps? Machine Learning Operations | Starter Guide 5 min. read Table of contents * [Why did MLOps emerge in the first place?](#cyberpedia-van-dalen-anchor) * [What challenges do organizations run into when adopting MLOps?](#cyberpedia-van-dalen-anchor) * [Top 7 best practices behind mature MLOps](#margin-top:20px;) * [How MLOps relates to adjacent disciplines (DevOps, DataOps, ModelOps, LLMOps)](#cyberpedia-list) 1. Why did MLOps emerge in the first place? * [1. Why did MLOps emerge in the first place?](#cyberpedia-van-dalen-anchor) * [2. What challenges do organizations run into when adopting MLOps?](#cyberpedia-van-dalen-anchor) * [3. Top 7 best practices behind mature MLOps](#margin-top:20px;) * [4. How MLOps relates to adjacent disciplines (DevOps, DataOps, ModelOps, LLMOps)](#cyberpedia-list) MLOps is a discipline that unifies machine learning, software engineering, and data engineering to build, deploy, monitor, and maintain ML systems in production. It manages the lifecycle of data, models, and code as connected workflows. MLOps isn't a toolset. It sits alongside DevOps, DataOps, ModelOps, and LLMOps as a distinct operational practice. ## Why did MLOps emerge in the first place? Organizations have rapidly increased their use of [AI](https://www.paloaltonetworks.com/cyberpedia/artificial-intelligence-ai) and [machine learning (ML)](https://www.paloaltonetworks.com/cyberpedia/machine-learning-ml) as part of everyday software systems. Adoption grew fast. However, production success didn't. Many teams struggled to run ML systems reliably outside controlled experimentation. Which is why this shift created new expectations for automation, prediction, and decision support. Basically, the industry could build ML models. But it couldn't operate them well. More specifically: ML systems depend on data. And data changes over time. As a result, the model can drift even if the code stays the same. Input patterns shift. Pipelines break. Performance degrades quietly. Traditional [DevOps](https://www.paloaltonetworks.com/cyberpedia/what-is-devops) practices assume stable inputs and deterministic behavior. But ML doesn't follow those assumptions. Experimental workflows added more challenges. Data scientists and ML engineers created lots of datasets, features, and model versions. They tuned parameters and retrained often. These steps produced artifacts that needed tracking, reproducibility, and review. And most software workflows weren't designed for this level of variation. Integration exposed further gaps. ML platform teams needed aligned environments, clear handoffs, consistent telemetry, and coordinated deployment. Without these, systems failed for operational reasons rather than model quality. That is what led to the emergence of MLOps. A discipline built to manage data, models, code, environments, and feedback loops as one operational system. ## What are the core components of a modern MLOps architecture? ![A wide flow diagram titled MLOps architecture shows data scientists on the left feeding data sources labeled databases, object storage, and structured data into an ML development platform containing object storage, a code repository, and Jupyter notebooks. From this platform, arrows connect to an artifacts section with feature store, model registry, container registry, model storage, and an orchestrator. Below, an ML training pipeline runs horizontally with an orchestrator, data preparation, functions, monitoring, object storage, and a model monitor, with arrows indicating data flow, baselines, and data or model drift. To the right, a CI/CD column contains a code compiler and a code deployment service connected downward. At the bottom, two boxed environments are shown side by side: a production environment in yellow with endpoint, compute service, object storage, and API gateway leading to users, and a staging environment in red with the same components leading to testers.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/MLOps-architecture.png) An MLOps architecture works because each component supports a different part of the lifecycle. The system moves code, data, and models through training, validation, deployment, and monitoring. And each one solves a specific operational problem. Understanding the architecture starts with understanding the purpose each component serves. Let's dig into the core components of MLOps architecture: * **CI/CD provides the entry point.** It creates a consistent way to package code, [pipeline](https://www.paloaltonetworks.com/cyberpedia/what-is-the-ci-cd-pipeline-and-ci-cd-security) steps, and configuration. It also gives teams a safe way to promote changes through build, test, and deployment. Without this, downstream workflows break before they begin. * **Workflow orchestration manages the pipeline itself.** It defines what runs, when it runs, and what each step depends on. It also keeps the process reproducible as data, features, or models evolve. This solves the problem of coordinating multi-step ML workflows. * **Feature stores support both experimentation and serving.** They centralize feature definitions and make them available across teams. And they reduce training--serving skew by ensuring feature logic stays consistent in every environment. Which prevents duplicated feature code and inconsistent results. * **Metadata stores record the details of each pipeline run.** They track datasets, parameters, artifacts, and outputs. And make lineage and reproducibility possible. That context makes it clear how the model was constructed and why its behavior looks the way it does. * **Model registries manage trained models as versioned assets.** They keep track of which model is approved, support promotion from staging to production, and they give teams a structured way to review changes. This keeps model releases controlled and reviewable. * **Model serving layers provide the runtime for predictions.** And expose models through real-time or batch interfaces. Also, they standardize how predictions are delivered across environments. That consistency helps keep latency low and behavior reliable. Even under production traffic. * **Monitoring watches data, model behavior, and system health.** Monitoring tracks data quality, model performance, and infrastructure status. It detects signs of drift and flags broken pipelines. These signals alert teams when behavior changes or performance drops. Before silent failures impact downstream systems. * **Environment and infrastructure management keep training and serving consistent across machines.** They make sure training and serving environments stay aligned as workloads move between systems. This consistency enables reproducible results. It also allows the system to scale reliably as demands grow. Without introducing drift between development and production. * **Feedback loops close the lifecycle.** They connect monitoring back to development. They trigger retraining. And they help teams keep models aligned with changing data. Together, these components create the architecture that makes ML operational. ## How does the MLOps lifecycle actually work end-to-end? ![A structured flow diagram titled MLOps lifecycle is divided into design, model development, and operations sections connected by directional arrows. On the left, the design area contains stacked boxes labeled requirements, ML use cases, and data availability, feeding into a model development block listing model analysis, experimentation, and data analysis. To the right, a large operations container includes a model registry box with versioning, evaluation metrics, and hyperparameters; a continuous integration box for package, build, and test; and a continuous delivery box listing real-time APIs, inference, and optimization, all flowing downward into a monitoring box showing data quality, performance, drift, and system health. A dotted workflow automation area on the right encloses data extraction, validation, preparation, model training, and model evaluation and validation, connected to a metadata store above and a feature store below that lists consistency, feature definitions, and training-serving alignment. Arrows indicate feedback loops from monitoring back to model development and between operations components, emphasizing iterative lifecycle flow.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/MLOps-lifecycle.png) An ML system moves through a lifecycle that connects its development, deployment, and long-term operation. Each phase prepares the next. Together, these phases function as one loop rather than a one-way pipeline. Let's break down each phase of the MLOps lifecycle: 1. **Project initiation** The lifecycle begins by defining the problem ML is meant to solve. This includes the model's purpose, the expected inputs, and the operational constraints. It also includes early decisions about how performance will be evaluated and monitored. These choices shape every downstream step. ***Note:*** *This phase may involve cross-functional input from business, product, and data teams. Especially when operational constraints are still fluid.* 2. **Data preparation** Work then shifts to the data that will support the model. Data must be located, profiled, cleaned, and labeled. Distribution changes, quality gaps, and validation needs are identified. This prepares the ground for reproducible features and consistent training. 3. **Feature engineering** The raw data is transformed into features the model can learn from. Rules for cleaning, aggregating, and deriving attributes are created and refined. These rules must work both during experimentation and in production. The objective is to align training and serving. ***Note:*** *In many organizations, the same team doesn't own both feature creation and feature serving, making alignment across environments more difficult in practice.* 4. **Experimentation and training** Next comes experimentation. Different algorithms, parameters, and configurations are tested. Each training run produces artifacts and results that must be tracked. The goal is to identify the version of the model that performs best under the defined conditions. 5. **Model validation** The selected model is then validated. It's tested on unseen data. It's checked for regressions. And it's reviewed against the success criteria defined in the initiation phase. This ensures the model is ready for controlled deployment. ***Note:*** *Validation criteria are often negotiated or reinterpreted late in the process, especially if early baselines were unrealistic or poorly defined.* 6. **Deployment** The model is packaged with its serving logic. It moves through staging. Automated checks run. Environments must be consistent so the model behaves the same way it did during validation. Deployment is where the system becomes operational. 7. **Monitoring** Once live, the system must be monitored. Data quality, model behavior, and serving performance are tracked. Drift is detected. Pipeline issues surface. Monitoring provides the signals that show when intervention is needed. 8. **Feedback and retraining** These signals initiate feedback loops. New data is incorporated. Features are updated. Models are retrained and evaluated. Improved versions move back toward deployment. It's how the lifecycle maintains alignment with changing conditions. ***Note:*** *Feedback loops don't always restart at data prep. Many begin midstream with new features, updated parameters, or model refinement only.* The lifecycle works because each phase strengthens the next. And the entire loop keeps ML systems reliable as their environment changes. ## What roles are involved in MLOps? ![A circular diagram titled MLOps roles and responsibilities places a central abstract ML icon inside a large light gray circle, with six numbered connection points radiating outward to role descriptions arranged around the perimeter. On the right, a data engineer section labeled with a wrench icon describes data ingestion and preparation and managing data flow and stability for training and serving, followed below by a data scientist section with a database icon describing developing candidate models and defining model direction with experimentation. Further down on the right, an ML engineer section with a connected-nodes icon describes connecting models to serving logic and real-world conditions with deployment preparation. On the left, an MLOps engineer section with a gears icon describes orchestration, CI/CD, monitoring, and retraining with continuous operations, above which a platform engineer section with a layered platform icon describes managing infrastructure, tooling, metadata, and storage with platform support. At the top left, a governance and quality section with a balance scale icon describes review and compliance, ensuring lineage, documentation, and model behavior meet standards, with thin lines linking each role back to the central circle.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/mlops-roles-and-responsibilities.png "A circular diagram titled MLOps roles and responsibilities places a central abstract ML icon inside a large light gray circle, with six numbered connection points radiating outward to role descriptions arranged around the perimeter. On the right, a data engineer section labeled with a wrench icon describes data ingestion and preparation and managing data flow and stability for training and serving, followed below by a data scientist section with a database icon describing developing candidate models and defining model direction with experimentation. Further down on the right, an ML engineer section with a connected-nodes icon describes connecting models to serving logic and real-world conditions with deployment preparation. On the left, an MLOps engineer section with a gears icon describes orchestration, CI/CD, monitoring, and retraining with continuous operations, above which a platform engineer section with a layered platform icon describes managing infrastructure, tooling, metadata, and storage with platform support. At the top left, a governance and quality section with a balance scale icon describes review and compliance, ensuring lineage, documentation, and model behavior meet standards, with thin lines linking each role back to the central circle.") MLOps brings together several disciplines. Each one supports a different part of the lifecycle. The value comes from how these responsibilities work together. **Data engineers shape the data layer.** Their work defines how information enters the system. It also determines how stable training and serving will be long term. When this foundation is solid, the entire workflow benefits. **Data scientists explore the problem space and develop candidate models.** They experiment to reveal what the system can learn. Form ideas. And set the initial direction of the model. **ML engineers turn those ideas into production-ready components.** This process is all about connecting models with serving logic. It also prepares the system to operate under real conditions. In practice, this is where experimentation transitions into applied use. **MLOps engineers maintain the workflows that hold the lifecycle together.** The role is all about operating orchestration, CI/CD, monitoring, and retraining. It ensures the system continues to function as one loop instead of disconnected steps. **Platform engineers support the shared environment beneath the workflow.** They maintain tooling, infrastructure, metadata systems, and storage. Which provides the consistency the lifecycle needs to operate smoothly. **Governance and quality roles provide oversight.** Oversight related work is focused on reviewing lineage, documentation, and model behavior to ensure the system meets organizational expectations before and after deployment. Now that we've broken down who's responsible for what in MLOps, let's get into the challenges they face in the adoption process. ## What challenges do organizations run into when adopting MLOps? ![A two-column layout titled MLOps adoption challenges places the title on the left over a light gray background, while six orange square tiles with white line icons and labels are arranged in two vertical columns to the right. The left column lists socio-technical misalignment with a balance scale icon, pipeline fragility with connected gears inside a pipeline icon, and continual learning pressure with a person holding a megaphone icon. The right column lists platform complexity with stacked layers and circuit lines, migration friction with a dotted arrow and warning symbol inside a screen outline, and automation boundaries with interlocking gears inside a rounded square.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/MLOps-adoption-challenges.png "A two-column layout titled MLOps adoption challenges places the title on the left over a light gray background, while six orange square tiles with white line icons and labels are arranged in two vertical columns to the right. The left column lists socio-technical misalignment with a balance scale icon, pipeline fragility with connected gears inside a pipeline icon, and continual learning pressure with a person holding a megaphone icon. The right column lists platform complexity with stacked layers and circuit lines, migration friction with a dotted arrow and warning symbol inside a screen outline, and automation boundaries with interlocking gears inside a rounded square.") Adopting MLOps tends to surface challenges that don't appear in traditional software work. These challenges crop up because ML systems depend on data, experiments, and cross-team coordination. Which means organizations have to adjust both their technical workflows and their team structures. **Socio-technical challenges appear first.** Teams often work in silos. They use different tools. They use different vocabulary. And they approach problems from different angles. This slows down collaboration. It also makes ownership unclear. **Pipeline fragility shows up next.** ML pipelines break when data shifts, schemas change, or upstream systems behave unpredictably. And these failures can be difficult to diagnose because they occur across multiple components and roles. **Continual learning adds more pressure.** Retraining is required when data changes. Evaluation is needed to confirm behavior. Rollout must be controlled. And monitoring must catch regressions early. A lot of organizations aren't prepared to automate these cycles. **Platform complexity increases the difficulty.** ML systems rely on orchestrators, feature stores, metadata stores, registries, and serving layers. Each component has its own behavior and failure modes. And each one introduces a new operational boundary. **Moving to MLOps platforms can also introduce migration challenges.** Organizations have to shift from manual workflows to automated ones. And align environments. Not to mention, there's the task of making legacy systems compatible with new components. **Automation boundaries create the final challenge.** At the same time, not every step should be automated. Some require review. Some require safety checks. MLOps teams have to tackle determining where automation helps and where human oversight is needed. MLOps isn't a tooling exercise. It's a shift in how ML systems are built, operated, and maintained. Organizations succeed when they approach it as an engineering discipline with clear ownership, defined workflows, and a lifecycle that can adapt to changing data. ## Top 7 best practices behind mature MLOps ![A horizontal infographic titled Top 7 MLOps best practices presents seven numbered items arranged left to right, each with a short heading, brief description, and a circular icon connected by a flowing dotted line. The items read transparent lineage with a magnifying glass icon, enforced reproducibility with overlapping shapes, quality validation at every stage with a checkmark icon, continuous monitoring with a gear and arrows, workflow automation with connected gears, artifact governance with a document icon, and platform centralization with stacked layers and circuit lines, using a consistent palette of gray, teal, orange, blue, purple, and dark slate accents.](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/MLOps-best-practices.png "A horizontal infographic titled Top 7 MLOps best practices presents seven numbered items arranged left to right, each with a short heading, brief description, and a circular icon connected by a flowing dotted line. The items read transparent lineage with a magnifying glass icon, enforced reproducibility with overlapping shapes, quality validation at every stage with a checkmark icon, continuous monitoring with a gear and arrows, workflow automation with connected gears, artifact governance with a document icon, and platform centralization with stacked layers and circuit lines, using a consistent palette of gray, teal, orange, blue, purple, and dark slate accents.") Operating ML systems at scale requires structure. The lifecycle moves quickly, and small issues in one phase can ripple into others. These best practices help you keep the system predictable, reproducible, and easier to operate as data and conditions evolve: 1. **Establish transparent lineage** Track how data, features, and models move through the lifecycle. Record the origin of every artifact and how it changed over time. Use that lineage to trace issues back to their source instead of troubleshooting blindly. Make it available to everyone involved so decisions are based on shared context. And rely on it to support reproducibility, governance, and responsible deployment. ***Tip:*** *Use unique artifact IDs, not file paths. They remain stable across reids or moves, making lineage tracking consistent across versions and environments.* 2. **Enforce reproducibility** Capture the parameters, configurations, and environment details used in every experiment or pipeline run. Recreate those runs to confirm that results are consistent and not dependent on hidden variation. Use reproducibility to compare models fairly and understand performance differences. Apply it throughout the lifecycle so workflows behave predictably. ***Important:*** reproducibility should be the basis for trustworthy evaluation. ***Tip:*** *Pin library and dependency versions. Locking environments prevents subtle changes from newer packages and ensures experiments run consistently.* 3. **Validate quality at every stage** Check data, features, and models before they move downstream. Confirm that inputs meet expectations before training begins. Review model output for regressions before deployment. Use automated tests to surface issues early rather than after the system breaks. Always treat these checks as safeguards that reduce the risk of shipping degraded behavior. ***Tip:*** *Use thresholds to auto-reject flawed data or models. Block inputs with issues like nulls, leakage, or poor accuracy before they move downstream.* 4. **Monitor the system continuously** Observe data patterns, model behavior, and pipeline health once the system is live. Detect drift as input distributions or model outputs start to shift. Identify failing pipelines early so their impact is limited. Use monitoring to understand when the model no longer reflects current conditions. These signals should guide investigation, retraining, or deeper evaluation. ***Tip:*** *Alert on both fast spikes and slow drifts. Catch sudden failures and gradual decay early by monitoring for both patterns.* 5. **Automate lifecycle workflows** Replace manual steps with orchestrated workflows for training, validation, and deployment. Standardize how work runs so results are consistent and easier to manage. Reduce human error by letting the system handle repetitive tasks. Use automation to free up time for higher-value improvements and keep the lifecycle moving without interruption. 6. **Govern artifacts as controlled assets** Version datasets, features, models, and metadata so their evolution is clear. Use approval flows to review changes before they affect production. Capture the intent behind each update through documentation. Ensure that artifacts enter and move through the lifecycle with accountability. And maintain control so you always know what's running and why. 7. **Centralize platform capabilities** Consolidate shared MLOps functions into unified environments for training, serving, storage, and metadata. Standardize the tooling that teams use so workflows behave the same across different stages. Provide consistent infrastructure that reduces operational friction. Use platformization to simplify onboarding and coordination. Platformization also creates a shared foundation that makes collaboration easier across roles. ## How MLOps relates to adjacent disciplines (DevOps, DataOps, ModelOps, LLMOps) MLOps doesn't exist in isolation. It sits next to other operational disciplines that shape how software and data move through an organization. Each one handles a different part of the workflow. Understanding those differences helps clarify what MLOps is responsible for---and what it isn't. Here's a comparison between MLOps and related disciplines: | Discipline | What it focuses on | How it relates to MLOps | |------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | DevOps | Software delivery and operational automation | MLOps builds on DevOps but adds data, experiments, and model lifecycle needs | | DataOps | Data pipelines, data quality, and data reliability | MLOps relies on DataOps because models depend on stable, well-managed data | | ModelOps | Governance and oversight of models after deployment | MLOps overlaps with ModelOps but covers the full ML lifecycle, not only post-deployment control | | LLMOps | Operating large language models, [RAG](https://www.paloaltonetworks.com/cyberpedia/what-is-retrieval-augmented-generation) workflows, and evaluation loops | MLOps provides the foundation; LLMOps extends it for prompt behavior, embeddings, and retrieval consistency | A key detail: These disciplines have to work together. ML systems depend on data, software, and governance workflows. The result is a shared operating environment where each discipline owns part of the system. MLOps fits by connecting these parts through processes that manage data, models, code, and feedback loops as one lifecycle. ## How MLOps is evolving in the era of LLMs, agents, and retrieval [LLMs](https://www.paloaltonetworks.com/cyberpedia/large-language-models-llm) changed how organizations build and operate ML systems. They introduced new behaviors, new sources of drift, and new evaluation needs. Which means the core ideas behind MLOps still apply. But the way teams use those ideas must adapt. In other words: LLMOps isn't separate from MLOps. It's an extension of it. In practical terms: **LLMs depend on prompt patterns, embeddings, and retrieval systems. This creates new drift types.** Prompt drift appears when small wording changes alter model behavior. Embedding drift appears when vector representations shift as data changes. Retrieval drift appears when search results become inconsistent. And these changes require new monitoring signals and new ways to detect regressions. **Evaluation also changes. Simple accuracy metrics are no longer enough.** Evaluation pipelines must review output quality, factuality, and stability. These pipelines also need to run continuously because LLM outputs can vary even without code or model updates. **Then there's the fact that LLMs introduce agent workflows, which increases operational risk.** Agents take actions, chain model calls, and rely on external tools. Which means there's an increased need for guardrails. Controlled orchestration, human oversight, and review cycles help keep agent behavior predictable. **Feedback loops expand as well.** Ranking, scoring, and structured feedback become part of the evaluation process. Reinforcement signals help improve outputs. And retrieval adjustments keep the system aligned with changing data. MLOps evolves by absorbing these needs. And by extending its lifecycle, monitoring, and governance practices to support modern AI systems. ![Icon of a document](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/cyberpedia/what-is-mlops/icon-report.svg) ## RESEARCH REPORT: THE STATE OF GENERATIVE AI 2025 Get new data on GenAI adoption and usage, drawing on observations of 7K+ enterprises. [Download report](https://www.paloaltonetworks.com/resources/research/state-of-genai-2025) ## MLOps FAQs ### What does MLOps mean? MLOps is the discipline that manages the end-to-end lifecycle of machine learning systems. It unifies data engineering, software engineering, and ML engineering to build, deploy, monitor, and maintain models as reliable, reproducible, and continuously improving production systems. ### What is MLOps vs DevOps? DevOps focuses on software delivery and operational automation. MLOps builds on DevOps but adds data, experimentation, lineage, drift monitoring, model validation, and retraining workflows. It manages the behavior of ML systems over time, not just code and infrastructure. ### What is MLOps vs AIOps? MLOps governs how machine learning systems are built and operated. AIOps applies AI to improve IT operations such as monitoring, alerting, and incident response. MLOps manages ML lifecycles. AIOps uses ML inside operational tooling. They serve different purposes. ### Is MLOps difficult to learn? MLOps can be challenging because it spans multiple domains. It requires understanding data workflows, experimentation, validation, deployment, monitoring, and retraining. It also requires coordinating roles and managing system complexity. The difficulty comes from the breadth of responsibilities, not from any single task. ### What are the 4 types of ML? The four commonly referenced categories are supervised learning, unsupervised learning, semi-supervised learning, and reinforcement learning. These categories describe how models learn from data and how feedback is used during training. Related content [Report: Unit 42 Threat Frontier: Prepare for Emerging AI Risks Get Unit 42's point of view on AI risks and how to defend your organization.](https://www.paloaltonetworks.com/resources/ebooks/unit42-threat-frontier) [LIVEcommunity blog: Secure AI by Design Discover a comprehensive GenAI security framework.](https://live.paloaltonetworks.com/t5/community-blogs/genai-security-technical-blog-series-1-6-secure-ai-by-design-a/ba-p/589504) [Podcast: Threat Vector | Human in the Loop for AI Security Get the facts on how to secure GenAI beyond the model itself](https://www.paloaltonetworks.com/resources/podcasts/threat-vector-human-in-the-loop-for-ai-security) [Podcast: Threat Vector | Securing the AI Frontier Hear from experts about how CIOs can lead AI transformation securely.](https://www.paloaltonetworks.com/resources/podcasts/threat-vector-securing-the-ai-frontier) ![Share page on facebook](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/facebook-circular-icon.svg) ![Share page on linkedin](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/linkedin-circular-icon.svg) [![Share page by an email](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/resources/email-circular-icon.svg)](mailto:?subject=What%20Is%20MLOps%3F%20Machine%20Learning%20Operations%20%7C%20Starter%20Guide&body=MLOps%20is%20a%20discipline%20that%20unifies%20machine%20learning%2C%20software%20engineering%2C%20and%20data%20engineering%20to%20build%2C%20deploy%2C%20monitor%2C%20and%20maintain%20ML%20systems%20in%20production.%20at%20https%3A//www.paloaltonetworks.com/cyberpedia/what-is-mlops) 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 © 2026 Palo Alto Networks. All Rights Reserved * [![Youtube](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/youtube-black.svg)](https://www.youtube.com/user/paloaltonetworks) * [![Podcast](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/icons/podcast.svg)](https://www.paloaltonetworks.com/podcasts/threat-vector?ts=markdown) * [![Facebook](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/facebook-black.svg)](https://www.facebook.com/PaloAltoNetworks/) * [![LinkedIn](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/linkedin-black.svg)](https://www.linkedin.com/company/palo-alto-networks) * [![Twitter](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/twitter-x-black.svg)](https://twitter.com/PaloAltoNtwks) * EN Select your language