Privileged Access

In today's cybersecurity landscape, organizations are increasingly recognizing the importance of implementing robust Privileged Access Management (PAM) programs. This recognition is primarily driven by regulatory requirements and the growing pressure from malicious actors. However, despite the availability of mature baseline capabilities for PAM products in the market, the implementation of privileged access often falls behind leading practices in typical organizations.

In this talk, we will explore the world of PAM design patterns and anti-patterns, with a specific focus on major use cases. We will explore typical patterns such as isolating accounts, systems, credentials, and networks. Additionally, we will discuss the various options available for defining privileged assets and access, as well as the potential for running Identity Governance and Administration (IGA) projects in parallel with PAM.

A fundamental aspect to consider is the concept of tier models and security domains. We will explore the role of different intermediaries, including Jump Hosts, Privileged Access Workstations (PAWs), and Agents, and their varying security properties.

Furthermore, we will address the often overlooked aspect of managing Secure Shell (SSH) keys within PAM. Lastly, we will touch upon the importance of having robust procedures in place to handle critical situations in emergency mode.

By understanding these PAM design patterns, organizations can assess their current practices and identify areas for improvement. This talk aims to provide valuable insights and practical guidance for organizations seeking to enhance their PAM programs and align with leading industry practices.

The principle of Least Privilege (PoLP) requires granting identities only the minimum permissions needed to perform their tasks. However, many technical and human factors make PoLP difficult to achieve.

In this talk, we will go through the various dimensions which need to be considered when we are implementing PoLP and what are the challenges in achieving it. While the obvious consideration for least privilege is the set of permissions, we show why factors such as grant timing and duration, and scaling across multiple cloud providers and SaaS applications are important as well.

We show how the lack of automation makes achieving PoLP inefficient, error-prone, and unscalable, and discuss strategies for continuous least privilege.

Finally, we show how to balance security and productivity to ensure widespread adoption of PoLP.