Skip to main content

Monitoring for DevSecOpss

Security monitoring is collecting and analysing logs to detect attacks and misuse. Applications, hosts, cloud audit trails and network devices send events to a central store, and a SIEM correlates them with detection rules and alerts. Good logging records who did what and when, without storing secrets or excess personal data.

Stage: Detection and Response · Part of the DevSecOps roadmap · Last reviewed 19 November 2026

What to learn in Monitoring

Monitoring interview questions

What is a SIEM?

A security information and event management system collects logs from many sources, normalises and stores them, correlates events with rules or analytics and raises alerts. It also supports investigation by searching across systems during an incident.

What should security logs not contain?

Passwords, API keys, session tokens, full card numbers and unnecessary personal data. Logs are widely accessible and long-lived, so leaking secrets there creates new exposure. Mask or hash sensitive fields before writing them.

Where Monitoring fits in the DevSecOps roadmap

Monitoring belongs to the Detection and Response stage (advanced level), which takes about 4 hours. Operate securely.

Back to the full DevSecOps roadmap