Build your security data lake w/ Amazon Security Lake, featuring
summary
Amazon Security Lake centralizes logs into customer-owned S3 buckets and normalizes them to the OCSF schema, ingesting AWS sources (VPC Flow, CloudTrail, Security Hub) and custom/partner feeds; GA supports 13 regions, rollups (IPG rolls to us‑east‑2), Athena/OpenSearch/QuickSight/SageMaker access, and 60+ partner integrations. Data remains in the account, Security Lake only ETLs certain AWS logs (15‑day free window per account), and subscribers get fine‑grained access control so analytics and long‑term retention work at scale.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:44Agenda
- 1:47Challenges
- 8:17What customers want
- 11:58Black Hat 2022
- 13:59Amazon Security Lake
- 15:27Integrations
- 17:21How does Security Lake work
- 18:10Bringing data into Security Lake
- 19:39Overview
- 20:52Security Console
- 26:40Visualizations
- 28:37Dashboards
- 30:02Troy Wilkerson
- 31:21Who is IPG
- 32:10Business challenges
- 34:33Journey with Security Lake
- 37:28Business Outcomes
- 40:55Future of Security Lake
- 44:29Wrapup
- 47:39Getting started
- 49:46Summary
- 51:51QA
related talks
17mUnifying Your Security Data with Amazon Security Lake and OCSF
39mAmazon Security Lake: Analyze Multiple Security Events
22mUse generative AI and Amazon Security Lake to enhance threat analysis
20mBuilding a better lake: Federated search for Amazon Security Lake
20mData lake deep dive: Using accelerated indexing for threat detection
47mDeveloping an autonomous framework with Security Lake & Torc Robotics
13mCloud-powered security with Amazon Security Lake & PwC’s fusion center
38mGet the most out of Splunk Security, OCSF, and Amazon Security Lake