What is your primary use case for ARCON Privileged Access Management?

We mainly use ARCON Privileged Access Management for managing the storage account password. Additionally, we maintain user activity logs from the server end to end.

ARCON can be used to protect privileged entities by granting access via remote RDP, SSH, or recorded systems. Any activity on the server, endpoint, or network device is recorded for compliance. Traffic is routed through a gateway, which enhances security by not requiring many open ports. This provides secure connectivity between the end user and the servers. ARCON also has password vaulting features, so passwords are not shared with users. Additionally, ARCON allows for just-in-time access to privileged terminals when needed and has implemented approval levels for access to critical servers.

I use the solution in my company since the product is very good. In one of the use cases attached to the solution, I remember that an ID got locked after being unable to unlock the ID three or four times as per company policy. As per the organization's policy, if you try to run a password three or four times, it will get locked. No options are available in ARCON Privileged Access Management to unlock a locked ID.

During my training days, I used ARCON PAM as part of mandatory training. I even installed a version on my personal portal back then. Currently, I support a banking client who has implemented ARCON in their organization.

ARCON PAM offers two main access control use cases: dynamic and fixed. In the dynamic use case, users request access to services through the admin, who approves the request and grants access to a specific user account. In the fixed use case, generic users are validated, and the admin manages the password. Additionally, the admin can take a real-time session for any user accessing any service.

Privileged access management (PAM) is why we use ARCON Privileged Access Management.

We primarily use it for managing our team's devices, such as remote desktops and Linux switches.

Our primary use case is for using servers or accessing servers remotely, mostly for common users.

We are using ARCON Privileged Access Management for entire data centers.

This solution is used by system administrators that need to access critical servers. They need to log in using this product, and it then logs their activities.

Our company is involved in the health care sector and our primary use case of this solution is for compliance. Previously we used a system that included an Excel sheet but it would crash all the time because we have a large number of IT executives; tech related, application development and other administrators. We weren't able to receive the complete audit file that told us who was accessing and who was deleting what. It wasn't in compliance with data information security. For that reason we introduced the PAM solution and it's working extremely well. We're using it constantly on a daily basis. We are customers of ARCON and I'm a project manager.

We prefer not to talk about our use cases for security reasons.

* Multi-user, multi-OS, multi-database, and multi-hardware platforms * Cisco, Huawei, IBM, HP, Dell, etc. * Lots of networking equipment including F5 Networks.

We're using it for managing the access to our devices; privileged administrative access to the devices is handled through ARCON.

Primary use is to control Microsoft administrators.

We use it to access all the servers.

The primary use case is we want to control the access of the administrator. We have a lot of the administrators in our organization who have privileged access on the infrastructure, devices, servers, and network devices. We want to control this access, and at the same time, monitor this access. We use it to control privileged access of administrators on infrastructure and security devices, then monitor them from time to time.

The primary use of the solution is to give privileged access to critical resources, including monitoring and auditability.

We have a team of people who do the administration activity for servers and databases before our kiosk came into the picture. They used to share a common user ID along with the password among each other. Now, after our kiosks came in, they login into our kiosks with their old user ID, enter the ID, and the underlying connection is a common ID, but the password, they do not know.

We use it for privileged access management for our production environment. We use it to record all of the changes that take place in our entire environment. That is the main function because there is a lot of compliance that we need to meet. It helps us meet those requirements.