Most resources, such as databases or machines, are running in the cloud today and need privileged access.
As a result, controlling, monitoring and auditing privileged access has become even more critical for protecting against both external and internal threat vectors, human error and a growing list of compliance requirements.
The following are nine of the most important questions to ask a potential privileged access provider.
Granularity is key when it comes to privilege access governance.
If the organization has an integration between AWS and Okta, it is important that the solution grants the privileged access over that integration rather than creating a different way to get access.
Just-in-Time Access Management is important because it aligns access privileges with actual needs, reduces security risks, ensures compliance, and enhances operational efficiency in a rapidly evolving digital landscape.
It's important to make sure the solution has the capabilities to dynamically grant and revoke permissions to all the critical resources and services to which it governs access.
The solution should strive to offer robust and dynamic IFTTT scenarios, by leveraging context about on-call shifts, IdP groups, managers, work hours, and more to make sure Just-in-Time access is refined to the specific business use case.
To make it easy-to-use, it's imperative the solution integrates with your tech stack and doesn't require internal maintenance, for example by using home-grown solutions with automation tools, workflow builders, Slack bots and GitHub PRs. It should allow for quick, automated and simple ways to request and be granted access.
It's very important that the experience from the end user side is intuitive and simple, as a large part of access governance includes a human element.
To adopt a privileged access solution it must be intuitive, and it must integrate easily with the way users are already used to working.
A policy-based access governance solution that doesn't change the way end users work and allows them to seamlessly use any client they would like to access resources and services, like cloud resources or databases.
Users should have clear visibility of their request status in their platform of choice, understand why requests were approved or rejected and time- saving mechanisms for frequently needed access.
Automation is an important part of any access governance solution that offers self-serve capabilities or just-in-time permissions.
OnCall shift integration so that developers on-duty can request and be granted access as soon as possible if there's an incident, at any hour of the day.
Break-glass scenarios to allow different teams to gain sensitive access temporarily, for example for production maintenance, customer support, and more.
Automation based on Cloud/Kubernetes resource tags/labels, so that new resources can be automatically included in existing access workflows.
The user is able to seamlessly ask for and receive the access needed to do their jobs.
Approval escalation policies with multiple approvers to make sure requests are handled swiftly, and multiple approvers for very sensitive access.
To keep your resources secure, it's important to limit access to each one.
This Cyber News was published on securityboulevard.com. Publication date: Sun, 07 Jan 2024 15:13:05 +0000