---
title: "Discussion on \"The Principle of Least Privilege: Why Less Access Means Better Security\" | Hashnode"
description: "Discussion on \"The Principle of Least Privilege: Why Less Access Means Better Security\". Imagine you have an application that only needs to read files from a cloud storage bucket. Would you give it permission to delete those files, create new buckets, or manage permissions across your ent"
url: "https://hashnode.com/posts/the-principle-of-least-privilege-why-less-access-means-better-security/6ad240594bef09219776a010"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Principle of Least Privilege: Why Less Access Means Better Security](https://codelikeawoman.com/the-principle-of-least-privilege-why-less-access-means-better-security?utm_source=hashnode&utm_medium=feed)

Imagine you have an application that only needs to read files from a cloud storage bucket. Would you give it permission to delete those files, create new buckets, or manage permissions across your ent

Oct 16 · 5 min read · codelikeawoman.com  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#security-best-practices](https://hashnode.com/tag/security-best-practices)
-   [#backend-development](https://hashnode.com/tag/backend-development)

## Written by

[Mirna De Jesus Cambero](https://hashnode.com/@mirnadjc)

@mirnadjc · Dominican Republic

  
[View profile](https://hashnode.com/@mirnadjc)

Coding, Debugging, Practicing

I'm a software engineer with over 15 years of experience. While my background is primarily in backend engineering, my work today spans cloud infrastructure, AI integrations, and the systems that support modern software applications. I started this blog to share what I’ve learned in a simplified, approachable way — and to add value for fellow developers. Though I’m an introvert, I’ve chosen to put myself out there to encourage more women to explore and thrive in tech. I believe that by sharing what we know, we learn twice as much — that’s precisely why I’m here.

## Responses 1

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 17](https://hashnode.com/posts/the-principle-of-least-privilege-why-less-access-means-better-security/6ad240594bef09219776a010/comment/6ad3364257d5597a97f7b02d)

The MVP part is the honest bit. The admin database user that "works out of the box" is usually still there two years later because nobody wants to find out what breaks. A cheap way to retrofit it: create the narrower role, point a staging copy at it, and let the permission errors tell you what the service really touches. The read-only analytics role example is a good first one to try, since the failures are loud and the blast radius is small.
