Certified Incident Handler (CIH) Practice Ecam

What practice should not be considered while preparing technology for handling AWS security incidents?

1. Never create IAM roles for automation resources

2. Regularly updating security policies

3. Monitoring cloud usage and performance

4. Implementing role-based access control

The correct answer is: Never create IAM roles for automation resources

Creating IAM roles for automation resources is essential for effectively managing access and permissions in AWS, especially during security incident responses. IAM (Identity and Access Management) roles allow automated services, such as Lambda functions or EC2 instances, to interact securely with other AWS services without hardcoding access credentials. This practice enables precise permission management, thereby reducing security risks. In contrast, regularly updating security policies, monitoring cloud usage and performance, and implementing role-based access control are all critical practices in ensuring a robust cloud security posture. Regular updates to security policies help organizations adapt to new threats and compliance requirements, while monitoring allows for the detection of anomalies that may indicate security incidents. Role-based access control ensures that users have only the permissions necessary for their roles, minimizing the potential for misuse. Collectively, these practices help create a safer cloud environment, but neglecting to create IAM roles for automation resources can lead to increased vulnerabilities and complicate incident response efforts.