What is your primary use case for Cisco ISE (Identity Services Engine)?

I use Cisco Identity Services Engine (ISE) for wireless authentication and device administration.

We used it mainly for network access control and full stream for devices.

We use the solution for network access control.

The solution is being used for authentication purposes and for sharing assessments.

I do the designing and implementation and hand it over to the customer. Sometimes, I provide support to the customer. The solution is used for network access control. I have implemented almost all the features of the product.

We use the solution to secure the endpoint. Before the user connects to the network, it can be investigated whether to connect.

We primarily use the solution for network access control solution and network device access management. The solution comes with features like posturing.

I am a Senior Technical Consultant. I have worked in professional services as a Cisco Gold partner for the last ten years. I have been offering Cisco ISE for the last three to four years. We do small deployments, upgrades, and those types of things. We see a lot of customers wanting to use Cisco ISE primarily for 802.1X wired and wireless and also for posture device administration, and guest access. A lot of our customers who come to us do not have any sort of NAC solution in place at all. They don't have a RADIUS, they might have a Soft MPS or something along those lines, but Cisco ISE is far superior. It gives them far more visibility and the policies are more configurable. The ability to do dynamic access lists, dynamic VLAN environments, and that type of thing, and it just gives them a different level of security altogether.

I'm a network engineer. I've been at my company for about six years. We have about ten people on the networking team. We support up to 30,000 students. We've been using ISE for five or six years now. Our primary use case is mainly to onboard students with the wireless authentication with our switches and network devices.

Right now we use Wireless.1X and TACACS for device management. It's in our wired network too, but only use it for MAC address bypass.

The company's use case for Cisco ISE is switch access. I'm from the high-performance compute side. I'm not the back office IT. I'm what they call GSIT. Their use cases are different but very similar.

We utilize Cisco ISE for wireless user authentication, as well as authentication, authorization, and accounting for our network devices.

We utilize Cisco ISE for authentication by employing the AnyConnect Posture model to address vulnerabilities on the workstations. Additionally, we make use of TACACS.

I utilize Cisco ISE to access the switches on our network for monitoring configurations.

We mainly use it for endpoint security.

We use the product for TACACS, dot1x, authentication for some of our RADIUS devices, and authentication and authorization for our VPN clients.

There's a variety of customer uses for Cisco ISE, which includes securing the edge of the network.

We use it for Cisco device TACACS authentication and .1X security.

We use it for NAC and wireless, and for our TrustSec policy. These are the three primary use cases we have so far.

We mainly use Cisco ISE for device authentication. We are now rolling out 802.1X.

I use Cisco ISE for VPN and authentication.

Cisco ISE is on the back end, and all our policies and security are on it. DNS centers and all our network backbone is integrated into Cisco ISE. So, the solution is pretty critical for us.

We are on-prem at twelve separate sites with one main node. We utilize Cisco ISE for authenticating both our employees and residents at our senior care center. We authenticate them either against LDAP or our network.

I often use Cisco ISE for guest portals to onboard devices. For example, if a company wants to allow their employees to bring their own devices, there's a large security risk. Cisco ISE can help with onboarding those devices and check whether they're up-to-date with security patches and whether they fit the criteria to join the network. There's so much stress involved with the pressures of trying to make it easy for customers to use the product without constantly having to jump over security hurdles. On the other hand, there is the constant threat of cyber attacks. Balancing the two can be quite stressful for developers, engineers, and consultants. Our main goal, as an intermediary between Cisco and our clients, is to help IT managers, IT engineers, and administrators have better days. There is a lot of pressure on IT staff, and by giving them the right tools and solutions, we can help them feel more empowered to do their job much more effectively and, therefore, feel proud of their work.

Today, we are performing wireless client authentication and using it as a captive portal for our guest wireless network. Eventually, I am hoping to roll into 802.1X for the wire. In our organization, we have about 2,000 employees and 12,000 other end users whom we service.

We are using it mainly for .1X authentication, and we also authenticate our VPN users, and we are doing some light profiling and posture. We're trying to solve the problem where different users have different privileges in the network. And also we're trying to block some access from our least privileged users. Those are the main use cases for us. We have on-prem virtual appliances and a distributed model.

Our main use case right now is TACACS for device administration and authentication, as well as for user authentication on the network: wireless authentication, 802.1X, and wired authentication too, for RADIUS.

Our use case is managing access to network devices for IT as well as end-users. Making that seamless is the challenge we were looking to handle.

Cisco Identity Service Engine (ISE) is used mostly for endpoints. If you want to know the profiling and what endpoints are connecting to your company, then ISE is a good solution because it has built-in signatures. Therefore, it knows what kinds of devices are getting added into the network. You can install it with any cloud provider, e.g., AWS or Azure. You can install ISE locally. If your site is critical, like in manufacturing, you need to make sure that ISE is a part of the local site. Usually, people install data centers, but you can also install at critical sites.

The primary use cases include customer environments, BYOD, posture assessment, and dot1x for wireless and wired networks.

We use it as our complete NAC solution for both on the wire and wireless as well as guest wireless access and SGTs. We have five hospitals. We have two service policy nodes at every hospital. We have a deployment at every hospital site.

We use it for wired .1x, wireless authentication, VPN, and multi-factor authentication. We wanted to have a consistent experience for authentication and authorization of endpoints across the network, as well as security.

We were looking for secure network access.

It's mostly for authentication to our network for our end-users.

We use it for the TACACS authentication, for administrator login to network devices, and the RADIUS service for VPN and wireless authentication. Initially, we were looking for a single sign-on for administrators to log in to every network device, but we also wanted a good way to control remote user access for logging in. Later we started using it for VPN and wireless.

This solution provides access to the employees of the company.

I primarily use ISE for segregating identities, IP addresses, and ports.

We're using version 3.1, which is very stable. There have been a lot of improvements.

Our customers use Cisco ISE (Identity Services Engine) as a network access control solution. Before they can get network access, you can do posture check, e.g. in the Windows version, or another version, then it is only after this posture check that the clients can enter the network.

The solution is used for controlled access in the network, like if you want to restrict access. The solution is deployed on-prem. I am an integrator of this solution.

My primary use case is network address translation and layer 4 filtering.

We use Cisco ISE for authentication for VPN and network management.

The solution is primarily used for Network management and Network Access Controls.

We are using Cisco ISE for limiting port access in our organization's building for wired and wireless networks.

We use Cisco ISE for device authentication, such as auto switches, and wireless authentication.

We are resellers. We provide and deploy solutions for our customers. Cisco ISE (Identity Services Engine) helps the operation to automate.

I am a reseller. I provide solutions to our customers. We used Cisco ISE for Wi-Fi implementation for one project at the International Airport.

The solution is primarily used for authentification purposes.

My clients are small to enterprise-size companies using this networking solution. One of my clients is a leading pharmaceutical manufacturing company, providing genetic medicine. The network they have has approximately 5,000 device inventory. Additionally, I have a couple of clients in the banking industry in the USA that has quite a large networking infrastructure using this solution.

This solution ties into our Cisco Duo and Cisco AnyConnect connections to help us authenticate against the active directory and Cisco Duo multifactor authentication. It takes metrics about the connections that are connecting it and allows us to set up a rule against them. For instance, if a Windows device is not all the way up to date, we can put a message up that says, "Before you're able to connect, please do your Windows updates as they haven't been done in six months." As this solution allows AnyConnect to authenticate with the active directory in the backend, the users won't directly use it. Still, it will be in use throughout the login process into Cisco AnyConnect as a source of authentication. With this solution, we don't require anyone for maintenance.

Our use cases are based around dot1x. Basically wired and wireless authentication, authorization, and accounting. In terms of administration, only our networking team uses this solution. Probably five to ten administrators manage the whole product. Their role pretty much is to make sure that we configure the use cases that we use ISE for — pretty much for authenticating users to the wired and wireless networks. We might have certain other advanced use cases depending on certain other business requirements, but their job is pretty much to make sure all the use cases work. If there are issues, if users are complaining, they log into ISE to troubleshoot those issues and have a look at the logs. They basically expand ISE to the rest of the network. There is ongoing activity there as well. The usage is administrative in nature, making sure the configurations are okay, deploying new use cases, and troubleshooting issues.

We use ISE for security group tagging in terms of guests and visitors who access the network to make sure that they actually go through this to control their privilege access to ensure they don't actually access the internal network, etc. Our clients use ISE as a form of security policy management so that users and devices between the wired, wireless, and VPN connections to the corporate network, can be managed accordingly. Take a house for example. Sometimes you need to access a room via a certain keyhole, so you use a key that is unique to that door. With ISE, you can segment this process in terms of policy management based on the security tag. You actually grant the user access based on the tagging. That's the IT trend — saving a lot on operating costs to manage the different users and access methods. Within our company, we have roughly 200 employees using this solution.

The primary use case is to have network access control and automation to integrate with the enterprise network. It also helps provide a method to make segmentations between users and enable access control.

We primarily use the solution for user authentication and wireless segmentation of users for actual radius purposes.

Mainly the use case of the solution is for ensuring that the corporate staff gets access to their authorized systems. Another use case is for contractors to get access to the authorized systems. Those are the ones that hope to assist in the maintenance or for authorized admissions to the network. We do also use it for remote access, for example, VPN's and also for wired and wireless access to the network.

We are a solution provider and we provide Cisco products, including ISE, to our customers. This product is used to facilitate the connection of a local network to wireless access. This allows us to restrict users and their access.

The company implemented the solution to keep track of wired and wireless devices.

One of the use cases was the certificate-based authentication for the endpoints. All the laptops and mobiles are embedded with certificates and once they get authenticated, then only they would be able to connect to the LAN. The other use case was the NAC use case wherein the integrity of the laptops and mobile and such were checked before the scan. They fulfill the policy requirements and then they are able to connect to the network. The third use case was the consolidated access control management for all the network devices and security devices.

We are a system integrator and Cisco ISE is one of the products that we sell and implement at our customers side. I have built ISE's POC and provided training to our customers. I also used real rent lab which was including; Active Directory integration, network access and core switches, access points, wireless access controller, and end points. (some end points have cisco client - anyconnect, and have not), and Web Server for creating wireless authentication portal solution end to end The AAA features were awesome and have important attributes, and also the security groups (SGTs) concept to enforce policies for each group of users, regardless they coming via wired or wireless network devices. also i see the guest authentication is very rich and easy tom implement

We have two servers and they're both VMs. Every network system is issued a certificate and each device coming onto the network has to be on the domain with an active AD user logging into it. It needs an up-to-date AMP, which is our Cisco malware and virus scan product and it also needs to have the most current Microsoft security updates and the three layers that we're using: The core VPN, the Network Access Manager and the ISE profiler. When it goes through all those different things on every port on the switch, there are commands for it to be able to go through an ACL so it knows what users are there, what server, and what devices have been put onto the domain. It can verify all that. The user can then proceed on to the network. We've set it so that regular users are VLAN'd off and can only see the data network through ISE and are blocked from seeing the rest of the network. Depending on the department needs or other factors, we have cameras for security which are on a different VLAN, and they can see those. We also have something for O&M where the AC guy can see the AC equipment, and we can prevent all the VLAN's from being viewed by everybody. We are customers of Cisco and I'm the infrastructure and Cyber security manager.

We use Cisco ISE for 802.1 network authentication.

We use this solution to provide wireless for our residence halls and guest networks. We're also a college that works primarily off of iPads, so we have to be able to keep resident hall activity off of the network so that students can do their homework and class activities. We use the Services Engine to authorize all of them.

We primarily use the solution for network admission control.

We use this solution to monitor and secure devices on our network.

We use Cisco ISE for network management, user access for enterprise clients, and advanced firewall support. We use Cisco ISE on domains and clients jointly with other network software utilities.

Our primary use case is to grant access to users, we deploy the bring your own device policy.

We are a reseller of Cisco ISE.

We use this solution to protect the network especially when someone brings their own device and to lock out access to anybody connecting to the network. Also to make sure that the people connect to the correct VLAN. So, mainly for security wifi access so that when people want to connect to our wifi they have to log in using their credentials.

Our company doesn't use Cisco ISE internally. We act as the solution reseller. Our business model is set up to provide a network-based approach for adaptable, trusted access to our clients. We provide our clients with intelligent, integrated protection through intent-based policy and compliance solutions.

It's a network access manager.

My primary use case for this solution is as a server for my networking devices.

We use this solution to authenticate the domain users and if someone is not the domain user to make them a guest.

We use it to aid the tools that we make and to sponsor and get flow.

My primary use case of this solution is for access control for authentication and for the authorization of wireless users.

My primary use case of this solution is to protect the website from web attacks.