Skip to content
Security/prologue

Security is the floor

"Why we treat security as a baseline condition, not an optional layer."

Authored by:Hammad MajidHammad Majid

Why this exists

Small agencies get breached because they think security is only a big-company problem. It isn't. One exposed key, one unvetted npm package, or one credential sitting in Slack is all it takes. We handle client data that isn't ours to lose.

Operational Flow

1

Access: Make sure every credential and permission is owned by a named person.

2

Secrets: Never store secrets in plaintext in code, chat, or notes.

3

Vulnerabilities: Patch security holes before discussing them publicly.

4

Third parties: Treat every new package or vendor integration as an accepted risk.

5

Data: Handle client records as if the client is looking over your shoulder.

6

Culture: Make security everyone's job, not just the person blamed after a breach.

What good looks like

  • An engineer questions why a new dependency was added in their own PR before review.
  • Any team member can explain how we handle database storage in under two minutes.
  • Rotating a compromised key takes under 30 minutes because the process is documented.
  • An incident postmortem reads like a process failure instead of pointing fingers at people.

What NOT to do

  • Don't treat security as a checklist you read once and forget.
  • Don't assign security to one person and assume the team is safe.
  • Don't ignore the reasons behind the rules. Understanding why makes you act correctly when edge cases happen.

Security is a discipline where you only discover your mistakes after it is too late to fix them. We have seen smart agencies with good engineers lose client trust because a .env file ended up in a public repo, or an ex-employee retained admin access for months. These are not rare attacks. They happen every day. This chapter exists to make safe behavior the default.

Security at a small agency is about discipline, not expensive software. You do not need a security team if everyone treats credential hygiene like code quality. Read these rules, understand the reasons, and you won’t paste API keys into Slack.