Overview#
Using stolen username-password pairs to gain unauthorized access. Mitigated with MFA, rate limits, breached-password checks, and bot protections.
Core objectives#
- Establish shared definitions of Credential Stuffing for security, engineering, and leadership teams.
- Connect Credential Stuffing activities to measurable risk reduction and resilience goals.
- Provide onboarding notes so new team members can quickly understand how Credential Stuffing works here.
Implementation notes#
- Identify the primary owner for Credential Stuffing, the data sources involved, and the systems affected.
- Document the minimum viable process, tooling, and runbooks that keep Credential Stuffing healthy.
- Map Credential Stuffing practices to standards such as ISO/IEC 27001, NIST CSF, or CIS Controls.
Operational signals#
- Leading indicators: early warnings that Credential Stuffing might degrade (e.g., backlog growth, noisy alerts, or missed SLAs).
- Lagging indicators: realized impact that shows Credential Stuffing failed or needs investment (e.g., incidents, audit findings).
- Feedback loops: retrospectives and metrics reviews that tune Credential Stuffing continuously.
Related practices#
- Align Credential Stuffing with defense-in-depth planning, threat modeling, and disaster recovery tests.
- Communicate updates to stakeholders through concise briefs, dashboards, and internal FAQs.
- Pair Credential Stuffing improvements with tabletop exercises to validate expectations.