Identity and Access Management in the age of Bimodal IT

<span style=”font-weight: 400;”>An important new practice that has emerged over the past few years in IT management is Bimodal IT, defined by Gartner as the practice of managing two separate but coherent styles of work: one focused on predictability; the other on exploration.</span>

<span style=”font-weight: 400;”>While the application of the Bimodal concept within an enterprise has been the subject of much discussion, employing these two modes of management in the context of Identity and Access Management has not.</span>

<span style=”font-weight: 400;”>Here’s our take on how the Bimodal concept fits into our scheme of things as an Identity and Access Management solution provider.</span>
<h3><span style=”font-weight: 400;”>Mode 1</span></h3>
<span style=”font-weight: 400;”>By the standard definition of Bimodal IT, the focus of Mode 1 is on ensuring that existing applications and business functions are kept running smoothly. Therefore, Mode 1 clearly prioritizes stability over innovation.</span>

<span style=”font-weight: 400;”>In the context of IAM, businesses are becoming increasingly complex in the digital age, with touchpoints and interactions with increasingly large numbers of people or users, both within and outside the organization. </span>

<span style=”font-weight: 400;”>Managing this change requires IAMs to undertake a gradual evolution towards becoming simpler and more scalable. A good example of this would be the need to build in the ability to automate decision-making for setting access rules and permissions based on dynamically collected information on users, from multiple sources.</span>

<span style=”font-weight: 400;”>This evolutionary approach is important to ensure continued forward movement, embracing new practices and technologies, while continuing to place primary emphasis on seamless operations.</span>
<h3><span style=”font-weight: 400;”>Mode 2</span></h3>
<span style=”font-weight: 400;”>Mode 2 in Bimodal IT, on the other hand, places its focus squarely on innovation. In Mode 2, the priority is to undertake larger, but less certain, leaps forward, to enable the existence of entirely new business processes and approaches. </span>

<span style=”font-weight: 400;”>To look at the Identity and Access Management universe, in Mode 2, the mandate would be to build the next, future-ready new IAM platform. This could involve the development of an all-new, simpler and more scalable architecture from scratch, or incorporating increased agility to adapt to a fast evolving environment, for example.</span>

<span style=”font-weight: 400;”>Mode 2 involves planning and building for scenarios and use-cases that go beyond what conventional thinking can conceive of, to drive the next big change. But with this focus on innovation comes a need to accept some risk as well.</span>

<i><span style=”font-weight: 400;”>Akku is an enterprise IAM solution, and our journey to get here has involved adopting different facets of Bimodal IT. This process has helped us build a platform that delivers solutions to a range of use-cases that few others can match, and to do it reliably and seamlessly. Talk to us today to see how Akku could enable identity and access management, and more, at your organization.</span></i>

Yeswanth A

Yeswanth is an Associate Project Manager at Akku, where he leads Agile projects, oversees user story management, and ensures seamless delivery of enterprise technology solutions. Having transitioned from a software engineering role within the company, he brings a strong technical foundation to his project leadership responsibilities, enabling him to bridge development and business needs effectively. Before his work at Akku, Yeswanth served as a Java Software Engineer at Proagrica, where he contributed to the design and development of enterprise applications. His experience spans both development and project management, equipping him with a well-rounded perspective on technology delivery.

Recent Posts

Access Controls for Indian Banks. What Need-Based Access Requires Technically.

Introduction RBI 2023 Master Direction Clause 19 is the most technically detailed access control provision in the framework. It establishes…

4 days ago

SEBI CSCRF Access Controls: What PR.AA and DE.CM Require From Your Identity Stack

Introduction SEBI CSCRF's Protect function contains the Access Authentication sub-category PR.AA, which runs from PR.AA.S1 through PR.AA.S17 and represents the…

5 days ago

DPDPA Consent Management: What Explicit, Informed, and Withdrawable Looks Like Technically

Introduction DPDPA Clause 6 sets specific conditions for consent as a lawful basis for processing personal data. Consent must be…

1 week ago

Continuous Compliance Posture: Why Audit Readiness Requires Infrastructure, Not Preparation

Introduction Most IT teams at regulated organisations experience compliance audits as events. A notice arrives. A scramble begins. Access records…

1 week ago

IRDAI Item 14: Centralised Authentication as a Compliance Requirement

Introduction IRDAI ICS Annexure III Item 14 requires that all access to organisational systems be authenticated through a centralised authentication…

1 week ago

GDPR for Indian Companies: What EU Data Protection Law Requires From Your Technical Infrastructure

Indian companies with EU customers, EU operations, or EU-based employees are subject to the General Data Protection Regulation regardless of…

2 weeks ago