01The story
The Friday advisory, and the two-hour question
A vendor you integrate with posts a breach advisory late on a Friday. Within two hours, your biggest customer's security lead asks if it touches their data.
A Friday evening, minute by minute
A vendor you integrate with posts a breach advisory.
Your biggest customer's security lead emails: does this touch our data?
Nobody knows which scopes that integration holds, or who set it up.
The answer becomes "we are looking into it", for the whole weekend.
The renewal call gets harder. Unless the register already had the row.
Three habits that end it
- A register of every integrationEach OAuth app and API key, its scopes, and the person who can revoke it.
- No long-lived keys in code or chatMove them to a secrets manager and rotate them on a schedule.
- Phishing-resistant sign-in for admins and engineersSecurity keys or passkeys first for the people who can push code or change the cloud.
