MobileIron plus Cisco: Mobilizing Network Security
Webinar transcript - View the full webinar
Cynthia Ryan: Good morning, everyone. This is Cynthia Ryan from MobileIron. I'm the solutions marketing manager for the Business and Corporate Development Group and I'll be hosting this event today.
We're going to give another minute or so for few other people to join, but then we will be getting started shortly.
I want to call your attention to the Q&A window. Please, feel free to use that window at any time during the presentations. We have people standing by to answer questions live, as well as verbally include your questions in the events at a break between sections.
Let's sit tight for another minute or so and then we'll get started. Thank you for your patience.
Cynthia: Good morning, everyone. This is Cynthia Ryan from MobileIron, the solutions marketing manager. I'll be your host for this event today. We will be discussing MobileIron plus Cisco and how you can mobilize network security.
We're going to start by introducing our host.
As I said, my name is Cynthia Ryan and I'm the solutions marketing manager at MobileIron in the business and corporate development group.
I've spent about 15 years in tech, largely on the business side, doing partnerships and alliance managements. I've worked in a variety of different functions including consulting, direct sales, and partner management at companies such as Accenture, Hewlett Packard, and Amazon Web Services.
Our first speaker today will be Fran Thorpe. She is head of the business development and corporate development group, Technology Alliances Department. Over the last 15 years, Fran has successfully blended science and art to develop go‑to‑market strategies, driving mobile speed changes.
At MobileIron, Fran heads up the team responsible for managing our network of over 350 technology partners. Together with our partners, we help each of our customers get the perfect solution mix for their business.
We have from Cisco, our first speaker is Amit Kulkarni, who is product manager at Cisco where he's been for a little over seven years.
Amit is a software marketing professional with a blend of technical and business skills. Amit's main area of expertise lies in VoIP and network security domain. He serves various roles, including product management, solution architecture, software engineering, and post sales engineering.
Finally, our last speaker is Paul Carco, who is a technical marketing engineer at Cisco with over 18 years at Cisco. He's one of the original AnyConnect VPN technical marketing engineers. Now, he's a member of the Advanced Threat Solutions area where Paul's role has expanded to include The Cisco Security Connector and its integrations with both Cisco and partner solutions.
Just a couple of things about housekeeping. This webinar is being recorded. A recording will be available afterwards at our MobileIron home page in the resources section, under library. In library, there's a section for webinars. It will be available there along with a transcript, the slides, as well as some additional information on the topics that we'll be discussing today.
As I mentioned before, we do welcome your questions. Some of them will be responded to in writing as the speakers are speaking. Others of them will be responded to them verbally during the presentation, right between the sections. Please take a look at your Q&A window and feel free to use it if you would like.
I want to talk a little bit about why we're here. Gartner, this year, in its UEM Magic Quadrant, or its Unified Endpoint Management Magic Quadrant, called MobileIron out as a leader in the space. One of the strengths that they listed about MobileIron specifically is the fact that we integrate with a large security ecosystem.
Why is that important to you? Because there are many security solutions out there that have been serving in the on‑premise and traditional IT world for a long time, like Cisco Solutions.
As we move forward into the mobile and cloud service arena, what we want people to know is that you can still get the best‑of‑breed solution by using what you've been using already, like Cisco, and bring in MobileIron into that picture.
One of the questions we get a lot from our customers, and prospects, and partners is, "Gosh, I didn't know that you could do with Cisco and MobileIron some of things that you can do." We're here to talk about how you can really get value, and flexibility, and best‑of‑breed solutions, by working with partners.
We would very much like to hear from you, by the way. If you ever have questions or would like to reach out to us afterwards, please feel free to email us at firstname.lastname@example.org. We're here. We would love to hear from you.
With that, let's get into our agenda. I'm going to turn it over to our first speaker, Fran Thorpe, to talk a little bit about MobileIron. Fran?
Fran Thorpe: Thank you, Cynthia. I welcome people who are attending this seminar. I hope this diagram starts to resonate with some of you. MobileIron and our customers are the center of a huge shift in how we are working together to get work done.
Many of you have been listening to today's presentation are likely charged with securing or managing corporate endpoints and applications that reside at those endpoints.
Those endpoints, whether they're laptops, desktops, or phones, or even Apple gear, or Android gear and Apple watches, it can be just about anywhere, not necessarily on the corporate network or owned by the business. These devices are not necessarily owned by the business.
They are accessing applications and business data that are no longer behind a firewall or part of a private cloud, but they're SaaS applications that could be available like [indecipherable 7:47] hosted in the Cloud.
When we started about 10 years ago with MobileIron, iPhones were an [indecipherable 7:56] case. The C level suite was wanting to use the iPhone as their communication device and they wanted to get email. That was pretty simple.
Now, iPhones, iPads, Android, and Mac, are all first‑class endpoints and the ways to deploy and management secure these endpoints are becoming more and more sophisticated. This is where we come in.
Cynthia, next slide, please.
MobileIron is part of this transformation.
You can build out the slide.
Our solutions and services ensure that the device identity, and application information, and risk based on that, is understood by the admin in the [indecipherable 8:39] office, so that access is granted, real‑time, to the right user, on the right device, at the right time.
We see ourselves as the system of records for trust for that last mile or that last moment, when the user needs access to that information on whatever device they're using.
Next slide, please.
As this plays out, as the system of records, we have visibility to critical contextual data that can help inform broader security and compliance decisions with traditional network solutions.
We have insight on entities like the user, the device and applications, and attributes about their health state, etc. That could be used to access risk in other solutions and add to a risk assessment in other solutions.
We are able to enforce compliance, i.e. access to that application or for that user, on a device based on the risk profile that's created.
Next slide, please.
Essentially, we see ourselves...As networks and security and management has become more complex, our role has expanded and we see ourselves in three ways, specifically.
We can act as a decision point as we define policies for access and compliance. We can act as a policy information point, where we can provide dataset on these entities such as the device, the user, and the application. We provide attributes about these entities as appropriate.
As a policy enforcement point, we can take remediation actions as a finder instructed by other network solutions and based on that policy. We can remove access, require new passwords, etc., in extreme cases.
The interesting thing is Cisco is one of the very first vendors to take advantage of this dataset as part of their ISE solution. Back in 2013, they used this data to write access to BYO devices.
Since then, our dataset has broadened and the use cases for the ISE solution has evolved and we will definitely get into more details on that as the presentation roles out.
Endpoint security has always been a core use case. Since Apple introduced iOS support throughout VPN 2013, our integration with Cisco AnyConnect VPN has become the most used VPN client amongst our customer base.
Whether they're being used as bedside check‑ins in hospitals, or POS devices in retail, or by flight attendants, Apple devices have become first‑class endpoints. Cisco and Apple have collaborated to release additional security in threat detection, based on this broader use.
It's specific to iOS devices which are managed as part of a corporate fleet. Integration with MobileIron's UEM, as part of Cisco's secure connectivity solutions, is a key component of this functionality.
What happens is with that, using MobileIron, our customers can deploy the security feature to thousands of devices in a matter of minutes. It's great to offer extended value of our two solutions, enabling our customers to confidently role out mass deployments of mobile devices, with an ability to securely and easily access applications in the cloud and on the network.
Now, I'd like to turn over the time to Amit and Paul to take you through specifically what Cisco is doing with these integrations.
Cynthia: This is Cynthia. I'm going to interject one thing here that I meant to say earlier. You're going to see references to UEM which is Unified Endpoint Management. You're going to see references to MDM, or Mobile Device Management, and you're going to see references to EMM, Enterprise Mobility Management, frequent throughout this presentation.
That is simply a reflection of the change of the name of the category that we've been in. Anytime you see any of those abbreviations during this presentation, just think MobileIron. With that, I'll hand it over to Amit.
Amit Kulkarni: Thank you Cynthia. This is Amit Kulkarni, product manager on the Identity Services Engine at Cisco.
We're going to walk through some of the use cases that we see a lot of our customers take a look at and use when they have the Identity Services Engine and MobileIron in their environment.
Let me first walk you guys through a little bit of what ISE, or Identity Services Engine, is about. For folks that know and have seen this, it's basically the next gen [indecipherable 13:33] very simplified, but it's a lot more than that. Let me walk you through what are the main things that have happened in the past and where they're going.
In general, conventional management in terms of network access has been painful and is risky in the past. There have been lots of new users, new devices that have come onto the network.
The IT needs to evaluate various things before giving personalized permissions for every access point in the network, whether that is through the wire channel, the wireless channel, or through remote access channel. It becomes quite difficult in terms of the way policies or access gets defined.
Without the ability to get a single consumable view for all these users and devices, there could be different gaps that may exist in the way access is granted. As a result, there might be sections of the network that become vulnerable to unwanted intrusions or unwanted access.
On the other hand, if you start becoming very protective and you have very restrictive policies, you could get to a scenario where there are non‑threatening employees that are just doing something different slightly and get stranded without the access that they need to do their jobs effectively.
What ends up happening if I am using my machine in a particular building and I happen to get into a different building, which is probably new, IP addresses have changed, what ends up happening if my access is defined based on IP addresses? There is a newer way of doing this these days. This is what we are going to walk through in a bit.
With Cisco, what we do provide is contextual awareness and software‑defined segmentation to unlock this next gen of secure access for the business. With this approach, what you could do is you could set up network permissions ahead of time, you can create policies that match business roles that an end user has, and the access that they need to get as a result of those roles.
When someone requests access, system can use the information associated with the user and the device, and they automatically identify their business role. As a result, you get access to the parts of the network that you need to.
The identity that ISE collects is shared across the entire network infrastructure that you have, so that the right level of access is enforced consistently throughout the entire network. With Cisco, what we strive to do is to make sure that we give you, our customers, the ability to grant access to your end users, to your internal customers, the way they need access to.
The other thing with software‑defined segmentation and some of the other aspects that we'll walk through a little bit, is to maximize your security of the network and to contain any breaches that you might end up having. Hopefully not, but we know that that is a given. The question is how do you contain that?
The other thing that we will talk a little bit about is how you can also streamline your network management. Let's talk about this in detail as well.
When customers get full access, your internal customers, they want to do that without interruptions from IT. What we strive to do is to give ubiquitous access, as I mentioned earlier, through your business role definition and your endpoints that you bring in.
Given that the endpoints, as Fran mentioned earlier, started with BYOD back in the day, but with a lot of the mobile devices coming onto the network, we provide you the ability to onboard these devices in a simpler and easier fashion.
The other aspect that ends up happening because of the automation is it relieves any tensions between ITs and users. The end users can bring in the devices that they want. It becomes pretty seamless for them to actually access the network, and there is less friction between the IT and the end users.
The other aspect is how do you safeguard the network? I talked about this a little bit but let's talk in a little bit more detail. We have so many devices that are now on the network. The question then becomes is how do you validate the security portion of those devices?
How do you make sure that you get total visibility for all these devices that are connecting to your network ‑‑ either from within the campus, or in the campus and going outside ‑‑ to the cloud? The other aspect is once you validate the security portion of these endpoints, how could you immunize your network so that you reduce the attack surface?
What can you do from a segmentation perspective so that you have a higher level of a security portion across the entire network? Last but not the least is how can you automate any tech protection that you have? I'm sure a lot of you have multiple different products from a security angle in your network.
How can you stitch together these multiple products together so that there is a consistent view across your entire infrastructure? We'll talk about that in here as well.
The last aspect that I wanted to talk about is the integration of those products within your infrastructure. That's where we have spent quite a bit of time developing what we call a CSTA, which stands for Cisco Secure Technical Alliance.
That is a large list of vendors that we have, integration sweep. I forget what the last count was, but there are some 100‑plus vendors and products out there that we integrate with.
Today we are obviously going to be focusing a lot on MobileIron and what we can do with MobileIron. As I mentioned, ISE provides the ability to give your end users ubiquitous access based on their business roles and the devices.
What does that really mean? It's essentially a centralized method to provide trusted users and trusted devices access to trusted apps and services. We spend a lot of time on making sure that users and devices are actually trusted.
We spend some time on making sure that we know who the user is, we can identify that, we can identify the various devices on your network, and again, identify the security compliance or the [indecipherable 21:10] state of those devices.
Now, when we talk about devices, a lot of these conversations end up on mobile devices. What ISE provides are multiple things associated with mobile devices coming onto the network. We can not only provide BYOD, or bring your own device, services, where those devices can be provisioned. Certs can be provisioned on those phones, as well.
Based on the role of that specific user, we can decide whether to check their public Internet access or corporate act.
The big thing that we have been seeing when we talk about mobile devices like the iOS, like Androids, Mac OS, etc., is the ability to get even compliance information associated with that.
This is where the integrations come in for ISE. We integrated with MobileIron, as Fran mentioned, way back in 2013, for our customers to be able to take a look at the [indecipherable 22:20] compliance of iOS and Android devices.
Some of the things that we do provide you to take a look at are checks associated with the general security compliance of the mobile devices as defined in MDM, which will be the MobileIron software, as well as take a little deeper dive into some very specific statuses of the mobile devices, such as the encryption status, the PIN lock status, jailbreak status, etc.
When you think about what happens, when mobile device comes into the network, it can register with ISE directly and can get only Internet access. The additional benefit that you can leverage when you integrate ISE with MobileIron is to actually check the compliance status of your mobile devices directly with MobileIron and allow proper access.
Whatever network resources they need to be able to access, you can define that in the policy. Let's talk a little bit about what these policy checks look like. You could do, as I mentioned a couple of times before, just general compliance status based on the policy definitions within MobileIron.
You could be a little more granular and actually start taking a look at things on the disk impression, the PIN lock status, and jailbroken status, as well. Further, you could also use different attributes that exist within MobileIron for those mobile devices to make some policy definition.
Let's take, for example, way back, a few years back when we had these problems with a certain type of an endpoint.
Those endpoints were being "banned" on the network. You could take a look at that manufacturer and the model number to set up a policy condition that says that if it is from this vendor and from this model type, you want to block that specific endpoint from connecting back into the network.
The other thing also that you could do is do what we define as passive reassessment, which means that there is a periodic check that you could do for the compliance status of those endpoints. Even though an endpoint has connected to the network, you could do a reassessment every x minutes or seconds based on whatever timer you configure.
If things change, the policy could be such that ISE would send a change of authorization to terminate the session that already exists.
I'm going to walk you quickly through what the flow looks like for an endpoint that comes in. Once an endpoint comes in, if it is not registered with ISE, we can do supplicant provisioning for a BYOD‑type scenario and provide an Internet access, and ISE can trigger a COA for them, providing the Internet access.
If it's already registered ‑‑ and by the way, this is just a sample flow, you could define peer policy much differently as well. If it is not registered with an MDM, you can point ISE to the onboarding page for MobileIron. That sends a COA, where the MobileIron can then go out and provision the endpoint.
Once that's done, ISE can check for the compliance status of the endpoint with MobileIron, and if it is not compliant, for whatever reason ‑‑ whether there are certain applications that need to be pushed, or whether the passcode needs to be set, six digits or what have you ‑‑ that could be done as well.
Once we establish that the endpoint is compliant with the policies in MobileIron, we could pretty much give access to the endpoint. Some additional actions that you can take from ISE would include things like fully wiping the endpoint, or just the corporate piece, or setting the PIN lock.
This is basically done where ISE sends a request to MobileIron to take this action on its behalf and MobileIron then goes out and takes that action.
This is a little bit smaller than what it looks like, what I wanted to share, but basically this is an ISE screen that shows the report, the type of data that you can see that ISE has gathered for various endpoints. We have things like the PIN lock status, the registration, etc. We can definitely give a lot more details about this if you guys are interested.
With that, I'll turn it over to Paul.
Paul Carco: There was a couple things I wanted to talk to you about today, so a couple of the integrations that we have. First and foremost, the Cisco Security Connector, CSC, and its integration with MobileIron. As well, at the end, I have a little bit about our per‑app, the VPN integration with MobileIron.
What is a Cisco Security Connector? First of all, it's an iOS app. What it does is it provides unprecedented visibility and control for organizational‑owned iOS devices. CSC is made up of two of our Cisco offerings ‑‑ AMP for endpoints, which provides the Clarity component or extension and also the Umbrella extension, which is our DNS protection.
What do you get from the Clarity piece? You get visibility into network and device traffic that you didn't have before. You get app inventory for each device. Usually when I say that, and especially with this audience, you might say, "I already get app inventory now with UEM."
It's true. It's a little bit different with CSC. You get that inventory, but you also get the app trajectory. You see what that app is doing and who's doing it. Where is it going on the network?
With Umbrella, you're going to get automatic blocking of known phishing sites, so the Umbrella cloud is keeping up to date with those known phishing sites and will block those attempts and throw up a block page to the user. It also will block connections to malicious domains so that sensitive data remains protected at all times.
I want to talk about the use case here, in case you're considering doing this, and whether this is a fit for you to try out. This is intended for supervised devices only, so it's not a BYOD solution. It's not for DEP‑enrolled enterprise‑owned devices that are unsupervised, and it's not for simply enterprise‑owned non‑supervised devices.
It must be managed and supervised, like in the case of this iPhone here you see on the right, by MobileIron.
The key takeaway here, if you take anything from my 10 slides on CSC, two things are what you get ‑‑ visibility and control. That's what it's all about here.
You're going to gain insight into activity on the iOS devices during the incident investigations, and the control to defend against those phishing attacks and accidental browsing to bad sites. Those are two things to remember about the Cisco Security Connector.
Apple has arguably had one of the strongest platforms from a security standpoint. If you look at an iOS device at the system level, things like Touch ID, device passcode, Secure Enclave, Secure Boot, or Data at Rest on a device with the keychain uses our encryption.
Then, with their apps, they've very strange. All the apps must be code‑signed. They go under an app store review. The developers are verified and sometime the apps are sandboxed. With the network, they provide always on and on‑demand VPN, ToS, IPv2, and also per‑app VPN.
For network activities, customers can protect the data in transit using the various VPN modes and various authentication methods, whether it's certificates, and certificates plus two‑factor, and using the different protocols, whether it's SSL, TLS or IPv2.
However, when VPN is not active, which honestly is the vast majority of the time, there's no way to know what the apps or the user via the apps are requesting over the network.
While VPNs are certainly useful to gain enterprise remote access, which makes me happy since I focus mainly on VPN, the VPNs can also be problematic to gain visibility and control for that network activity. This is where CSE solves that problem.
Working closely with Apple like we do at MobileIron ‑‑ and what I'm showing you on this slide, so you understand how we're doing this ‑‑ we were able to get a shim between the apps and the networking API in iOS, which was unheard of. We're the first ones, I'm not sure if we're the only ones still, but we were the first ones.
What this allows us to do is gain visibility into URLs before the communications is encrypted.
Typically, when I do have time for a demo, not here today, or talk about this, an example would be there are browser apps out there, [indecipherable 32:40] browsers, which the intent is to encrypt traffic from the endpoint to a server somewhere on the Internet, with the intent of just hiding what's going on.
Actually, in that case, the DNS request would be blind to Umbrella, but Clarity steps in because we see it before it's encrypted and be able to pick up on that malicious activity. This is the control and visibility.
Again, Cisco Security Connector, two functions ‑‑ the Umbrella DNS layer enforcement encryption. If you're not familiar with Umbrella at all, we're intercepting that DNS request, sending it up to the Umbrella cloud.
Based on the policy, we're either going to throw a block page up at the user or return what you typically get with your DNS request with the IP address for the FQDN or the site they want to go to.
With Clarity, this allows apps auditing, and correlation of the logs, encrypted URL requests, like I just mention. We do this without SSL decryption. Again, because of that shim, we don't need to be the man in the middle and unencrypted that traffic, inspect it, and re‑encrypt it. We don't need to do that with this app.
Again, in Clarity, this is for supervised and managed devices already in place, using MobileIron.
How we integrate with MobileIron specifically, here, on this slide.
MobileIron worked with us early on with this. MobileIron is able to take our mobile configs from both our Umbrella and our [indecipherable 34:32] endpoints platforms and push and configure this Cisco Security Connector, with the two extensions, to the known supervised devices that MobileIron already has in the system and knowledge of.
Paul: Just a summary of what these three pieces do. MobileIron, the UEM ‑‑ and I was saying MDM up until yesterday ‑‑ is all about the endpoint management. They manage those supervised devices so that we can push out the Cisco Security Connector with Umbrella.
Umbrella's going to give you that accident avoidance and control over content with the intelligent proxy built into Umbrella. Clarity's going to aid in Internet response and awareness of what the app and the user's doing, as well as the ability to block at the IP layer.
I mainly use the term visibility with Clarity. You do have some control with Clarity because it is possible to define an IP blacklist and do some blocking with that, but most of the control would come with Umbrella. That was Cisco Security Connector.
Per‑app VPN. I've been working with MobileIron probably six years when they first started to work with AnyConnect, to be able to push and provision AnyConnect. About four years ago, I then worked again with MobileIron on per‑app VPN.
First I want to talk about VPN. When you look at AnyConnect, there's three main modes that AnyConnect will work on. Most are probably familiar with full tunneling. You establish that tunnel to the headend. In the case of Cisco, with the ASA. All traffic traverses the tunnel, whether they use it one side or not.
We can also do split tunneling based on IP. We can do split tunneling based on domains. Our per‑app VPN is essentially split tunneling for your applications.
What this allows us to do. In all truth, when working with MobileIron, MobileIron will do most of the heavy lifting because it will define what app should traverse the tunnel.
What we'll do is define the policy on our headend. It essentially says, "Trust the policy push for MobileIron and enforce it." Only the apps that MobileIron has explicitly said should traverse the tunnel will come across that tunnel. Everything else will be dropped.
If Facebook wasn't specified by the MobileIron config to traverse the tunnel, the ASA will see that based on its app ID and just drop it dead in its tracks.
Per‑app VPN specifically for iOS, it does work on Android also. It is for managed devices. Unlike Cisco Security Connector, they don't need to be supervised. They just need to be managed.
The policy's provisioned by MobileIron. Because of that, it allows us...As I was just saying, our policy can simply be a wildcard that says, again, "Trust what the policy MobileIron push down states." It will just enforce that at the headend.
The last slide I have on per‑app is just the build out of the flow here. Obviously, the mobile user will request the connection to the headend. They'll be challenged for authentication, whether that's certificates or two‑factor, etc.
They'll respond back with the credentials, along with what we call ACIDex or AnyConnect ID Extensions. At that point, the ASA is going to push that policy that I talked about down to AnyConnect. We could have a policy that was built out in its base64 blob that's only readable to the ASA and AnyConnect.
We could specifically build our policy out to list the apps that align with what MobileIron has specified. Typically, best practice is just to specify a wildcard and have that push down to AnyConnect. At that point, the MobileIron config is there. We have knowledge of those apps on AnyConnect.
Again, as I said in this previous slide, if not explicitly defined there from MobileIron, we will just disallow it. Only the permitted apps will traverse.
With that, I will hand back over to Cynthia.
Cynthia: Thank you so much, Paul. I really appreciate your covers of CFC and VPN. Thank you, Amit, for covering ISE.
Paul: Sorry if I was too low. I didn't know. I just saw that. Hopefully, wasn't too low.
Cynthia: That's OK. [laughs] It made me be quiet and listen carefully. It was all good.
Before we move into Q&A, I just want to emphasize to our audience that our partnerships with Cisco and MobileIron has legs. It's been here a long time. We've got a lot of great case studies, particularly around the ISE integration and the AnyConnect integration.
These are long‑standing, popular, well‑consumed integrations. We're working on case studies for the security connectors since it's a little bit of a newer technology, and particularly with the advent of iOS 12. We have a lot of information that we can share with you about customers like yourself who has been successful.
We will be sending out follow‑up emails with links to integration guides, datasheets, those kinds of things. As I was changing my slides, unfortunately, I left out an important thing ‑‑ where you can also get additional information, which is marketplace.mobileiron.com.
If you go to marketplace.mobileiron.com and search Cisco, you will see listings in that marketplace for each of the technologies that we've spoken about today. Within each of those listings are additional information about the product.
With that, we're going to go to Q&A. Some of your questions were answered actually during the webinar by one of our trustee Cisco colleagues, Imran. I'm going to start with the ISE questions.
Cayman asked, "How does ISE check jailbreak/root status on a device?" The answer is it checks with MobileIron via APIs.
Our next question came from Cole, who asked, "Are there any plans to allow ISE to check for device ownership status, company versus employee‑owned?" The answer to that is if referring to the device owner flag corporate device under MobileIron, then this is on the ISE roadmap.
We had a question from Jessica about whether Cisco Security Connector works with both MobileIron on cloud and on‑prem. Paul, did you want to comment on that a little bit further?
Paul: I'm sorry. I was answering a question in the Q&A panel there. If Cisco Security Connector can work with both? Yes.
Cynthia: We've got a question from it looks like Roseo. "How does this differ from MobileIron Access and Sentry setup?"
Fran: I'll just take that [indecipherable 43:23] please, Fran. I assume we're saying how does Cisco and AnyConnect differ from Access and Sentry setup. I'm not sure about when you're talking about setup or product? I don't know if you want to qualify that, Roseo?
Cynthia: Roseo, if you want to just type a little bit more into that Q&A window we can attempt to answer it now. Otherwise, we can certainly reach out to you with a better answer in writing after the webinar.
Our next question is is this webcast available afterwards? The answer is yes. It will be available via the MobileIron home page in the resources section. In the library there will be a webinar link.
You'll also get links to that information and a replay mailed to you as a follow‑up to the event.
Fran: Back to the question about Access, and Sentry, and difference. I'll follow up with a more detailed answer. The idea is that the per‑app VPN...AnyConnect, as Paul pointed out, it works on a couple of different levels from a VPN point of view.
Tunnel, Access, and Sentry ‑‑ they do different things, is the point. There is one capability that they share and that's that they can end the per‑app VPN tunnel. Paul can talk to that.
Access delivers all other sorts of other single [indecipherable 45:10] capability. We use our own identity and other identity to do that. We can complete a tunnel or not.
I think we're different products and robust in different ways and we share come common piece in terms of the per‑app VPN capability.
Cynthia: Great. Thanks, Fran. Finally, we have a question from Chris, who says, "Regarding per‑app. if I want to tunnel Facebook, can it tunnel the app and browser based access or only the app?"
Paul responded saying that the per‑app would only control the Facebook app. If you want to push browser traffic such as traffic destined for Facebook, you would not allow split tunneling and all traffic would need to traverse the tunnel.
It looks like we've answered all of our questions. Last call for questions. If you've got anything, please type it into the Q&A window.
Otherwise, I definitely want to thank everyone for attending. I want to thank our colleagues from Cisco for the great content that they brought to this. As we said, please reach out to us at email@example.com. We'd love to have a dialogue with you.
With that, it looks like we've answered all our questions. We will wrap our webinar. Thank you so much for attending.