Detection and monitoring
Security department
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires.
Good for
- Design or assess monitoring coverage
- Work out why an incident went unnoticed
- Cut alert volume without losing signal
- Decide what a detection capability should cost
Ask this specialistNew here? 30 free credits, no card.
Authorities this specialist cites
- MITRE ATT&CK (opens in new tab) · The MITRE Corporation
- NIST SP 800-61: Incident Response Recommendations and Considerations (opens in new tab) · NIST
- NIST SP 800-92: Guide to Computer Security Log Management (opens in new tab) · NIST
- PCI Data Security Standard (opens in new tab) · PCI Security Standards Council
Related specialists
- Access and identityDesigns and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
- Chief information security officerOwns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure.
- Data protection and encryptionProtects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends against, managing keys and their rotation, handling secrets in applications and pipelines, minimizing and de-identifying, and deleting on purpose.
- Incident responseRuns a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward.
General guidance, not professional advice. Method adapted from headcount (MIT).