Overview#
Network of compromised devices controlled by an attacker. Used for DDoS, spam, credential stuffing, and proxying malicious traffic.
Core objectives#
- Establish shared definitions of Botnet for security, engineering, and leadership teams.
- Connect Botnet activities to measurable risk reduction and resilience goals.
- Provide onboarding notes so new team members can quickly understand how Botnet works here.
Implementation notes#
- Identify the primary owner for Botnet, the data sources involved, and the systems affected.
- Document the minimum viable process, tooling, and runbooks that keep Botnet healthy.
- Map Botnet practices to standards such as ISO/IEC 27001, NIST CSF, or CIS Controls.
Operational signals#
- Leading indicators: early warnings that Botnet might degrade (e.g., backlog growth, noisy alerts, or missed SLAs).
- Lagging indicators: realized impact that shows Botnet failed or needs investment (e.g., incidents, audit findings).
- Feedback loops: retrospectives and metrics reviews that tune Botnet continuously.
Related practices#
- Align Botnet with defense-in-depth planning, threat modeling, and disaster recovery tests.
- Communicate updates to stakeholders through concise briefs, dashboards, and internal FAQs.
- Pair Botnet improvements with tabletop exercises to validate expectations.