Question 590
At Seabrook Media, a vendor integration reuses a developer's personal credential for production and loses access when that user leaves. Which monitoring step protects the accepted result?
Answer and explanations
The recorded symptom for Seabrook Media is that a vendor integration reuses a developer's personal credential for production and loses access when that user leaves. Reassess the targeted dependency over time: Rotate credentials and retest scopes after application or service-account changes.
The Seabrook Media case reports that a vendor integration reuses a developer's personal credential for production and loses access when that user leaves. A check of search stage and document permissions would not follow this failure mode. The relevant continuing control is: Rotate credentials and retest scopes after application or service-account changes.
This measure is focused on model-specific rbac choice. To catch a repeat of the Seabrook Media problem, rotate credentials and retest scopes after application or service-account changes.
This measure is focused on ai cost usage view selection. To catch a repeat of the Seabrook Media problem, rotate credentials and retest scopes after application or service-account changes.