PAM in Most Reasonable Price in India.
PAM in Most Reasonable Price in India.
CONTENTS
Executive Summary
As the world grows more and more networked with workloads getting automated through technology
transformations and the workplace becoming virtual, the need for securing data, governing accesses
and mitigating risks has increased multi-fold.
Enterprises stepping on the cloud paradigm to optimize on infra requirements, scale operations and
move their application workloads need to focus equally on the security of the data and the super user
credentials that also reside in cloud.
A plethora of point solutions have come up to address this growing need to managing and securing
super user credentials. From password vaults to traditional identity verification and Single Sign On
solutions, there are many offerings available that help manage the identity and accesses of privileged
users on cloud.
Fundamental to managing this challenge is to look for the use cases and map it to the solution that
meets these use cases better than other solutions.
There are few scenarios which loosely is referred to as a Cloud PAM solution.
This white paper explores these uses cases and how Iraje PAM can help manage,
monitor, control and discover, comply & secure your cloud environments better.
Privileged identities are users or accounts that hold elevated permission to access files, install and run
programs, and change configuration settings. They have access to operating systems, database
servers, user directories, network devices, and enterprise resource planning applications. Privileged
users could be system, database, or network administrators, support personnel and application
owners. These accounts allow unrestricted access to view and change data, alter configuration
settings, and run programs. Typically associated with hardware and software assets (and not with any
one user), privileged identities grant “super-user” access to virtually every resource on your network.
Privileged accounts are the most powerful accounts in the organisation because -
The following Risks have emerged due to the growth of privileged accounts
within organizations.
Organization Assets Account Types Actions that may go Flavours
untraced
Operating Systems: • Administrator Read, Copy, Alter data
Windows, Unix, Linux, • Root Change security settings
AIX, Sun Solaris, • Service Create and delete accounts
Mainframe • Super User Run programs
Enable & remove file shares
Databases: • Root Access transaction data
Oracle, MS-SQL, • Sys Switch on-off the logs
MySQL, DB2, Ingress, • Sysdba Edit-delete DB logs
Informix, Sybase • SA Modify DB records
• Ora Change DB configuration and
schema
Modify stored procedures
Database Tools: • System Access transaction data
Toad, MS SQL, PL/SQL, • Sys Edit-delete DB logs
OEM, SQL Developer, • SA Modify DB records
DB2, MongoDB, • Service Change DB configuration and
Postgres accounts schema
• App Owner Modify stored procedures
Additional business drivers can include the need to manage privilege account ids & passwords, get
audit trails of every activity and action performed by privileged users, file regulatory compliance,
manage completely outsourced environments effectively and get overall visibility and control of your
IT organization.
Password Management
• Critical passwords of Databases, OS & Routers are stored in text files and/or spreadsheets
• 30-60 day password change: Admins must manually change approx. 100*3=300 passwords
• ‘Admin’ passwords shared by all Administrators
Audit Trails
• No audit trail to the activities performed using tools like Toad, OEM, XManager, etc.
• Limited audit trail of Application administrator activities
• Limited audit trail of OS (Unix/Linux/Windows) access and activity
• Limited audit trail of access to databases
• Limited audit trail of access to all network devices
• Logs not available at one central location for all devices without being under the control of
administrators
Private Cloud
This model is similar to the traditional on-premise deployment model where resources use
virtualisation and resource management capabilities. This model does not bring the associated cost
savings or flexibility associated with the public cloud model. It does however, allow the end
user/organisation to control and customise the cloud to meet their specifications. As a result, this
restricts the scalability and flexibility of the offering yet ensures comfortable levels of security (data,
user information etc.) provided in-house security practices are set in place.
Public Cloud
This is the most common Cloud model that comes to mind when the discussion of Cloud comes up.
Public Cloud is a multi-tenant model, typically offered by a vendor such as Google Cloud, Microsoft
Azure, Oracle Cloud or Amazon Web Services.
This model deploys and runs an application fully in a public, off-premise Cloud. The main benefits
associated with this approach are lower software Total Cost of Ownership (TCO) and substantial
agility — access to pay-as-you-go, on-demand storage and compute power. Where data security is
not a top-level concern, applications are suited to this model.
Hybrid Cloud
Hybrid Cloud is a mixture of the two previous models described — they remain separate but are
linked together giving some flexibility when demand cannot be served solely in private Cloud.
Applications can be deployed in the private cloud while associated data stored on-premise.
This is due to concerns about data security and ownership. When usage spikes, access can be
connected to a Public Cloud to obtain more flexible compute power and storage access.
The main concerns with the Cloud are security and control. The level of sensitivity relating to the
data you are managing can mean that the benefits of lower TCO (associated with public cloud) is
sacrificed.
Private
Security
Hybrid
Public
When data sensitivity is low, then the public cloud can be considered but the level of control is
reduced as the Cloud vendor is responsible for configuration management.
Private
Hybrid
Control
Public
Scalability
Cloud Services
The Cloud allows you to deliver three different service types within your organisation. Each service
has a different function depending on the resources available and the flexibility desired.
Cloud Computing is growing at substantial rate and is definitely an option considered by
organisations when deciding how to manage their way of working.
Before embarking on your Privileged Access Management (PAM) cloud journey, it’s important to
understand the severity and criticality of the issue and how urgent it is to manage the same.
Example: If your answer is option a, put 1 in the first column, if your answer is option b. put 2. in the
second column, if option c. put 3 in the third column and so on.
Sr.
No. Lead in Questions Severity & Criticality
Less Very Very
Severe Severe severe Critical critical
1. How many privileged users do we have in the
organization accessing cloud?
a. < 10
b. >10 <25
c. >25<50
d. >50<100
e. >100
2. How many privileged accounts are there on
your systems? [admin, ora, sys, root etc]
a. < 100
b. >100 <250
c. >250<500
d. >500<1000
e. >1000
3. How many passwords are there across all
privileged accounts?
a. < 100
b. >100 <250
c. >250<500
d. >500<1000
e. >1000
4. Is your environment completely outsourced,
insourced or a mix?
a. Completely insourced
b. Mostly insourced
c. Mix of both
d. Mostly outsourced
e. Completely outsourced
5. How sensitive is your business data? Is your
data residing on infra hosted on cloud?
a. No breaches at all
Now add the answers. The scores will point to the severity and criticality of a PAM solution required
for the organization. Table below gives the severity and criticality scores at which organization needs
to take a decision on implementing PAM solution.
It is very likely that your scores are in the 20s, which means that though this threat is important it may
not be urgent to be acted on.
Alternatively, your scores may be in the 40s, which means the issue is not only critical but very urgent
as well, and needs to be address immediately.
In many organizations, there is no tracking around of who does what and what kind of account is being
used. Therefore, Privileged Access Management (PAM) is necessary to automate control over
administrative accounts, which typically put too much power in too many people's hands with too
little accountability. It helps to address the security, operational and compliance issues posed by the
widely shared administrative accounts and passwords, excessive administrative rights, poor
separation of duties, embedded passwords in legacy applications and scripts, and poor or non-existent
privileged-password rotation. It also provides individual accountability and an audit trail to prove that
policies and controls are actually being enforced.
With Infra and applications moving on cloud, the privileged passwords and public private keys used to
access these need to be governed and secured more effectively. Cloud environments do provide basic
security around identity and accesses but lack the more granular controls required to manage the
security around privileged user accounts in terms of session recording, smart audit trails, centralized
console to manage all accounts, discovery & control capabilities to meet audit and compliance
requirements.
The key drivers to PAM on Cloud are shown below. These key capabilities are important and a “must
have”, to ensure that the PAM is ready and capable of providing the integrations.
A PAM solution that provides these 16 core capabilities is fully ready to support the enterprises who
want to go for Cloud PAM – with either the infra being on-premise, infra being on cloud or a hybrid
option of infra and apps on cloud as well as on-prem.
As companies begin their journey towards cloud, they often begin by creating suites of SaaS
platforms. These applications enable them to streamline business operations but create more
access points that increase risk.
For example, as business leaders seek to streamline their ERP systems using SaaS applications,
their IT security departments struggle to maintain privacy and security across the ever-expanding
ecosystem. According to the Oracle’s 2018 report, “Securing SaaS at Scale,” the mobile workforce
redefines “perimeter” and legacy solutions cannot support the new cloud threat landscape.
The disconnect between SSO use and IGA tool use indicates that although organizations express
concern over compliance and security, they lack integrated tools that enable protection. SaaS
applications require privileged access to databases or other applications across the overarching IT
infrastructure. Their passwords, which often remain embedded and stored in unencrypted text
files, create a security vulnerability. As cybercriminals increasingly use stolen credentials to gain
unauthorized access to protected information, the passwords act as a point of entry. Even more
disconcerting, as the applications interact throughout the cloud ecosystem and across multiple
servers, this vulnerability exponentially impacts the whole organization.
IaaS applications interact across an organization’s ecosystem, often requiring privileged access to
systems to interact with operating systems. These service accounts may have domain
administrative privileges that require additional security controls and monitoring to ensure
privacy and security.
While PaaS services bring together SaaS and IaaS enablements, they also create new challenges.
Specific to PaaS, the journal article “MPSM: Multi-prospective PaaS Security Model” explains the
unique data and infrastructure risks inherent in PaaS ecosystems:
Data location: duplication of information in multiple locations that remain on the service
provider’s network
Information leakage: shared communication channels and resources can lead to “shadow IT”
sharing similar to within an IaaS ecosystem
Privileged Access: “built-in” debug feature grant privileged access to memory and data
locations
Distributed system: open default ports decrease visibility into how and where data can be
accessed
Vulnerable hosts: Multiple accounts (multi-tenancy) in PaaS ecosystem allows user objects to
connect which leads to visibility issues that lead to infiltration
PaaS services lead to privileged access risk as they incorporate domain service accounts and
require coordination across multiple systems. Within the PaaS environment, administrators need
to apply access on a more detailed level. Traditional IGA services and privileged access
management providers lack the ability to create fine-grained entitlements, such as limiting access
at the file and folder levels. Coarse-grained entitlements, such as application level access, fail to
secure privileged access in the cloud.
Securing identity and proving governance over access and use becomes challenging as the
enterprise adds more human and digital users to its cloud. Once the enterprise ensures that the
cloud environment is secure, it must also find an Identity Governance and Administration (IGA)
solution to enable authentication, authorization, and traceability.
1. PAM on Cloud: This is where customer infra is on cloud and PAM is also on cloud as part of
the infra
2. Infra on cloud, PAM on Prem: This is a scenario where customer has moved majority of their
infra on cloud but want PAM in their premises to manage the infra
3. Hybrid environment, PAM on Prem: This is a case where infra is on prem as well on cloud and
PAM is on prem
PAM on Cloud:
• Agents for Windows devices for alerting • Not available in some solutions
unauthorized access bypassing PAM including
advanced remote access alerts
• SSH Tunnelling support • Not available in some solutions
• Supports all types of cloud environments and • Limited support for devices on cloud
devices on cloud.
Bottom Line
The threat of un-managed privileged identities is very high and it can cost the organization very
heavily in case of data breaches. The insider threat is dangerous as well since it goes on without
being traced easily.
Addressing the threats from insiders is always a sensitive area to handle. While companies will
always want to hire trustworthy employees, it is an irrefutable fact that accidental breaches occur
very regularly, and that a single, well-motivated malicious insider with privilege accesses can cause
immense damage.
IT auditors are also realizing the potential of threats posed by unmanaged privileged identities in
your organization. There is an ever-increasing pressure to bring these powerful logins under control.
Fortunately, Privileged Access Management software can help organizations secure privileged
credentials throughout your network and provide an authoritative/forensic audit trail of their access.