Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes B.Tech - Computer Science / Information Science / Information Technology - Semester V Cloud Security A Comprehensive Undergraduate Textbook CHAPTER 4 Monitoring, Auditing and Management Unit IV: MONITORING, AUDITING AND MANAGEMENT Sections Covered 4.1 Proactive Activity Monitoring 4.2 Incident Response 4.3 Monitoring for Unauthorized Access 4.4 Detection of Malicious Traffic 4.5 Prevention of Abuse of System Privileges 4.6 Events and Alerts Management 4.7 Auditing in Cloud Systems 4.8 Record Generation 4.9 Reporting and Management 4.10 Tamper-Proofing Audit Logs 4.11 Quality of Service (QoS) 4.12 Secure Management Practices Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes 4.13 User Management 4.14 Identity Management 4.15 Security Information and Event Management (SIEM) Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Table of Contents Chapter Introduction / Overview Learning Outcomes Key Concepts 4.1 Proactive Activity Monitoring 4.2 Incident Response 4.3 Monitoring for Unauthorized Access 4.4 Detection of Malicious Traffic 4.5 Prevention of Abuse of System Privileges 4.6 Events and Alerts Management 4.7 Auditing in Cloud Systems 4.8 Record Generation 4.9 Reporting and Management 4.10 Tamper-Proofing Audit Logs 4.11 Quality of Service (QoS) 4.12 Secure Management Practices 4.13 User Management 4.14 Identity Management 4.15 Security Information and Event Management (SIEM) Further Reading / Viewing Laboratory Exercise Assessment Questions Chapter 4: Monitoring, Auditing and Management Chapter Introduction / Overview Cloud security does not end after designing access controls, encryption mechanisms and secure architecture. A cloud environment must be continuously monitored, audited and managed because users, workloads, networks, applications and threats change every day. Monitoring provides live visibility into what is happening in the environment, while auditing provides recorded evidence of what happened, who performed an action, when it occurred and whether the action was successful or failed. In cloud computing, monitoring is more complex than in a traditional data center because resources are elastic, distributed and often controlled through APIs. Virtual machines, containers, serverless functions, databases, load balancers, storage buckets and identity services can be created or modified rapidly. Without proper monitoring and logging, unauthorized access, privilege abuse, misconfiguration, data exfiltration and malicious traffic may remain hidden until serious damage occurs. This unit explains how proactive activity monitoring, incident response, alert management, audit- log generation, tamper-proof log storage, QoS management, secure administration, user management, identity management and SIEM systems work together to support secure cloud operations. The unit also connects cloud monitoring to practical tools such as CloudTrail, Azure Monitor, log analytics platforms, intrusion detection systems, dashboards and security operations centers. Did You Know: In cloud environments, many security incidents are first detected through unusual log patterns, such as impossible travel sign-ins, repeated failed logins, suspicious API calls, unexpected Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes privilege escalation or abnormal outbound traffic. Learning Outcomes Upon successful completion of this chapter, students will be able to: 1. Define proactive monitoring, cloud auditing, SIEM, QoS and secure management in cloud systems. 2. Explain how cloud activity monitoring helps detect unauthorized access, privilege abuse and malicious traffic. 3. Describe the main stages of incident response and connect them to cloud environments. 4. Identify important security events, alerts and audit-record fields used in cloud security operations. 5. Differentiate between monitoring, logging, auditing, reporting and management activities. 6. Explain how tamper-proofing, encryption, access control and retention policies protect audit logs. 7. Discuss the role of QoS, secure administration, user management and identity management in cloud operations. 8. Explain how SIEM platforms collect, normalize, correlate, alert and support investigation across cloud systems. 9. Design a simple cloud monitoring and incident response workflow for a small organization. 10. Prepare audit-ready reports and security-management practices for cloud infrastructure. Key Concepts Term Meaning in Cloud Security Proactive Monitoring Continuous observation of cloud assets, users, applications and networks to detect issues before they become serious incidents. Incident Response A structured process for preparing for, detecting, analyzing, containing, eradicating and recovering from security incidents. Audit Log A record of security-relevant activity, such as login attempts, administrative actions, data access, configuration changes and network events. Alert A notification generated when a rule, threshold or anomaly suggests a possible problem or security event. Unauthorized Access Access to a system, account, resource or data without proper permission or outside approved policy. Malicious Traffic Network communication associated with attacks such as scanning, malware command-and-control, DDoS, data exfiltration or exploitation attempts. Privilege Abuse Misuse of elevated permissions by an administrator, compromised account, insider or service identity. Tamper-Proof Logs Logs protected so that unauthorized modification, deletion or concealment is prevented or at least detectable. QoS Quality of Service, referring to performance, availability, latency, reliability and service-level expectations. SIEM Security Information and Event Management, a platform that collects, correlates, analyzes and reports security Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes events from multiple sources. 4.1 Proactive Activity Monitoring Proactive activity monitoring is the continuous observation of cloud resources, users, services, APIs and network behavior to identify security and operational problems early. Instead of waiting for a failure or breach report, proactive monitoring uses logs, metrics, traces, alerts and dashboards to maintain awareness of the cloud environment. In cloud infrastructure, activity happens at many layers. A user may sign in through an identity provider, an administrator may change a firewall rule, an application may access a database, a virtual machine may send outbound traffic, and a storage bucket may be made public. Each activity can generate telemetry that must be collected and analyzed. A good monitoring system answers questions such as: Which users accessed sensitive resources? Were there failed login attempts? Did a workload communicate with unknown IP addresses? Were new administrator roles assigned? Did CPU, memory or response time cross a threshold? Was a storage policy changed unexpectedly? Figure 4.1: Proactive monitoring continuously collects, correlates, alerts, responds and improves controls. Monitoring Area Examples of Activity to Monitor Security Value Identity activity Sign-ins, failed logins, MFA failures, password resets, role assignments. Detects account compromise, brute force attacks and privilege changes. Control-plane activity API calls, configuration changes, resource creation or deletion. Reveals unauthorized administration and misconfiguration. Network activity Flow logs, firewall logs, DNS queries, WAF events, VPN logs. Detects scanning, lateral movement, command-and-control and exfiltration. Compute activity VM events, container logs, process Detects malware, abnormal processes Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes behavior, patch status. and insecure hosts. Storage activity Object read/write/delete, policy changes, public access events. Protects sensitive files and supports data-loss investigation. Application activity Authentication events, business transactions, errors, API requests. Supports fraud detection, debugging and user-level investigation. Best Practice: Start monitoring from the most sensitive assets first: identity services, administrator actions, internet-facing services, critical databases and storage containing confidential data. 4.2 Incident Response Incident response is the organized approach used to handle cybersecurity incidents. A cloud incident may include compromised credentials, exposed storage, malware on a virtual machine, data leakage, DDoS attack, suspicious API activity, unauthorized database access or abuse of system privileges. Cloud incident response must be planned before an incident occurs. Teams should know who is responsible, which logs are required, how to isolate resources, how to preserve evidence, how to communicate with stakeholders and how to restore service safely. In cloud environments, many response actions are performed through automation and APIs, such as disabling keys, isolating instances, changing security groups, rotating secrets and taking forensic snapshots. A standard response process includes preparation, detection and analysis, containment, eradication, recovery and lessons learned. Each phase should be documented and periodically tested through tabletop exercises and simulated incidents. Figure 4.2: Incident response phases adapted for cloud environments. Phase Cloud-Specific Activities Output Preparation Define playbooks, enable logging, Incident response plan and readiness Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes create response roles, prepare forensic storage, train responders. checklist. Detection and analysis Review SIEM alerts, IAM logs, network flows, endpoint logs and application evidence. Confirmed incident scope, severity and affected assets. Containment Disable compromised users, revoke tokens, isolate VMs, block IPs, freeze storage access. Attack is stopped from spreading. Eradication Remove malware, patch vulnerability, rotate keys, remove malicious rules or backdoors. Root cause and persistence mechanisms removed. Recovery Restore services, monitor closely, validate backups and business functions. Secure return to normal operations. Lessons learned Update controls, detection rules, training, architecture and documentation. Improved security posture. Important Point: During a cloud incident, never delete suspicious resources immediately. Capture evidence such as logs, snapshots, configuration history and access records before cleanup whenever legal and organizational policies allow. 4.3 Monitoring for Unauthorized Access Unauthorized access occurs when a user, service account, application or attacker accesses a resource without valid permission or outside approved policy. In the cloud, unauthorized access is often caused by stolen credentials, weak passwords, missing MFA, overly permissive IAM policies, leaked API keys, misconfigured storage, exposed management ports or compromised service identities. Monitoring for unauthorized access requires combining identity logs, authorization decisions, resource access logs and contextual signals. A single failed login may not be critical, but repeated failures from many countries, a successful login from an unusual location, or a new administrator role assigned after a suspicious login can indicate compromise. Detection should focus on high-risk actions: root or owner account use, creation of access keys, disabling logging, modifying security policies, exporting data, changing network rules, deleting backups, and access outside normal working hours or approved locations. Unauthorized Access Signal Possible Meaning Recommended Response Multiple failed login attempts Password guessing or brute-force attempt. Trigger alert, enforce MFA, rate-limit, investigate source. Successful login from unusual location Credential theft or impossible travel. Require step-up authentication and verify user. New admin role assignment Privilege escalation. Review approver, ticket, identity and timing. Access from unknown device Compromised password or unmanaged endpoint. Check device compliance and conditional access. API key used from new IP Leaked credential or automation drift. Rotate key, restrict source IP and review code repositories. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Storage object bulk download Potential data exfiltration. Temporarily restrict access and investigate activity trail. Example detection logic for unauthorized access: IF sign-in status = success AND user location is unusual AND MFA was not satisfied AND resource sensitivity = high THEN create high-priority security alert and require account review. 4.4 Detection of Malicious Traffic Malicious traffic refers to network communication associated with attacks or suspicious behavior. Examples include port scanning, vulnerability exploitation, malware command-and-control communication, DDoS traffic, suspicious DNS queries, TOR or proxy access, unexpected outbound connections, data exfiltration and lateral movement between cloud workloads. Cloud platforms provide several sources for traffic visibility, including virtual network flow logs, firewall logs, load balancer logs, DNS logs, WAF logs, IDS/IPS alerts, API gateway logs and endpoint telemetry. These logs can be correlated to detect traffic that violates normal patterns or security policies. Detection should include both signature-based and behavior-based techniques. Signature-based detection identifies known threats, while behavior-based detection identifies unusual patterns such as a server suddenly sending large volumes of data to an unknown country or a database communicating directly with the internet. Figure 4.3: Network security controls classify traffic as allowed, suspicious or malicious. Traffic Type Common Detection Source Example Alert Port scanning VPC/VNet flow logs, IDS, firewall logs. Many denied connections to different ports from one source. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes DDoS traffic Load balancer metrics, CDN/WAF logs, network telemetry. Sudden spike in requests or bandwidth from distributed sources. Command-and-control DNS logs, threat intelligence, outbound proxy logs. Connection to known malicious domain or rare destination. Data exfiltration Flow logs, storage access logs, DLP, CASB. Large outbound transfer from sensitive workload. Web attack WAF logs, application logs, API gateway logs. SQL injection, XSS, path traversal or API abuse pattern. Lateral movement East-west flow logs, endpoint telemetry. Unusual internal connections between unrelated workloads. Best Practice: Store network-flow logs long enough to support investigations. Many attacks are discovered days or weeks after the first malicious connection. 4.5 Prevention of Abuse of System Privileges System privileges allow users and services to perform powerful actions such as creating resources, changing security settings, accessing sensitive data, managing encryption keys, deleting logs and modifying networks. Abuse of privileges may be intentional insider misuse, accidental misuse or the result of an attacker compromising an administrator account. Preventing privilege abuse requires strong governance. The principle of least privilege should be applied so that users receive only the permissions required for their tasks. Privileged accounts should use MFA, just-in-time access, approval workflows, session recording, command logging and separation of duties. Cloud environments should avoid long-lived static administrator credentials. Temporary credentials, managed identities, break-glass accounts, privileged identity management and automated policy reviews reduce the risk of uncontrolled privilege abuse. Control How It Prevents Privilege Abuse Example Least privilege Limits the damage that any account can cause. Developer can deploy app but cannot change billing or security logs. Separation of duties Prevents one person from approving and executing sensitive actions alone. Key deletion requires security and operations approval. Just-in-time access Gives elevated rights only for a limited time. Admin role active for two hours after approval. Privileged session monitoring Records commands and actions for accountability. Session log is reviewed after database maintenance. MFA for administrators Reduces risk from stolen passwords. Admin console requires authenticator approval. Immutable logging Prevents attackers from hiding privileged actions. Audit logs written to locked storage. 4.6 Events and Alerts Management An event is any recorded activity in a system. An alert is a notification generated when one or more events meet a defined condition. Not every event is an alert, and not every alert is an incident. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Event and alert management is the process of collecting events, defining alert rules, assigning severity, reducing noise, routing notifications and tracking actions until closure. Poor alert management creates alert fatigue. If analysts receive too many low-quality alerts, they may ignore important warnings. Therefore, cloud security teams must tune rules, suppress duplicates, enrich alerts with context and prioritize alerts based on business impact and threat severity. Alert handling should define severity levels, ownership, response time, escalation path, notification channel, evidence requirements and closure criteria. High-priority alerts should be linked to incident response playbooks. Severity Typical Condition Expected Action Critical Confirmed breach, active exfiltration, root/admin compromise, production outage. Immediate incident response and leadership notification. High Likely compromise, high-risk policy change, malware detection, privilege escalation. Rapid investigation and containment. Medium Suspicious behavior requiring review, abnormal access, repeated failures. Analyze within defined SLA and tune detection if needed. Low Informational anomaly or policy drift. Review during routine monitoring or compliance checks. Informational Normal event recorded for visibility. Store, index and use for reporting or trend analysis. Example alert rule: Trigger: More than 10 failed sign-in attempts for the same user within 5 minutes Condition: Source IP is outside approved geography Severity: High Action: Notify SOC, lock account temporarily, require password reset and MFA verification. 4.7 Auditing in Cloud Systems Auditing is the systematic review of records, configurations and activities to verify that cloud systems operate according to policies, standards, contracts and legal requirements. Monitoring is often real-time or near real-time, while auditing is usually evidence-based and may be periodic, event-driven or compliance-driven. Cloud audits examine identity records, access policies, network rules, storage permissions, encryption settings, backup status, vulnerability reports, change records, service configurations and incident history. Auditing helps prove accountability, detect policy violations, support forensic investigations and demonstrate compliance. A strong audit process requires complete records, synchronized timestamps, clear ownership, retention policies, protected log storage and documented review procedures. Auditors should be able to answer who did what, when, from where, using which identity, against which resource, and with what outcome. Audit Area Evidence Required Purpose Identity and access User lists, roles, group membership, MFA status, access reviews. Validate least privilege and user accountability. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Administrative activity API calls, console changes, privileged sessions, approvals. Detect unauthorized or risky changes. Data access Object access logs, database query logs, DLP events. Protect sensitive information. Configuration compliance Security group rules, encryption settings, backup settings. Identify policy drift and misconfiguration. Incident records Timeline, evidence, containment actions, recovery proof. Support legal, management and improvement needs. Change management Tickets, approvals, deployment logs, rollback records. Ensure controlled system modification. 4.8 Record Generation Record generation is the creation of structured evidence about events that occur in cloud systems. Records may be generated by identity providers, operating systems, applications, databases, storage services, networks, APIs, security tools and management platforms. A record becomes valuable when it contains enough context for analysis, investigation and reporting. Useful records should include time, source, actor, action, target resource, result, reason, request ID, IP address, device or workload identity, geographic context, user agent, severity and correlation ID where possible. Records should avoid unnecessary sensitive data such as passwords, tokens, full card numbers or private keys. Security teams should standardize record formats so that logs from different services can be searched and correlated. JSON and structured logs are preferred in modern cloud environments because fields can be indexed and queried efficiently. Record Field Meaning Example Timestamp When the event occurred. 2026-07-04T10:30:22+05:30 Actor User, service or process that initiated action. admin@example.com or vm-service- role Action Operation performed. CreateUser, DeleteBucketPolicy, LoginFailed Resource Target of the action. database/prod-customer-db Source Origin of the event. IP address, device ID, region, application. Outcome Result of the action. Success, Failure, Denied. Correlation ID Identifier linking related events. request-id-9c32ab Severity Risk or importance level. Low, Medium, High, Critical. Example structured security log record: { "time": "2026-07-04T10:30:22+05:30", "actor": "cloud-admin@example.com", "action": "UpdateNetworkSecurityRule", "resource": "prod-web-subnet", "source_ip": "203.0.113.25", "outcome": "success", "severity": "high", Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes "correlation_id": "req-88371" } 4.9 Reporting and Management Reporting converts monitoring and auditing data into meaningful information for technical teams, management, auditors and regulators. A report should not simply list raw logs. It should summarize the security posture, major risks, incidents, response performance, compliance status, trend changes and recommended actions. Cloud security reporting usually includes dashboards, daily operational reports, weekly risk summaries, monthly compliance reports and incident-specific reports. Management uses these reports to allocate budget, approve risk treatment, track service quality and verify that security controls are working. Good reporting separates technical details from executive summaries. A security analyst may need raw event IDs and packet details, while management needs trend lines, severity counts, unresolved risks, SLA breaches and business impact. Report Type Audience Contents Daily SOC report Security operations team. Open alerts, incidents, blocked attacks, high-risk changes. Weekly risk report Security manager and IT leads. Top risks, vulnerabilities, privilege changes, unresolved actions. Monthly compliance report Auditors, compliance team, management. Control status, audit findings, evidence gaps, retention status. Incident report IR team, leadership, legal if required. Timeline, root cause, impact, containment, recovery and lessons learned. QoS report Operations and service owners. Availability, latency, error rate, capacity, SLA/SLO performance. 4.10 Tamper-Proofing Audit Logs Tamper-proofing audit logs means protecting logs from unauthorized modification, deletion or concealment. Attackers often try to erase traces after compromising an account or system. If logs can be changed by the same administrators or workloads being monitored, accountability is weakened. Cloud environments can protect audit logs using write-once-read-many storage, object lock, versioning, retention policies, encryption, digital signatures, hash chaining, separate logging accounts, restricted access policies and continuous export to an independent SIEM or archive. Tamper-proofing should also include monitoring for attempts to disable logging or delete log storage. The goal is not only to preserve logs, but also to prove their integrity. During an investigation or audit, the organization should be able to show that records were generated, stored, retained and accessed according to policy. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Figure 4.4: Audit logs should be collected, protected, stored and analyzed in a tamper-resistant pipeline. Protection Method How It Helps Example Separate log account/project Prevents compromised workload owners from deleting logs. Production account sends logs to security account. Immutable storage Prevents changes during retention period. Object lock or WORM configuration. Encryption Protects log confidentiality. KMS-managed encryption key. Digital signatures or hashes Detects unauthorized modification. Hash chain for sequential log files. Strict access control Limits who can read, export or delete logs. Only security team can access audit archive. Retention and legal hold Preserves evidence for required period. Keep critical logs for 1 year or as policy requires. Important Point: Log confidentiality is also important. Logs may contain usernames, IP addresses, file names, API paths and business details that should not be exposed unnecessarily. 4.11 Quality of Service (QoS) Quality of Service refers to the expected level of service performance and reliability. In cloud security management, QoS includes availability, latency, throughput, error rate, capacity, resilience, backup success, recovery time and user experience. Security and QoS are connected because attacks, misconfigurations and privilege abuse can directly affect service quality. Monitoring QoS helps identify operational problems before users are affected. For example, increased latency may indicate resource exhaustion, DDoS traffic, database failure, poor scaling configuration or an overloaded dependency. Security teams should correlate QoS degradation with security events to determine whether a performance problem is actually part of an attack. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Cloud teams use Service Level Agreements (SLAs), Service Level Objectives (SLOs) and Service Level Indicators (SLIs) to measure and manage quality. Security controls should support QoS rather than blindly blocking legitimate business activity. Figure 4.5: QoS and secure management work together to maintain reliable and protected cloud service delivery. QoS Metric Meaning Security Connection Availability Percentage of time service is usable. DDoS, ransomware or misconfiguration may reduce availability. Latency Time taken to respond to a request. Malicious traffic or overloaded security inspection may increase delay. Throughput Volume of requests or data processed. Capacity abuse or exfiltration can distort throughput. Error rate Percentage of failed requests. Attack attempts may cause authentication or application errors. Recovery time Time needed to restore service. Incident response and backups directly affect recovery. Backup success Whether backups complete and can be restored. Backup failure increases impact of ransomware or deletion. 4.12 Secure Management Practices Secure management practices are the policies, procedures and technical controls used to administer cloud infrastructure safely. Cloud management includes provisioning resources, changing configurations, managing identities, applying patches, reviewing logs, rotating secrets, approving changes, handling incidents and maintaining compliance evidence. A secure management model should use least privilege, MFA, change control, secure administrative workstations, separate administrative accounts, approved automation, configuration baselines, vulnerability management, backup verification, encryption, logging and periodic access reviews. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Management-plane access is especially sensitive because cloud APIs can create, delete or modify resources at scale. A single compromised administrator token can affect the entire environment. Therefore, cloud management should be treated as a critical security boundary. Practice Description Example Change control Approve and document important configuration changes. Firewall rule change linked to ticket ID. Configuration baseline Maintain approved secure settings. Default encryption, private storage, logging enabled. Patch management Update OS, applications and agents. Monthly critical patch window. Secret rotation Regularly rotate passwords, keys and tokens. Rotate database password and API key after staff change. Backup testing Verify that backups can actually be restored. Quarterly restore drill. Administrative isolation Protect admin access from normal browsing or email risks. Use privileged access workstation or hardened admin device. Best Practice: Automate repetitive management tasks through approved infrastructure-as-code and policy-as-code pipelines. Manual console changes should be limited and audited. 4.13 User Management User management is the process of creating, modifying, disabling, reviewing and removing user accounts in a cloud environment. It covers employees, contractors, administrators, developers, auditors, temporary users and sometimes external partners. Poor user management causes orphaned accounts, excessive permissions and unmanaged access to sensitive resources. The user lifecycle includes onboarding, role assignment, access approval, periodic review, role change, suspension and offboarding. Cloud user management should be integrated with HR or organizational processes so that access changes happen when people join, move roles or leave the organization. User accounts should be grouped by role and responsibility. Direct permissions assigned to individual users should be minimized because they are harder to audit and maintain. Dormant accounts, shared accounts and accounts without MFA should be treated as risks. Lifecycle Stage Security Action Reason Onboarding Create identity, assign group, enable MFA, accept policy. Gives controlled initial access. Role assignment Map job responsibility to approved roles. Supports least privilege. Periodic review Review access with manager and resource owner. Removes unnecessary permissions. Role change Update groups and revoke old permissions. Prevents privilege accumulation. Suspension Temporarily disable account during leave or investigation. Reduces risk from inactive identity. Offboarding Disable account, revoke sessions, rotate shared secrets. Prevents former users from accessing systems. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes 4.14 Identity Management Identity management is broader than user management. It includes human users, service accounts, workloads, devices, APIs and federated identities. In a modern cloud system, identity is the new security perimeter because access decisions depend heavily on who or what is requesting access and under what conditions. Identity management includes authentication, authorization, MFA, SSO, federation, conditional access, identity governance, privileged access management, credential rotation and identity monitoring. It should support both centralized control and distributed cloud services. Security teams must monitor identity events continuously because many cloud attacks begin with identity compromise. Strong identity management reduces the chance that stolen credentials can be used to access sensitive systems. Identity Type Example Management Requirement Human user Employee, contractor, student administrator. MFA, role assignment, periodic review. Privileged user Cloud administrator, security engineer. Just-in-time access, session monitoring, strong approval. Service account Application identity used by workload. Least privilege, key rotation, no interactive login. Device identity Managed laptop, server, mobile device. Compliance check, certificate, endpoint protection. Federated identity External user authenticated by partner IdP. Trust policy, claims mapping, limited access. Workload identity VM, container, function or pod identity. Managed identity and scoped resource permissions. 4.15 Security Information and Event Management (SIEM) A Security Information and Event Management system collects security events and logs from many sources, normalizes them into a searchable format, correlates related activity, detects threats, generates alerts, supports investigation and produces reports. SIEM is a core tool used by Security Operations Centers. In cloud environments, a SIEM may ingest identity logs, audit logs, network flow logs, DNS logs, endpoint logs, application logs, database logs, container logs, firewall logs, WAF logs and vulnerability data. It may also enrich events with threat intelligence, asset criticality, user context and geolocation. Modern SIEM systems often integrate with SOAR, which stands for Security Orchestration, Automation and Response. SOAR playbooks can automatically perform actions such as disabling a user, blocking an IP address, opening a ticket, notifying a team, collecting evidence or enriching an alert. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Figure 4.6: SIEM platforms centralize security visibility across identity, network, endpoint, application and cloud services. SIEM Function Description Example Log collection Ingest events from many sources. Cloud audit logs, firewall logs, application logs. Normalization Convert different formats into common fields. Map source_ip, user, action and outcome. Correlation Connect related events across sources. Login from new country followed by admin role change. Alerting Notify when rules or analytics identify risk. Critical alert for disabled logging service. Investigation Search, pivot and build timeline. Trace user activity across multiple services. Reporting Produce dashboards and compliance evidence. Monthly report on privileged access. Automation Trigger playbooks for standard response. Disable suspicious account and open ticket. SIEM Reminder: A SIEM is only as useful as the quality of the logs and detection rules feeding it. Missing logs, noisy alerts and poor asset context reduce detection value. 4.16 Further Reading / Viewing Resource Type Resource Reason for Recommendation Official guidance NIST SP 800-137: Information Security Continuous Monitoring. Explains continuous monitoring strategy and security-control visibility. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes Official guidance NIST SP 800-61 Rev. 2: Computer Security Incident Handling Guide. Provides incident response lifecycle and handling guidance. Official guidance NIST SP 800-92: Guide to Computer Security Log Management. Useful for log collection, analysis, protection and retention. Official guidance NIST SP 800-207: Zero Trust Architecture. Connects monitoring and identity- based access to modern security architecture. Cloud guidance CISA Cloud Security Technical Reference Architecture. Explains cloud security layers, monitoring, shared services and incident response considerations. Cloud documentation AWS CloudTrail and Azure Monitor documentation. Practical examples of cloud audit trails, monitoring and alerts. Developer guidance OWASP Logging Cheat Sheet. Helps design useful and safe application security logging. SIEM documentation Microsoft Sentinel / IBM QRadar / similar SIEM product documentation. Shows practical SIEM ingestion, correlation, dashboards and response workflows. 4.17 Laboratory Exercise Lab Title: Designing a Cloud Monitoring and Audit Plan Objective: To design a basic monitoring, alerting and auditing plan for a small cloud-hosted web application. Step Activity Expected Output 1 List assets such as users, web server, database, storage bucket, network and identity provider. Cloud asset inventory. 2 Identify important logs: sign-in logs, admin activity logs, network flow logs, web logs and database access logs. Log-source checklist. 3 Define five alert rules for unauthorized access, privilege escalation, malicious traffic, disabled logging and data export. Alert rule table with severity. 4 Create an incident response workflow for compromised administrator credentials. Incident playbook. 5 Design an audit-log retention and tamper-proofing approach. Audit storage and retention plan. 6 Prepare a one-page management report template. Security reporting template. Suggested Submission: Students may submit the asset inventory, log-source checklist, alert table, incident workflow diagram and audit-retention plan as a single lab record. Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes 4.18 Assessment Questions Part A - Multiple Choice Questions (1 Mark Each) Q1. Which activity provides continuous visibility into cloud resources and users? 11. 1. Static documentation 12. 2. Proactive monitoring 13. 3. Manual billing 14. 4. Software installation Answer: (b) Q2. Which phase of incident response focuses on stopping an attack from spreading? 15. 1. Preparation 16. 2. Containment 17. 3. Reporting 18. 4. Procurement Answer: (b) Q3. A record of user actions, API calls and configuration changes is called a: 19. 1. Dashboard 20. 2. Audit log 21. 3. Virtual machine 22. 4. Load balancer Answer: (b) Q4. Which tool collects and correlates security events from multiple sources? 23. 1. SIEM 24. 2. Spreadsheet 25. 3. Compiler 26. 4. Text editor Answer: (a) Q5. Which of the following is a sign of possible unauthorized access? 27. 1. Successful login from unusual location 28. 2. Scheduled backup completed 29. 3. Normal CPU usage 30. 4. Approved maintenance window Answer: (a) Q6. What does tamper-proofing audit logs primarily help achieve? 31. 1. Faster image processing 32. 2. Log integrity and accountability 33. 3. Lower screen brightness 34. 4. Larger file size Answer: (b) Q7. Which metric is related to Quality of Service? 35. 1. Latency Unit IV: Monitoring, Auditing and Management Cloud Security • Comprehensive Undergraduate Textbook Notes 36. 2. Username length 37. 3. Keyboard type 38. 4. Font size Answer: (a) Q8. Which control helps prevent privilege abuse? 39. 1. Least privilege 40. 2. Public passwords 41. 3. Shared administrator account 42. 4. Disabled logging Answer: (a) Part B - Short Answer Questions (5 Marks Each) Q9. Define proactive activity monitoring and explain its importance in cloud security. Q10. Explain the incident response lifecycle with a cloud security example. Q11. What is unauthorized access? List any five indicators of unauthorized access. Q12. Explain how malicious traffic can be detected in a cloud network. Q13. Differentiate between events, alerts and incidents. Q14. What is auditing in cloud systems? Why is it im