{"id":111835,"date":"2020-05-27T06:00:24","date_gmt":"2020-05-27T13:00:24","guid":{"rendered":"https:\/\/www.paloaltonetworks.com\/blog\/?p=111835"},"modified":"2020-08-07T15:19:56","modified_gmt":"2020-08-07T22:19:56","slug":"network-cloud-native-applications","status":"publish","type":"post","link":"https:\/\/www2.paloaltonetworks.com\/blog\/2020\/05\/network-cloud-native-applications\/","title":{"rendered":"Need to Secure Cloud Native Applications? Take a Look at Airport Security"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Securing an airport and securing your cloud-native applications have more in common than you may realize \u2013 and two essentials of airport threat prevention nicely illustrate why virtual and container NGFWs are vital for security in the cloud. As digital transformation drives you to move crown jewel applications to public clouds and containers, you need to use the same layered security approach airports typically provide.\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><b>Cloud Native Apps Need to Travel to More Than One Environment<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Before we head off to our airport analogy, it\u2019s important to understand that most enterprises today use data centers and multiple public clouds. On top of that, they run workloads, some of which now may be <\/span><a href=\"https:\/\/www.paloaltonetworks.com\/blog\/2020\/05\/containers-are-inherently-secure-reality-or-myth\/\"><span style=\"font-weight: 400;\">containerized<\/span><\/a><span style=\"font-weight: 400;\"> or <\/span><a href=\"https:\/\/www.paloaltonetworks.com\/blog\/2019\/11\/cloud-serverless-security\/\"><span style=\"font-weight: 400;\">serverless<\/span><\/a><span style=\"font-weight: 400;\">, but most organizations still have plenty of bare-metal servers, virtual machines and even mainframes.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">But regardless of where workloads run, what companies really care about are the enterprise applications running on top of their hybrid infrastructures. These enterprise applications tend to be highly interconnected. Most apps connect to core services \u2013 services such as Active Directory, administration, monitoring and logging infrastructure. Many of these apps also connect to critical databases running on legacy systems such as Solaris or mainframes. Because it's <\/span><i><span style=\"font-weight: 400;\">the network<\/span><\/i><span style=\"font-weight: 400;\"> that connects these apps, network security needs to span the entire infrastructure. That\u2019s why network protection for cloud native applications needs to be approached holistically. Cloud native applications don\u2019t live on isolated islands or an annex tucked away from the rest of an airport.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Complete network protection requires next-generation firewalls (NFGWs) and identity-based microsegmentation. And because our cloud journey is an ongoing journey, it\u2019s important to gain complete visibility into all the connections made over the network. This includes internet to the workloads, workloads to the internet, and workloads to workloads.\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><b>Scanning and Detection are Vital for Airports \u2013 And Your Public Cloud Journey<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Visibility into the overall environment is a first step, but only a first step to ward off threats \u2013 we\u2019d all worry if airport security was limited to CCTV cameras. Fortunately, airports have two additional and deeper layers of security, which are instructive when it comes to securing cloud native applications:\u00a0<\/span><\/p>\n<p><b>1. Full body and luggage scanners:<\/b><span style=\"font-weight: 400;\"> The goal of this layer is to ensure that people heading toward departing airplanes are not carrying anything dangerous. Security agents (such as the TSA in the United States) perform this task with scanning equipment that examines people, luggage and myriad small items. Airport authorities deploy this process at strategic locations. Some airports have only one security and scanning station at the entrance, while bigger airports tend to have one or more at the boundary of each terminal.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And this is where NGFWs come in, because they map to these<\/span> <span style=\"font-weight: 400;\">security scans. Just as security is deployed at strategically chosen perimeters at the airport, NGFWs need to be deployed at carefully chosen perimeters or trust boundaries.\u00a0\u00a0<\/span><\/p>\n<p><b>2. Boarding pass scanners: <\/b><span style=\"font-weight: 400;\">The goal of this layer of inspection is to reduce the attack surface by minimizing the movement of people into places where they are not supposed to go. Boarding pass scanners are deployed at every gate \u2013 typically as close as possible to the boarding entrance of the appropriate airplane.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Similarly, <\/span><a href=\"https:\/\/www.paloaltonetworks.com\/cyberpedia\/what-is-microsegmentation\"><span style=\"font-weight: 400;\">microsegmentation<\/span><\/a><span style=\"font-weight: 400;\"> is another form of access control that reduces the attack surface by minimizing allowed connections between workloads. If you only allow connections absolutely required for applications to function and then block everything else, damage can be significantly minimized because a breach can be effectively contained to the location where it occurs. In cloud-native environments \u2013 where workloads are very dynamic and IP addresses are meaningless \u2013 microsegmentation policies need to be enforced by using the identity of the workloads. The Palo Alto Networks Prisma Cloud platform delivers <\/span><a href=\"https:\/\/www.paloaltonetworks.com\/blog\/2020\/05\/network-data-center-transformation\/\"><span style=\"font-weight: 400;\">scalable<\/span><\/a><span style=\"font-weight: 400;\">, identity-based microsegmentation that complements the capabilities of the NGFW.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Just as boarding pass scanners are deployed at every airport gate, microsegmentation needs to be enforced at every workload, and agent-based solutions are best suited for enforcing microsegmentation policies right at the workload level.\u00a0<\/span><\/p>\n<figure id=\"attachment_111836\" aria-describedby=\"caption-attachment-111836\" style=\"width: 900px\" class=\"wp-caption aligncenter\"><div style=\"max-width:100%\" data-width=\"900\"><span class=\"ar-custom\" style=\"padding-bottom:80.67%;\"><img loading=\"lazy\" decoding=\"async\"  class=\"wp-image-111836 lozad\"  data-src=\"https:\/\/www.paloaltonetworks.com\/blog\/wp-content\/uploads\/2020\/05\/staging-environ.png\" alt=\"\" width=\"900\" height=\"726\" \/><\/span><\/div><figcaption id=\"caption-attachment-111836\" class=\"wp-caption-text\">Microsegmentation on workloads with NGFWs at trust boundaries.<\/figcaption><\/figure>\n<h2><b>Understand What Goes into Cloud Native Scanning and Detection<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Now, let\u2019s discuss what kinds of protection the NGFWs provide in these cloud-native environments:\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><b>Inbound Protection: <\/b><span style=\"font-weight: 400;\">In order to serve applications to users on the Internet, workloads<\/span> <span style=\"font-weight: 400;\">need to accept connections from the Internet. Most modern applications are exposed on HTTPS, and inbound connections are generally protected by cloud-based web application firewalls (WAFs). Still, most workloads \u2013 not just Internet-facing workloads \u2013 need to accept inbound connections from orchestration and monitoring tools such as<\/span><a href=\"https:\/\/www.terraform.io\/docs\/enterprise\/before-installing\/network-requirements.html\" rel=\"nofollow,noopener\" > <span style=\"font-weight: 400;\">Terraform<\/span><\/a><span style=\"font-weight: 400;\"> and<\/span><a href=\"https:\/\/puppet.com\/docs\/pe\/2018.1\/system_configuration.html\" rel=\"nofollow,noopener\" > <span style=\"font-weight: 400;\">Puppet<\/span><\/a><span style=\"font-weight: 400;\">, connections on MySQL ports from database admins, and on the ssh\/RDP ports from the server admins.\u00a0<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">These allowed connections \u2013 combined with software vulnerabilities and the ongoing struggle to deploy patches \u2013 increase the risk of attackers breaking into your infrastructure. Case in point, our researchers deployed a containerized version of Drupal 8 fully secured by cloud-native security tools in a public cloud. The container was compromised in 45 minutes. You can read more about this particular attack in our whitepaper, <\/span><a href=\"https:\/\/start.paloaltonetworks.com\/5-major-security-threats.html\"><span style=\"font-weight: 400;\">\u201cFive Major Security Threats and How to Stop Them.\u201d<\/span><\/a><\/p>\n<p><span style=\"font-weight: 400;\">An NGFW continuously being updated from a cloud service, however, can protect these workloads from threats and exploits so your workloads don\u2019t end up being used for bitcoin mining or other malicious activity.\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><b>East-West Protection<\/b><span style=\"font-weight: 400;\">: <\/span><a href=\"https:\/\/www.paloaltonetworks.com\/cyberpedia\/what-is-a-zero-trust-architecture\"><span style=\"font-weight: 400;\">Zero Trust<\/span><\/a><span style=\"font-weight: 400;\"> philosophy assumes that it\u2019s not a matter of <\/span><i><span style=\"font-weight: 400;\">if<\/span><\/i><span style=\"font-weight: 400;\"> but <\/span><i><span style=\"font-weight: 400;\">when<\/span><\/i><span style=\"font-weight: 400;\"> someone will break into your infrastructure. That\u2019s why you need to have east-west protection in place to prevent threats from moving laterally. Not all applications have the same risk of a breach or the impact on business. Some have higher risk because they run vulnerable software or are directly connected to the internet. Others are just more important in the larger scheme of things because they have access to your business-critical data.\u00a0<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Deploying an NGFW with threat protection capabilities for all the traffic that crosses the trust boundaries (such as traffic between staging and production or production and PCI environments) allows you to successfully contain a breach and prevent it from moving laterally to mission-critical applications or data.\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><b>Outbound Protection:<\/b><span style=\"font-weight: 400;\"> Most workloads need to connect outbound to the Internet for activities such as downloading software updates or using public APIs (such as the egress requirements for Terraform and Puppet). This means outbound connectivity on TCP ports 80 and 443 need to be allowed for most workloads with cloud-native access control tools such as AWS Security Groups or Kubernetes network policies.\u00a0<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Allowing outbound connectivity from port TCP ports 80 and 443 to the Internet also gives attackers the ability to exfiltrate data from these workloads, download malware from dangerous sites on them, and use these workloads to launch DoS attacks on other sites. This means port-level controls won\u2019t cut it for outbound protection.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">You can use the layer-7 filtering capabilities of an NGFW to only allow the required connections and block everything else. The URL filtering capabilities of an NGFW can easily and automatically block connections to any malicious websites on the Internet.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><b>Three Factors Help Decide NGFW Location<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Just as airport security must choose where full scanning takes place, network security teams need to choose the trust boundaries where NGFWs will be deployed. Three factors often play into these decisions:\u00a0<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Compliance requirements for the applications, such as the Payment Card Industry Data Security Standard (PCI DSS).<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Breach risk for an application driven by unpatched vulnerabilities \u2013 whether or not the application is connected directly to the Internet (both inbound and outbound).<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Business impact of a breach, which is driven by how mission critical that application is for the enterprise.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Zero Trust philosophy calls for pushing the trust boundary as close as possible to applications, but operational complexity can keep pushing it back. Most enterprises make boundary decisions based on their security budgets and ability to push security deeper into these environments.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In the public cloud, Amazon Web Services (AWS) virtual private clouds (VPCs) or Microsoft\u00a0 Azure virtual networks (VNETs) are generally chosen as the trust boundaries, which calls for NGFWs to inspect traffic going in and out of these perimeters.\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h2><b>Get Packed Up and Ready to Go<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Just like a trip to the airport, security for cloud-native applications and workloads require that you understand the journey, the destination \u2013 and what you need to pack. Complete network visibility, identity-based microsegmentation at the workloads, and next-gen firewalls deployed at strategically chosen trust boundaries will move you closer to the Zero Trust posture needed to protect your organization as it moves forward with cloud native applications and workloads.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For more information about cloud-native risk in your travels, come to the <\/span><a href=\"https:\/\/start.paloaltonetworks.com\/secure-enterprise-transformation-now\"><span style=\"font-weight: 400;\">Make It Real!<\/span><\/a><span style=\"font-weight: 400;\"> virtual launch event in June. You\u2019ll have a first-class seat as we unveil industry firsts in container network security vital for securing cloud-native applications. <\/span><a href=\"https:\/\/start.paloaltonetworks.com\/secure-enterprise-transformation-now\"><span style=\"font-weight: 400;\">Register and save the date for \u201cA Paradigm Shift In Cybersecurity...Intelligent Network Security\u201d<\/span><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h5><strong>Intelligent Network Security: LinkedIn Live Broadcast<\/strong><\/h5>\n<p><span style=\"font-weight: 400;\">AJ Shipley, vice president of product, and Paul Calatayud, Americas CSO, appeared on LinkedIn Live to answer questions about the industry\u2019s first ML-Powered NGFW. <\/span><a href=\"https:\/\/www.linkedin.com\/video\/live\/urn:li:ugcPost:6681933905844584448\/\" rel=\"nofollow,noopener\" ><span style=\"font-weight: 400;\">Watch the event on-demand<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>2 essentials of airport threat prevention nicely illustrate why virtual and container NGFWs are vital for securing cloud-native applications.<\/p>\n","protected":false},"author":663,"featured_media":108494,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[6768,6765],"tags":[6504,111],"coauthors":[7128,6821],"class_list":["post-111835","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-secure-the-cloud","category-secure-the-enterprise","tag-container-security","tag-ngfw","net_sec_category-next-generation-firewalls"],"jetpack_featured_media_url":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-content\/uploads\/2020\/03\/IMG_2009.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/111835","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/users\/663"}],"replies":[{"embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/comments?post=111835"}],"version-history":[{"count":10,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/111835\/revisions"}],"predecessor-version":[{"id":117369,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/111835\/revisions\/117369"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media\/108494"}],"wp:attachment":[{"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media?parent=111835"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/categories?post=111835"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/tags?post=111835"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www2.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/coauthors?post=111835"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}