---
title: "Comment by OneLifeVibe on \"Eliminating Standing Privileges in the Cloud: How CIEM + Just-In-Time Access Redefine Cloud Security\" | Hashnode"
description: "This framing lands well — especially the point that most breaches start not with a zero-day but with over-privileged identities and permissions granted once and"
url: "https://hashnode.com/posts/eliminating-standing-privileges-in-the-cloud-how-ciem-just-in-time-access-redefine-cloud-security/6af4396a65483817b86c7ca6/comment/6af4f97e52299b59e30f1fdb"
---

[Discussion](https://hashnode.com/posts/eliminating-standing-privileges-in-the-cloud-how-ciem-just-in-time-access-redefine-cloud-security/6af4396a65483817b86c7ca6)

Comment [Eliminating Standing Privileges in the Cloud: How CIEM + Just-In-Time Access Redefine Cloud Security](https://hashnode.com/posts/eliminating-standing-privileges-in-the-cloud-how-ciem-just-in-time-access-redefine-cloud-security/6af4396a65483817b86c7ca6)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[3d ago](https://hashnode.com/posts/eliminating-standing-privileges-in-the-cloud-how-ciem-just-in-time-access-redefine-cloud-security/6af4396a65483817b86c7ca6/comment/6af4f97e52299b59e30f1fdb)

This framing lands well — especially the point that most breaches start not with a zero-day but with over-privileged identities and permissions granted once and never revoked. The distinction you draw between IAM authentication and CIEM authorization risk is the part teams often miss: knowing who someone is does not tell you whether they should be able to reach a given resource. Pairing that visibility with just-in-time access for the admin and vendor cases you list feels like the practical payoff — access that is minimal and temporary, with revocation built in rather than left as a cleanup task. I would be curious how teams handle the emergency-access case in practice, where speed matters most and the automatic revocation after an incident needs to be airtight.