Securden provides both on-premises and cloud-based (SaaS) deployment options to address a wide range of business requirements. Whether you prefer managing your infrastructure internally or choosing a cloud-based deployment, we are dedicated to delivering robust security, scalability, and seamless integration tailored to your requirements.
Both versions encompass a wide range of comprehensive features, including secure access management, detailed reporting, and flexible configurations. These capabilities help your organization to maintain control over sensitive data while simultaneously enhancing operational efficiency.
Install the product on a central server—physical or virtual, within your premises. The quick installation takes only minutes and requires no additional hardware or software. As a web-based solution, end-users can connect using any standard web browser, with no installations needed on their devices.
Deployment requirements for the on-premises version of Securden Unified PAM:
The product can be installed on any machine that runs Windows 7 and later versions, or Windows Server 2008 R2 and later versions. Each machine should be equipped with a minimum of 8 GB of RAM and 50 GB of hard disk space. By default, the product includes a bundled PostgreSQL database; however, users have the option to use MS SQL Server as an alternative backend database if desired. It supports web interfaces on various browsers, including Chrome, Firefox, Edge, Safari, and Internet Explorer 10 and above.
Securden also offers solutions hosted on a public cloud, allowing you to sign up and use the vault as a Software as a Service (SaaS) solution. Your data will be securely encrypted and stored in data centers located across Europe and the USA.
Deployment requirements for the SaaS / Cloud version of Securden Unified PAM:
There are no specific prerequisites for deploying Securden Unified PAM cloud edition. We will create a dedicated cloud instance, onto which you will be able to onboard and manage all your privileged access entities.
The features and functionalities remain identical for both deployment models, except for a few settings/configurations that differ in the SaaS version. You can find the differences between the on-premises and the SaaS version in the below table.
Securden PAM (On-premise)
Securden SaaS PAM (Cloud)
Set up by the customer
High availability is managed by Securden, through AWS
Set up by the customer
Database backups are stored by Securden in AWS.
Customer needs to carry out the upgrade process
Securden continuously updates the product for new features and bug fixes, these are automatically rolled out for the SaaS version.
Unified PAM helps scan distributed networks and identify all privileged systems and accounts within them.
Email Settings
Set up by the customer
Securden sends out the emails from the SaaS server.
Set up by the customer
Stored securely in KMS by Securden.
AD connectivity - To start managing privileges on AD domain computers, Securden needs to connect your AD domain.
The customer sets up direct connectivity to their AD using administrative credentials. No additional connector is required.
Since Securden SaaS PAM is hosted on cloud and cannot directly reach the AD domain running in your network, you need to deploy a lightweight remote connector on a device in your domain. Securden will connect to the AD domain through this lightweight remote connector.
Available in on-prem PAM
Not available in SaaS PAM yet
Windows Session Recorder app for Windows machines
Available in on-prem PAM
Not required in SaaS PAM, as SSM takes care of recording the sessions
SIEM Integration
Available in both on-prem PAM and SaaS PAM
Need to enable public access for SIEM server to connect over the internet to SaaS PAM
Ticketing Integration
Available in on-prem PAM and SaaS PAM
Need to enable public access for ticketing system server to connect over the internet to SaaS PAM
There are a few configuration options relating to the unavailable features that come under Admin >> Customization >> Configurations that may not be available in the SaaS version yet. These configurations in no way affect the functioning of the product’s vital functionalities.
If you have set up any of these configurations, they will not be carried over.