Detection for Cloud Architects
Cloud detection is the security operations part of architecture: collecting audit logs, network flow logs and configuration changes, centralising them, and alerting on suspicious activity. Threat detection services and a defined incident response process help teams notice a compromise quickly and limit the damage.
Stage: Secure Architectures · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026
What to learn in Detection
- Enable audit logging for every account and send it to a protected store
- Centralise logs from several services into one searchable place
- Create alerts for root login, policy changes and unusual API calls
- Describe the stages of a cloud incident response
- Use automated remediation for common misconfigurations
Detection interview questions
Which logs matter most for cloud security?
Control plane audit logs, which record who called which API, are first. Then network flow logs, authentication logs and application logs. Together they show what changed, who changed it and what traffic moved, supporting both detection and investigation.
Why store logs in a separate, protected account?
If an attacker gains access to a workload account, they may try to delete evidence. Writing logs to an isolated account with restricted write-only access keeps them intact for investigation and meets many compliance requirements.
Where Detection fits in the Cloud Architect roadmap
Detection belongs to the Secure Architectures stage (advanced level), which takes about 38 hours. Protect workloads and data.
Other units in this stage
Back to the full Cloud Architect roadmap