Security When It Is Someone Else’s Business
Working inside a customer’s environment means their security team, their compliance rules and their data classification apply — not your usual defaults. Getting this wrong does not just cause a bug, it can end the relationship.
The basics that get skipped under deadline pressure
- Least privilege — ask for exactly the access the task needs, nothing broader "just in case."
- Knowing what data you are allowed to log, store or even see — ask before you assume.
- A plan for what happens if your access is revoked mid-project, because it sometimes will be.
Why over-asking for access is its own riskAsking for broad access "to be safe" feels responsible but does the opposite — it widens what can go wrong if your account or laptop is ever compromised, and it is usually the first thing a customer’s security review flags.
Do this in 60 secondsLook at the access level of any tool, script or account you use regularly for work. Write down whether it actually needs everything it currently has — most things, once audited honestly, turn out to over-request.
Today’s AI angleAn AI agent with broad tool access inherits the same least-privilege problem at a larger scale — an agent that can technically delete records should not be given that power just because it is convenient during a demo.
Interview prepHow do you decide how much access to request when building an integration for a customer? I list exactly what the task needs to do, then request only the permissions that match that list — never broader access "just in case," because that is the default that gets flagged, and rightly so, when a customer's security team reviews it later. Least privilege is cheaper to ask for upfront than to explain afterward.