Non human identities section is valuable
We found dozens of long lived API keys after the inventory exercise. Now replacing them with workload identity.
Browse
Protect accounts and access across an organisation with single sign on, phishing resistant MFA, passkeys, conditional access and clean lifecycles
Created by Levan Kapanadze
Identity is the new perimeter. When employees work from anywhere and applications live in the cloud, the question "who is this, and should they have access?" decides most security outcomes. Attackers know it: stolen credentials, phished MFA codes and hijacked sessions are behind a large share of modern breaches.
IT administrators, security engineers and developers who integrate login into applications. Examples use common identity providers such as Microsoft Entra ID, Okta and Google Workspace in general terms, and the open source Keycloak for hands on labs, so you can practise without a paid tenant.
You will finish with a practical identity roadmap for an organisation of any size, ordered by impact.
Security engineer teaching security fundamentals, identity and network defence in plain language
I work on security for engineering organisations: access control, network design reviews, incident response and a lot of patient explaining. I believe most security problems are solved by clear habits rather than expensive tools.
My courses are for developers, IT staff and curious beginners who want to understand how attacks really happen and which controls actually reduce risk. We cover passwords and passkeys, MFA, least privilege, segmentation, logging and how to respond when something goes wrong.
I avoid fear based teaching. You will leave each course with a short list of concrete changes you can make at work or at home this week.
We found dozens of long lived API keys after the inventory exercise. Now replacing them with workload identity.
We followed the order from the course: admins with hardware keys, then a pilot, then everyone. Smooth so far.
Running Keycloak locally and reading a real ID token made the protocol click after years of confusion.
The explanation of adversary in the middle phishing was the clearest I have found. Practical detections too.
Report only mode advice saved us from locking out a whole department. Wanted more Entra specifics.
Accurate content. Being vendor neutral means you still need your IdP's docs for the exact clicks.