When establishing a cloud incident response program, responders need persistent read access to resources, such as logs, configurations, and system data, in order to analyze and investigate incidents effectively. This access allows them to view and understand the nature of the incident, the affected systems, and any potential risks. In critical situations, controlled write access is necessary to take remedial actions, such as stopping malicious processes, patching vulnerabilities, or implementing other immediate security measures, but write access should be restricted and carefully managed to prevent misuse or errors.
Access limited to log events is too restrictive, as responders need more than just log events to fully analyze incidents. Unlimited write access for all responders is too broad and dangerous; unrestricted write access could lead to accidental or malicious changes to critical systems. Full-read access without any approval process could be dangerous if it allows responders too much access without appropriate oversight, potentially violating privacy or security policies.