Comprehensive AWS monitoring and security with EventLog Analyzer
Amazon Web Services (AWS) is a comprehensive, evolving cloud computing platform provided by Amazon. It offers a wide range of services including computing power, storage options, and networking, which are essential for running various applications and websites.
ManageEngine EventLog Analyzer, a robust log management tool , audits AWS logs to help ensure the platform's optimal performance, health, and security.
This tutorial outlines various use cases for monitoring and securing AWS environments using EventLog Analyzer. To effectively monitor and secure your AWS infrastructure with Eventlog Analyzer, you must enable logging and add AWS logs for monitoring.
AWS performance and health monitoring using EventLog Analyzer: Use cases
EventLog Analyzer addresses the following AWS monitoring use cases with its security auditing reports. These reports are predefined and can be scheduled to be generated at specific times and distributed over email.
| AWS component | Use case | Description | Why implement? | Available reports |
|---|---|---|---|---|
| EC2 | EC2 Instance State Monitoring | Monitor the state changes of EC2 instances and track key pair activities. | Ensure the optimal performance and operational status of EC2 instances. |
|
| S3 | S3 Bucket Activity Monitoring | Track all activities related to AWS S3 buckets, including accesses, modifications, and deletions. | Prevent unauthorized access and ensure data integrity and security. |
|
| IAM | IAM User Activity Monitoring | Audit IAM activities including user logins, authorization failures, and policy changes. | Ensure compliance with security policies and detect unauthorized changes. |
|
| Auto Scaling | Auto Scaling Activity Monitoring | Track the activity and performance of Auto Scaling groups, including instance and load balancer attachments. | Ensure efficient scaling and resource utilization. |
|
| Route 53 | Route 53 DNS Activity Monitoring | Track changes and activities in Route 53, including hosted zone and resource record set changes. | Ensure DNS configuration is managed correctly and changes are tracked. |
|
Securing an AWS environment using EventLog Analyzer: Use cases
The following table provides details on the threat detection scenarios available for an AWS environment in EventLog Analyzer. Moreover, our solution offers a flexible correlation rule builder, enabling users to create their own detection rules.
| Use case | Description | Why implement? | Available detection alerts and correlation rules |
|---|---|---|---|
| Unauthorized access attempts | Detect and prevent unauthorized access attempts to AWS resources by monitoring failed logins and authorization failures. | Protect sensitive data and prevent compromised accounts from causing security incidents. |
|
| Insider threats | Keeps track of user activities to uncover deliberate or accidental actions compromising cloud security. | Detects and mitigates risks from insider threats before they escalate. |
|
| Account hijacking | Detects attempts to compromise accounts. | Protects against account takeovers that could compromise cloud resources. |
|
| Privilege escalation | Monitors activities attempting to escalate privileges. | Prevents unauthorized access to critical resources and mitigates insider threats. |
|
Compliance
Ensuring compliance with data security and privacy regulations is a critical priority for organizations leveraging AWS. This section explores how robust monitoring practices can be implemented for your AWS environment, allowing you to address specific compliance requirements and maintain a secure cloud infrastructure.
| Compliance requirement: Solution mapping for AWS environments | |||
|---|---|---|---|
| EventLog Analyzer Reports and Alerts | Detection rules | Regulatory mandates | Requirements |
|
|
FISMA |
|
| PCI DSS | PCI DSS requirements 10.1 | ||
| SOX | SEC 302 (a) (4) (D) | ||
| HIPAA | 164.308 (a) (1) (ii) (D) | ||
| GLBA |
|
||
| ISO 27001:2013 | Control A 12.4.2 | ||
| GPG |
|
||
| ISLP |
|
||
| GDPR |
|
||
| NRC |
|
||
| Cyber Essentials |
|
||
| COCO | Authentication and Access Control | ||
| CCPA and CPRA | Section 1798.150.(a) | ||
| PDPA |
|
||
| CMMC |
|
||
|
AWS Config Errors | PCI DSS |
|
| SOX | SEC 302 (a) (4) (D) | ||
| HIPAA | 164.308 (a) (3) (ii) (A) | ||
| GLBA |
|
||
| ISO 27001:2013 | Control A 9.4 | ||
| GPG |
|
||
| ISLP |
|
||
| GDPR | GDPR ARTICLE 5 (1B) | ||
| Cyber Essentials | Secure Configuration | ||
| COCO | 2.Authentication and Access Control | ||
| CCPA and CPRA | Section 1798.150.(a) | ||
| NERC | CIP 005-6 R1.3 | ||
|
|
FISMA | Configuration Management (CM) |
| PCI DSS | PCI DSS requirements 10.2.3 | ||
| SOX | SEC 302 (a) (6) | ||
|
|
SOX | SEC 302 (a) (4) (C) |
| HIPAA |
|
||
| ISO 27001:2013 |
|
||
| GPG |
|
||
| ISLP |
|
||
| GDPR | GDPR ARTICLE 32 (2) | ||
|
|
FISMA | Configuration Management (CM) |
| PCI DSS |
|
||
| SOX | SEC 302 (a) (4) (C) | ||
| HIPAA | 164.306 (a) (1) (i) | ||
| GLBA | Section 314.4(c) | ||
| ISO 27001:2013 |
|
||
| GPG |
|
||
| ISLP |
|
||
|
SOX | SEC 302 (a) (4) (D) | |
|
AWS Config Errors | FISMA | Configuration Management (CM) |
| PCI DSS | PCI DSS requirements 10.2.3 | ||
|
EC2 Instance State Changes | FISMA | PCI DSS requirements 10.1 |
| PCI DSS | Configuration Management (CM) | ||
|
|
FISMA |
|
| HIPAA |
|
||
| GLBA |
|
||
| ISO 27001:2013 |
|
||
| GPG | Recording on Internal Workstation, Server or Device Status (PMC Rule 4) | ||
| ISLP | ARTICLE 18.1 | ||
| GDPR |
|
||
| Cyber Essentials | Secure Configuration | ||
| COCO | 1.B.Secure Configuration | ||
|
|
FISMA | Configuration Management (CM) |
| PCI DSS | PCI DSS requirements 10.1 | ||
| HIPAA | 164.306 (a) (1) (i) | ||
| GLBA | Section 314.4(c) | ||
| ISO 27001:2013 |
|
||
| GPG |
|
||
| ISLP |
|
||
| GDPR | GDPR ARTICLE 32 (2) | ||
| NRC |
|
||
| Cyber Essentials | Secure Configuration | ||
| NERC |
|
||
| CCPA and CPRA | Section 1798.105 (c) (2) | ||










