| GLBA requirements |
What is it? |
Predefined reports in EventLog Analyzer |
| Section 314.4(b)(1) |
Login Monitoring: Procedures for monitoring login attempts and reporting discrepancies. |
- Network device reports on logon and security activities.
- AWS failed or unauthorized activity.
- Cloud user login activity.
|
| Section 314.4(c) |
Response and Reporting: Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity; and document security incidents and their outcomes. |
- Network device reports including logon, attack, configuration, and security activities.
- AWS activity encompassing user actions, failed/unauthorized events, config reports, and network security groups.
- Reports related to specific AWS services: Route 53, WAF, EC2, and Amazon ELB.
- Cloud storage and database activities including storage activity and database reports.
- Traffic analysis reports.
- IAM activity.
- Cloud user login activity.
|
| Section 501B (1) |
Ensuring the confidentiality of customer financial information. |
- Windows system events.
- IAM activity.
- AWS user activity, including failed and unauthorized events.
- File changes audit.
- Database reports.
|
| Section 501B (2) & (3) |
Protecting against anticipated threats to customer records. Protecting against unauthorized access to customer information that could result in substantial impact to the customer. |
- Windows and Unix logon reports.
- Terminal service session activity.
- IAM activity.
- AWS user activity, including failed and unauthorized events.
- Cloud user login activity.
|
