Most IAM tools utilize browser extensions or applications installed on the end-user’s machine, or on an Active Directory, for access to identity. But why?! A user can be identified even without an agent – so having an so-called ‘lightweight agent’ sitting in your Active Directory itself is not the most secure way to manage user identity.

Whenever you create a dependency to achieve a particular solution, it is important to ensure the solution is 100% secure and that applies for the dependencies (Agents) too. This could make the architecture slightly complicated, depending on how it works.

Another important factor against the use of an Agent-based architecture is that  you have to trust the Agent not to exceed its scope. This is very important because even many of the applications and services that we trust these days are not actually secure, and many act beyond their scope. For example, as per Digital Content Next, even the big boy of the tech industry, Google, still collects user location information even after turning off location settings.

So the big question is, when the things can be done without an agent, then why use an agent at all? People say it is for efficiency, and may be they are right. But is this worth the compromise on transparency and security?

Dinesh Harikrishnan

Dinesh is Senior Vice President – Pre-Sales at Akku, where he plays a pivotal role as Product Owner for the Akku platform. Having been part of the product journey from its earliest stages, he has shaped its roadmap, overseen its development, and worked closely with clients to ensure successful implementations. His focus lies in consulting with organizations on their cloud transformation journeys, designing solutions that balance security, compliance, and usability. Over his career, Dinesh has grown through roles in development, consulting, customer success, and pre-sales, giving him a 360-degree view of technology delivery and client engagement. His work has spanned industries from manufacturing and automobiles to edtech, consistently delivering value through innovative solutions and lasting client partnerships.

Recent Posts

Building a Defensible Audit Evidence Package for Regulators | Akku

Introduction Every compliance audit, regardless of framework, arrives at the same point: the auditor requests evidence that specific controls operated…

3 days ago

DPDPA Data Principal Rights: What the Technical Infrastructure Behind Each Right Requires

Introduction DPDPA Chapters II and III establish six rights for Data Principals. Each right creates a corresponding technical obligation for…

4 days ago

GDPR Article 25: Data Protection by Design and IAM | Akku

Introduction GDPR Article 25 requires that data protection be built into system architecture by design and that data minimisation be…

2 weeks ago

ISO 27001 A.8.15: User Activity Logs and Authentication Logs Are Not the Same Control

Introduction ISO 27001:2022 Annex A.8.15 requires that logs recording user activities, exceptions, faults, and security events be produced, kept, and…

2 weeks ago

How to Build an Audit Evidence Package That Survives Regulatory Scrutiny

Introduction Every compliance audit, regardless of framework, arrives at the same point: the auditor requests evidence that specific controls operated…

2 weeks ago

SOC 2 CC6: Logical Access Controls and What IAM Must Deliver

Introduction SOC 2 CC6 is the Logical and Physical Access Controls criterion cluster and is where the majority of IAM-relevant…

2 weeks ago