In this webinar:
Security information and event management play an important role in collecting data on network assets and traffic. That information can then be funneled through security orchestration and automation and response (SOAR) systems to protect network environments both on-premises and in the cloud. This webcast provides guidance on the key issues to consider when choosing SIEM or SOAR products for integration on the AWS platform and suggests a process for making such important decisions.
Attendees will learn about:
- Cloud design considerations affecting the selection and use of SIEM and SOAR technologies
- Needs and capabilities associated with SIEMs or SOARs with respect to bandwidth, performance affects, logging capabilities and more
- Key business, technical and operational considerations for SIEM/SOAR implementation
- Key AWS-specific considerations for enabling effective logging, endpoint protection, forensics, automation and reporting through SOAR systems
- Process for making an informed decision about products to integrate
Register now to be among the first to receive the associated whitepaper written by SANS Analyst and cybersecurity specialist J. Michael Butler.
About the SANS presenter:
J. Michael Butler is a SANS analyst who has also written SANS security training courseware and audited certification test questions; presents thought-provoking webcasts, and writes position papers, articles and blogs. He is an information security consultant with a leading provider of technical services for the mortgage industry, where he is involved in migration of assets to the cloud. Mike's responsibilities have included computer forensics, incident response, enterprise security incident management planning, internal auditing of information systems and infrastructure, information security policies, service delivery and distributed systems support. He holds the GCFA, GCIH, CISA, GSEC and EnCE certifications.
*The views and opinions of the SANS Institute and their presenter, J. Michael Butler, are their own, and do not necessarily reflect the positions of AWS.
