Accounts & Access

Gone are the times where we can simply assign any permissions we need to get the work moving on with minimal disturbance and with minimal constant approval. Unfortunately, it has lead to a huge trending problem now that one has to monitor with a microscope to ensure ONLY the needed permissions are assigned in a granular manner. It's time to implement the Least Of Privilege Permissions and Segregation of Duties as a CyberSecurity Policy and not only as Security Controls/Best P

Service Accounts, the accounts that lack TLC since the day they are created rapidly to meet the requirements of a new implementation or for troubleshooting purpose. The next in line are Service Prinicipals which are heavily used in Cloud Environments (Azure/AWS/GCP). This is a manual task at the moment although there are several IAM Management Tools now to monitor them in an automated manner. Not only that, almost every company is now working on automating this manual proces

Now that we know what is a Privileged Account, we always got to ask ourselves these questions before we begin to work with any vendor or even to initiate a meeting with Head of Security/Security Manager/Security Lead/Security Director/CISO/CTO: Note: This is really a sensitive task/responsibility that one must be very careful and needs to pay important attention to it even in a discussion or a presentation about it. Why the need to protect Privileged Accounts? What is the nee

Funny isnt it, how these two words is simply driving everyone so cautious in everything they do and the dire need to now discover and monitor ALL Privileged Accounts? Well, it's time to do so actually and it's a commendable effort to trying to get it right or even the intiatiting process of it. Kudos to you! Alright, these is where the misunderstandings/confusion start to rise. Let's break it down and we will see how we go. Feel free to comment your thoughts away, it's pretty