A Wicked Cool Palo Alto Networks Feature That Not Everyone Knows About

One of my roles in the company is to participate in our regular new hire training, and in our last session, I was asked a question that I had never been asked before. The question was, “What is the coolest feature in your product that not everyone knows about?” While there are many, many very cool features in our product, without hesitation I told them that it is actually a combination of three features that allow customers to collect external data and use it to automate firewall deployment and policy updates.

Let me explain.

To be specific, the three cool features I am referring to are the XML API, Dynamic Address Groups (DAG) and Virtual Machine Monitoring (VM-Monitoring). They are standard PAN-OS features and are supported in both our virtualized and appliance-based form factor firewalls. I believe the reason users don’t know about them is that they see these three features as being primarily applicable to managing the dynamic nature of virtualized environments, ensuring that security keeps pace with business.

But the best-kept secret around these features is that they are equally valuable when used with our appliance form-factor firewalls. Just think about the external data sources that you may refer to regularly and then use (manually) to manage your network security. Now imagine if there was a way to automate those tedious, day-to-day tasks. You understand the value these features might provide.

It’s true that they are invaluable in a virtualized environment because they facilitate two forms of automation:

  1. They help automate the provisioning of a VM-Series firewall so that when new virtual machines are created, our next-generation firewall can be deployed simultaneously.
  2. They bring a sense of order to policy chaos by updating policies dynamically as virtualized and hardware form-factor workloads are added, changed or removed.

In a virtualized environment, change is common and happens rapidly. But often security, as part of a set of best practices, follows a more rigid change control process that may mean delays. Therefore, the value of these three features is they allow security to keep pace with the speed of change in virtualized environments. You can preserve the flexibility of a virtualized environment and ensure important security updates get made just as rapidly. Here are two other examples of how these features solve a variety of challenges using our appliances:

  • Automating the deployment of hundreds of physical firewalls: Imagine the challenge of deploying our firewall appliance to hundreds of remote locations, quickly, consistently and cost-effectively. The solution for this customer was a strict adherence to IP addressing on the networking side that they mapped to named objects in PAN-OS such as “External_IP”, “Wireless_network”, and “Wired_workstations”. The objects are then used in Panorama Templates and the IP addresses are dynamically provisioned, greatly simplifying firewall deployment. One of our firewalls is sent to the remote location, they are connected to the network and Panorama is used to deliver the configuration via a Template. Device Groups are then used to complete the setup.
  • Enabling policy creation that accompanies IT asset allocation: In another example of how these three features can enable dynamic policy updates, a customer is integrating our firewall with their IT ticketing solution (ServiceNow) as a means of generating policy updates as new IT assets are deployed. In this scenario, the new asset (PC, Workstation, Laptop) IP address is harvested and pulled into the firewall as part of the policy update.

Most security professionals have too many things to do in a single day. The ability use the XMP API, DAG and VM-Monitoring to tie our enterprise security platform, both virtualized or physical form-factor, into external data sources as a means of automating what are normally manual and time consuming tasks is a wickedly cool feature.

Got a cool example of how you use any of these features? Comment and let us know.

Matt Keil

[Palo Alto Networks Blog]

Protecting The Data Lifecyle From Network To Cloud

Enterprises are pushing more sensitive and regulated data into the public cloud than ever before. But the journey carries many new risks.

When thinking about protecting data in the cloud, there are three areas of use that security and privacy professionals need to consider: data in motion, data at rest and data in use. In a nutshell, the data leaves your environment and goes from to point A (your network) to B (the cloud); within point B it gets initially processed and stored within a database, and then is pulled out of that database for processing. Each of these phases carries risk:

  • The first area, data in motion, is the most well known and understood. The goal of protecting data in motion is to prevent a third party from eavesdropping on a conversation on the transmission wire.
  • The next key area, data at rest, is also relatively well understood. Data at rest is essentially the data that is stored persistently in some form, as a file, in a database, etc. The goal of protecting data at rest is to prevent a third party from reading the data, should they gain access to the data in its persistent form (for example, when an attacker gains access to the file system and opens or copies the files).
  • Data in use is, effectively, the data that has been loaded into a process and is in the memory of the program that is running. In general, this data is in the clear while being processed and is typically not protected by techniques such as the in-cloud based encryption provided by Cloud Service Providers (CSPs).

In each of these three phases, there are security mitigation techniques that address the corresponding issues. Several approaches need to be evaluated, and at minimum, enterprises need to explore what their CSPs have to offer:

Data in Motion: Cryptographic protocols, such as Secure Sockets Layer (SSL) or Transport Layer Security (TLS), are typically used for protecting data in motion by establishing an encrypted and authenticated channel. Note that the data payload inside the transportation layer is still in the clear, so exploring encrypting the data itself versus (or in addition to) encrypting the wrapper should be evaluated.

Data at Rest: To protect this data, database solutions used by CSPs offer a variety of tools for encryption operations, such as transparent data encryption (which encrypts the database blocks on disk) or column encryption (which directly encrypts the column values). Moreover, there are several techniques that can be employed to encrypt file contents including encrypted file systems and block level encryption techniques.

You should note that a big concern regarding the encryption of data at rest in a cloud environment is who owns the keys, and where the keys physically reside. The benefits of data at rest protection are somewhat weakened if the data, and the key used to encrypt the data, are both stored in a less trusted security zone, such as the CSP’s environment. In response, CSPs are innovating in this space and are developing techniques whereby the enterprise, not the cloud service provider, can at least virtually owns the keys securing data at rest (even though they physically reside elsewhere).

Data in Use:  In this case, data is in the clear while being processed and is not protected by techniques such as the in-cloud based encryption provided by the CSP. The Cloud application actually needs to decrypt data from its encrypted at rest state in order to perform any and all required application processing within the CSP datacenter.  A new category of technologies focusing on data protection — dubbed by Gartner as cloud access security brokers (CASB)  — is a solution to explore here. These solutions can encrypt data before it leaves the enterprise to provide protection during the data in use phase, as well as the other data lifecycle phases. Enterprises considering these technologies should ensure that they evaluate them to identify any impact they may have on the functionality of their cloud applications. (Disclosure: Perspecsys is one of many CASB vendors with this technology).

As cloud adoption pushes greater volumes of sensitive and regulated data into cloud-based SaaS applications, it’s more important than ever for security and compliance professionals to ask the right questions about where cloud data is flowing, who has access to it and what protection mechanisms can be put in place to mitigate risks.

Gerry Grealish

[Dark Reading]

English
Exit mobile version