What is your primary use case for Cisco Secure Access?

Cisco Secure Access serves as a replacement for customers' old VPN solutions while increasing security through Zero Trust Network Access (ZTNA). We had a chicken production client that identified their current VPN as the lowest hanging fruit for increasing security. Since the customer already had Secure Client or AnyConnect previously, introducing the ZTNA module into Cisco Secure Client felt quite straightforward. We implemented it step-by-step, side-by-side, and rolled it out for that customer, which improved secure access for both on-premises and cloud solutions and turned out to be very effective.

Cisco Secure Access is used for CTNA with a couple of applications deployed on it. There is a journey underway to move all applications off VPN into CTNA, but some applications are too old and legacy and will not support it very well. Business input into testing is required, and everyone is busy with everything, making it quite difficult. The VPN is working wonderfully.

My main use case for Cisco Secure Access is to secure our network. A specific example of how I'm using Cisco Secure Access to secure my network is that we use it for our customers as an internet service provider to ensure everything is safe.

My main use case is Zero Trust because we're moving to a full SASE platform and Cisco Secure Access was our first step.

We installed Cisco Secure Access for customers rather than our company since we're a reseller. Cisco Secure Access is not installed for VPN as a service; the customer using the VPN side is using it for access into the core network, so it functions as a landing point and an on-ramp into the core.

Our company's use case is exclusively for VPN, specifically for remote users at this time. We are exploring what other possibilities or functions are available, such as ZTNA and other features, but we have not reached that point yet. The only business case that stacks up currently is the replacement of a legacy VPN with Cisco Secure Access. We are looking to explore further functionalities that come with it. Using Cisco Secure Access for VPN as a service is key, especially with hybrid working where many users are home-based or traveling around the world. It is crucial that we get the VPN up and running consistently, especially if people need access to secure resources. Based on our use case, I think it has been really good to see the statistics and the number of users connecting daily, and we receive great data from it. There are many more things we can do, such as integration with ThousandEyes and Cisco ISE, but we have not done that yet. For now, we only use the basic functionality, which is a VPN as a SaaS service, but we are looking to expand to zero trust network access and various other features available.

Our main use cases for Cisco Secure Access focus on information security direction in companies like banks, and we are implementing it in on-premise or cloud systems while integrating it into third-party vendors, particularly with information security teams.

I use Cisco Secure Access as a VPN service. Cisco Secure Access provides not just securing and filtering capability on the traffic, but also a cloud VPN capability. This basically relieves the company from using the traditional perimeter firewall to connect via VPN. VPN connectivity through the cloud is incredibly flexible and is not constrained by the power of the firewall the company has, because the VPN is through the cloud. This allows companies to provide VPN capability to any remote user on a very short notice and not be limited by their firewall. I use ZTNA with Cisco Secure Access, which is another very clever capability that Cisco Secure Access has grouped along with several other interesting capabilities in one product. I always recommend and suggest to customers to try a proof of value or proof of concept of the product, which is very easy to do. Cisco allows any customer, literally for free, to test the product by themselves and test, for example, ZTNA capability. Customers can see for themselves with a proof of value how easy it is to install the product and how quickly it can be delivered in production. I use it with my clients both client-based and clientless with Cisco Secure Access. There are requirements for customers to allow connectivity to subcontractors who cannot install a client on the endpoints. Cisco Secure Access is a crucial solution in these situations because it can protect both employees and subcontractors, or any situation where a client is not feasible to install on the endpoint, while still allowing the same kind of level of protection. Cisco Secure Access has helped my clients transition from Zero Trust and least privilege principles. It provides protection even with technology such as MFA installed. It provides that seamless, transparent experience for a user that can use an agent installed. Cisco Secure Access covers a different spectrum of situations where the customer needs to protect remote access. There is also a flavor of Cisco Secure Access specific for IoT, which allows recording of the session. This is crucial for contractors when they need to access facilities offshore. This is a classic example of remote access where we cannot install any agent for the subcontractor, but we can record the session for whatever they do.

My company's use case for Cisco Secure Access is for teleworkers in general and for third parties.

We operate in the financial industry, specifically banking, where security is a primary concern when it comes to financial transactions. Our use case always prioritizes security requirements specific to the financial industry.

The main use cases for Cisco Secure Access are placing the product and attempting to place the product for the customer. People who do not have an SSE solution and do not know what it is need to be educated about it. I have to explain what it is and what the advantages are. There are two situations: people who do not know that they need it already and people who really need it and do not know which product to choose. Therefore, I guide them to a Cisco product. The first targets for Cisco Secure Access are organizations with remote customers who are working from different places. They have many on-premises apps and many SaaS apps. The benefits are that people just need to connect and they have their whole environment available for everybody. It feels the same as if they were in the office, plus they are safe against malware.

Our main use case for Cisco Secure Access is remote access to the company.

I use Cisco Secure Access for VPN resources in my day-to-day work to implement the VPN tunnel to the data center.

Cisco Secure Access serves as our main remote access tool for all of our users, which number about two and a half thousand endpoints. Our primary use case involves deploying Cisco Secure Access across all clients for connectivity, as we are a very remote organization, mainly in the UK, with many people accessing from three main sites, including working from home. Additionally, it supports all of our internet connectivity from our offices, and all of our laptops have the remote agent, so it is essential for that as well. We have implemented the ZTNA in Cisco Secure Access. We have adopted both client-based and clientless options within Cisco Secure Access. We currently have about five or six services on a clientless basis, which aligns with what Cisco recommends, and we are working to put more behind that. The client side consists mainly of some legacy private applications that remain on-premises that we have not yet migrated to clientless.

My use case for Cisco Secure Access is to replace our on-premises, not site-to-site, remote access SSL VPN as we are going from on-premises to cloud service. The second use case is to replace our Umbrella service, as we currently use Umbrella and will migrate to Cisco Secure Access as well, along with all the policies.

My adventure with Cisco Secure Access started when I began my work, and my main use cases are focused on ensuring secure connectivity and protecting sensitive data.

We are about to start up with Cisco Secure Access now. We started this last year, but we have a lot of Umbrella that we are moving over to Cisco Secure Access. The main use cases for Cisco Secure Access are mostly the internet, but we are also looking for the client part, including ZTNA and so on, to move over that part from the traditional SSL VPNs.

My main use case for Cisco Secure Access is providing access to private resources. For example, we have outstaff or any external partners, and we don't want to provide them wide access to our network. Cisco Secure Access provides us the opportunity to give access granularly, exactly for the resources that are needed for our partners, outstaff, and so on. It's one of the scenarios, and of course, besides ZTNA, we use internet access, which provides us the opportunity to control users through a web proxy and apply some policies to control them. Regarding whether the deployment of Cisco Secure Access has impacted the help desk ticket volume and the end-user experience, I believe it has improved significantly. For example, we have two separate infrastructures; it is a hybrid one. In Ukraine, we have infrastructure in local data centers, and in Europe, we have it in the cloud with Google. To have access to private resources, we needed two different profiles of VPN. Using Cisco Secure Access and building IPsec tunnels between Cisco ASA and Cisco Secure Access, we can combine these two separate infrastructures and use only one account to access resources in Ukraine, in local data centers, and in Europe.

Our main use case for Cisco Secure Access is that we need a new way for our remote workers to work. We were working with VDI and remote desktop solutions, but these do not scale out for real-time traffic such as Webex.

As of today, my main use cases for Cisco Secure Access are VPN solutions, and I'm looking forward to having more SASE solutions. Indeed, I would say that since the VPN solutions that we have delivered and that our customers are consuming today are not that flexible, if we can transform them to SASE solutions instead, we could make more policy-based access and level up the security. Since we are a partner to Cisco and we are working in the business-to-business with our customers, they rely on us to be a trusted advisor and a solution partner that can deliver secure solutions for their needs, and secure access is very much a part of securing their environments. I do not use VPN in Cisco Secure Access yet. In some customer solutions, we have done ZTNA, and we are very eager to get more of these SASE solutions in this ZTNA.

Cisco Secure Access is used for remote access VPN, supporting approximately 6,000 users in my organization. Daily usage ranges from about 3,000 to 4,000 users actually utilizing the solution.

My team's use case for Cisco Secure Access is that we currently have, or just had, a system with VDI connections, and it was quite difficult to handle because this VDI session is not optimized for video and telephony, especially Webex meetings. We are now glad to have the opportunity to move to the SSE environment.

The use case depends upon the vertical, such as manufacturing or enterprise. Mostly customers are looking for secure remote access to their applications. They may have a vendor ecosystem where they do not want to install any client. If they are looking for a clientless VPN like ZTNA, Zero Trust Network Access, that is where it fits. Mostly they want to move away from the centralized filtering point of view, even if it is a proxy. They want to facilitate access wherever they are geographically distributed. Because Cisco Secure Access PoP is there everywhere in major regions, this helps. If they have a use case of a user sitting in an office and a user sitting remote, and a vendor accessing their applications from outside their network, you cannot expect anything installed in the vendor laptop, which is a non-domain laptop. That time, you need to have a solution that supports secure access of that application for that vendor who is sitting outside the network and is not a domain user. Private application access is definitely there with the resource connectors. The concept of resource connectors is there to ensure the backend traffic from the application to the user. I have use cases, but I mainly worked on SaaS web traffic where I position SSE. Internal traffic is there, but not much discussion. It is hybrid only. There are customers who are adopting data center and coming out from cloud to data center, and vice versa. Definitely it will be Hybrid Remote Access.

I use Cisco Secure Access for Secure Access Service Edge (SASE), which provides me with secure identity-based access to applications and the internet from anywhere. I don't have to rely on traditional VPN architectures. Cisco Secure Access provides Zero Trust Network Access (ZTNA), Secure Web Gateway, Cloud Security Broker, and Firewall as a Service all into one platform, which is beneficial. I use it for firewalling, security, and Zero Trust Network Access.

I use Cisco Secure Access for Secure Access Service Edge (SASE), which provides me with secure identity-based access to applications and the internet from anywhere. I don't have to rely on traditional VPN architectures. Cisco Secure Access provides Zero Trust Network Access (ZTNA), Secure Web Gateway, Cloud Security Broker, and Firewall as a Service all into one platform, which is beneficial. I use it for firewalling, security, and Zero Trust Network Access.

Cisco Secure Access is used as a security tool within the tenant as a firewall and serves as a cloud-delivered Zero Trust access platform. It is used for Microsoft Intune as conditional access, Global Secure Access, and from Defender for Cloud Apps, working behind before it.Cisco Secure Access provides application-level access. Usually, it's full network access, but with this tool, application-level access can be given. It removes the dependency of VPN, and then user authentications are continuously based on identity, device, and risk, which is an add-on there. The Zero Trust Network Access feature is being used.

I support the US government. From a customer perspective, the use cases tend to be where we are guarding edge devices that we don't have necessarily 100% positive command and control. The devices have data transport that traverses in some cases ISPs, so we can't really control who's adjacent to those networks. We often deploy in those types of environments. Where we can use dark fiber, we prefer to, but that's not always an option.

Our main use cases for Cisco Secure Access are security and managing access.

Our main use cases for Cisco Secure Access include everything, such as all of our switching and wireless. I mostly work on the level one switching side. I deal with all the Catalyst 9300 switches and 9280 wireless routers.

The main use cases for Cisco Secure Access involve secure access to the network, as they've had some history with malware, ransomware, and things like that. They are focused on better control for remote users and access to the network.

Our business is in energy. We are using it to provide protection for different remote energy sites and for all the data that we transfer from the solar, wind, and hydrocarbon sites.

Our primary use case for Cisco Secure Access ( /products/cisco-secure-access-reviews ) is seamless connectivity for users, whether they are inside our corporate network or accessing it externally over the internet. The users do not have to switch on VPNs and reconnect. They can directly connect to Cisco Secure Access ( /products/cisco-secure-access-reviews ) using Zero Trust Network Access ( /categories/ztna ) (ZTNA ( /categories/ztna )) and access all resources as if they are inside the corporate network.

I use this solution for securing security controls like Secure Security Control (SSC) for local Internet breakouts. It offers a unified security policy across Google sites, providing secure web gateways, DNS and web security filtering, and multi-malware protection. These features are essential for comprehensive security.

We use the solution for authentications and accounting services.