{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2024-08-15T20:39:00Z",
      "note": "Imported from the Ctrl+Shift archive",
      "version": 1
    }
  ],
  "content_hash": "sha256:8be2799360bca9b7477a99700bb5540d3527d22c46e93021033e34db253acd80",
  "content_html": "\u003ch1\u003eScrew the principle of least privilege\u003c/h1\u003e\n\u003cp\u003eThe Principle of Least Privilege holds that every component in your system should have precisely the access to the rest of the system that it needs to fulfill its assigned responsibilities—and not one iota more.\u003c/p\u003e\n\u003cp\u003eThis sounds like a great idea! Coarse application of access control, like how most folks use \u003ccode\u003esudo\u003c/code\u003e, is find and dandy. Your CDN probably doesn’t need write access to your credit card database.\u003c/p\u003e\n\u003cp\u003eThe trouble comes when you apply this to your people by limiting their access to your systems.\u003c/p\u003e\n\u003cp\u003eSending builders or implementers or architects on a cross-departmental chase for access permissions so they can do their job is a \u003cem\u003ewildly terrible\u003c/em\u003e idea.\u003c/p\u003e\n\u003cp\u003eIf you trust people you’re doing this with, then you’re wasting their time and yours, and sending the constant and subtle message that you don’t trust them.\u003c/p\u003e\n\u003cp\u003eIf you don\u0026rsquo;t trust the people you’re doing this, \u003cem\u003efire them\u003c/em\u003e. Why on earth did you hire people you don\u0026rsquo;t trust in the first place?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003e\u003cstrong\u003eTrust your people—or fire them.\u003c/strong\u003e\u003c/strong\u003e\u003c/p\u003e\n",
  "content_md": "# Screw the principle of least privilege\n\nThe Principle of Least Privilege holds that every component in your system should have precisely the access to the rest of the system that it needs to fulfill its assigned responsibilities—and not one iota more.\n\nThis sounds like a great idea! Coarse application of access control, like how most folks use `sudo`, is find and dandy. Your CDN probably doesn’t need write access to your credit card database.\n\nThe trouble comes when you apply this to your people by limiting their access to your systems.\n\nSending builders or implementers or architects on a cross-departmental chase for access permissions so they can do their job is a _wildly terrible_ idea.\n\nIf you trust people you’re doing this with, then you’re wasting their time and yours, and sending the constant and subtle message that you don’t trust them.\n\nIf you don't trust the people you’re doing this, _fire them_. Why on earth did you hire people you don't trust in the first place?\n\n****Trust your people—or fire them.****",
  "created": "2024-08-15T20:39:00Z",
  "id": "57ys70bzeqqm433mmqvkwqjsxk",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/screw_the_principle_of_least_privilege/",
  "transclusions": [],
  "updated": "2024-08-15T20:39:00Z",
  "version": 1
}