IAM overview

This is a work in progress, and many concepts have been simplified for the sake of conciseness, ease of access, and, to no small extent, for a lack of omniscience on my part.

IAM Infratructure

Plan a flexible IAM architecture as a means of facilitating Governance, Compliance, and Risk (GCR) management through the use of Governance as Code and Policies as Code, for real-time, explicitly evaluated, adaptive trust in a zero standing privileges and zero-trust architecture.

This document attempts to align requirements and perspectives of:

The Information Security team is often considered as part of Compliance and Risk Management and the Cyber Security team as part of Information Technology, but given their significant impact for an effective planning of projects built around IAM, they have been included in the list as separate entities.

The implementation of a proper IAM infrastructure requires the involvement of people from different teams and departments. Underestimating the need to involve all stakeholders at an early stage will lead to delays, waste of money and resources, and poor adoption.

The following is an incomplete list of candidate stakeholders:

Workforce IAM