What is your primary use case for Delinea Secret Server?

I need to look at using their tool's true multi-tenancy capability to cater to multiple customers within a single platform architecture without compromising security. Information security is key, and an MSP model's objective is to have a privileged access management solution. Secret Server is called a secret server for a reason. You can create multiple secret servers underneath the parent for every secret server. Every "parent" will be considered as one customer, secret server #1, secret server #2, etc. Under every secret server, you can create multiple secret servers. Those secrets will belong to customers A, B, and C, respectively. If I want to access a customer's Windows environment under a secret server, I will create a secret group called "Windows." This group will be onboarded with customer A's Windows environments within their secret server. We have a logically separated environment as an MSP model.

I use it for laboratory practice before implementing it for end-users. Specifically, I use the Linux server to discover related accounts in our domain, pull them into the solution, manage their passwords, carry out session monitoring, and practice workflow, which allows for leading access to better-trained individuals when needed. I also make presentations to clients concerning this type of solution.

We use Delinea Secret Server for pharmacy equipment management. We use a secret vault. We use it as a temporary hold, and we use it for password rotation.

We primarily use the solution for privileged access management. Delinea Secret Server is like a vault for the users to store their device passwords and is also used for auditing sessions monitoring password production, et cetera.

We use Delinea Secret Server for password rotations for end-point access.

Our clients use this solution to manage privileged accounts, meaning their administrative accounts. Whether it's active directories, co-banking solutions, or databases, the solution will take over all the privileged accounts on the network or in the infrastructure.

I use Delinea Secret Server for demonstration purposes while talking to clients, for internet access management, and user monitoring.

The primary use case for Delinea Secret Server is to sort the privileged passwords. It can also change passwords after a set period or revoke passwords when someone leaves the company. Delinea needs to be on-premises because Turkish regulations do not allow cloud-based security solutions for some sectors.

We provide Thycotic Secret Server as well as use it. Thycotic Secret Server is used for data security.

We intend to replace our pairing password management solution with something more enterprise-friendly. We are currently conducting a demonstration with Thycotic Secret Server. I've only used this solution a few times as a demo and haven't explored everything it has to offer, but I have experience integrating it with our Active Directory and setting up the server.

We have used Thycotic Secret Server for some secret management and integrated it with some applications. We mainly used it for Privileged Account Discovery and the management of them.

We are a Thycotic partner. We use Thycotic extensively, and we also do a lot of implementations for them. Generally, it is for privilege access management and session recording capabilities. A few clients have used it as a proxy capability, and the functionality there is that the privileged accounts have access from their workstations to the servers. In order to get access, they have to be basically proxied through Thycotic for an SSH or RDP connection, and then you have a control capability for auditing and session recording. We have used pretty much every version since 2018, including the latest version. We have deployed it to AWS and on-prem.

We use the solution to store all of our secrets. For example, passwords, usernames, and other credentials. These credentials can be from many places, such as service accounts, bank accounts, and key pairs. It also has the functionality if, for example, a contractor requests to log into a specific server, they would use the Secret Server to log in to the server session that is monitored and he or she would be logging in without the actual real credentials. It is also on a rotating password system.

The most common use case will be just for keeping personal passwords. There are other things that we use if for, but that is the most common use case.

We primarily use this product for password cycling.

The primary use case is managing access for user groups and individuals in a very large environment.

I primarily use the solution for PRAM management, privileged access management, and other similar tasks as well. We submit credentials and replicate and post them directly behind the scenes. There's also some session monitoring and issue recording, etc. that we handle.

We are a system integrator and this is one of the solutions that we implement for our clients. It is used for privileged access management for networks, servers, applications, databases, and more.

I'm a director/engineer and we partnered with the company. Our primary use case was for a project that we followed from an administrator point of view, not the end-user point of view. My responsibility was to manage the migration-related to the project, installing and configuring the infrastructure, creating policies and so on. Technically speaking, it was at a high level. All of my clients are enterprise companies.

This solution provides us with increased security when working with privileged accounts. It has well-arranged and detailed logging of privileged accounts. It offers the possibility of secure administration of hardware devices, as well as Linux systems administration from a Windows environment.

Our primary use case is for password management.

It's a password vault.

We use it for managing secrets and distributing them to our users.