What You Will Learn
Attackers Can Run But Not Hide. Our Radar Sees All Threats.
Cloud infrastructure provides organizations with new and exciting services to better meet the demands of their customers. However, these services bring with them new challenges, particularly for organizations struggling to make sense of the cloud native logs, keeping ahead of fast moving development teams, and trying to learn about how threats are adapting to cloud services. Securely operating cloud infrastructure requires new tools and approaches.
In SEC541, we start by walking through a real world attack campaign against a cloud infrastructure. We will break down how it happened, what made it successful, and what could have been done to catch them in the act. We spend the day dissecting the attacks, learning how to leverage cloud native and cloud integrated capabilities to detect, hunt, or investigate similar attacks in a real environment, and build our arsenol of analytics, detections and best practices for you to bring back to work on Monday.
SEC541: Cloud Monitoring and Threat Detection Will Prepare You To:
- Research attacks and threats to cloud infrastructure and how they could effect you
- Use AWS and Azure core logging services effectively to detect suspicious behaviors
- Move beyond the cloud provided GUIs to perform complex analysis
- Perform network analysis with cloud provided network logging
- Integrate container, operating system, and deployed application logging into cloud logging services for more cohesive analysis
- Make the most of managed security services such as AWS GuardDuty, AWS Detective and Azure Sentinel
NOTICE TO STUDENTS
This course was formerly 1-Day. Additional content around AWS as well as Azure, and more labs have been added to this content.
The labs in this course are hands-on explorations into AWS logging and monitoring services. Each lab will start by researching a particular threat and the data needed to detect it. Then the student will use native services within AWS to extract, transform, and analyze the threat. The course lecture coupled with the labs will give students a full picture of how those services within AWS work, the data they produce, and common ways to analyze those data.
Day 1 and 2 labs will center around your own infrastructure you will build in class, perform your own attacks, and gather those logs. Day 3, the class will open up to a larger shared AWS environment leverage managed security services.
WHAT YOU WILL RECEIVE
- Printed and Electronic courseware
- Virtual machine with all lab resources
- MP3 of the course
WHAT TO TAKE NEXT
Depending on your current job role and your future career plans, any of these courses may be a great follow-on to SEC541: Cloud Security Monitoring and Threat Detection:
Syllabus (18 CPEs)Download PDF
Section 1 will look at how attackers took over the infrastructure from the company CodeSpaces, and investigate how the AWS and Azure management plane and network logging can be used to detect similar techniques.
- SEC541 Environment Deployment
- Analyzing Cloud API logs with CloudTrail
- Parsing JSON-Formatted Logs with JQ
- Network Analysis
- Story Overview
- Course Overview
- Introduce MITRE ATT&CK
- Walk through of the attack
- Definitions of threat, hunting, detection, monitoring
Detecting T1526 with API Logging
- AWS CloudTrail
- Azure Activity Log
Log Parsing with JQ
Detecting T1499, T1078.004 with Cloud-Native Logging Services
- AWS CloudWatch
- Azure Log Analytics
- Proxying Services and Log Generation
Detecting T1048.001 with Network Flow Logging
- AWS VPC Flow Logs
- AWS Athena
- Azure Flow Logs
- Capturing Packets with AWS VPC Mirroring and Azure Virtual Tap
Section 2 of the course will investigate how bitcoin miners snuck into Teslas Kubernetes infrastructure, and will investigate ways to use cloud native services, application logs, managed container telemetry, and operating system logs to gather together data from across your organization to analyze for attack behavior.
- CloudWatch Agent
- CloudWatch Customization
- Strange ECS Behavior
- Metadata Services
Debrief Tesla Attack
- Story Overview
- Introduce MITRE Container Matrix
- Discuss threats to container-based deployments
Operating System Logs
- AWS CloudWatch Agent
- Azure Log Analytics Agent
- Third-Party Options
- Container Challenges
- AWS ECS (EC2 and Fargate)
- AWS EKS (EC2 and Fargate)
- Azure Container Instances
- Azure AKS
Cloud Services Logs
- Metadata Services
In Section 3, we will investigate the Capital One attack, how the attacker gained access and extracted over 100 million customers information, and investigate how AWS and Azures inventory services, managed security products, and active vulnerability services can be leveraged to identify potential vulnerabilities and threats in your cloud infrastructure.
- Lab: Cloud Inventory
- Lab: Discovering Sensitive Data in Unapproved Location
- Lab: Inspector
- Lab: Data Centralization
Debrief: Capital One
- Story Overview
- Walk through of the attack
- AWS GuardDuty overview and AWS provided threat intel
- AWS Detective
Detecting T1530 with Cloud Inventory
- Command Line Discovery
- AWS Config
Detecting T1105 with Data Discovery
Detecting T1190 with Vulnerability Analysis Services
- AWS Inspector
- AWS ECR
- AWS Event Bus
- AWS Kinesis Data Firehose
- AWS Elasticsearch
The target students should be familiar with AWS or Azure and have worked with it hands-on, especially security professionals working in the cloud security field who understand basic threats and attack vectors.
The course will assume that students are able to understand or do the following without help:
- Build a VM
- Understand how IAM roles/policies work
- Create key pairs for SSH log-in
- Understand basic cloud networking capabilities.
Other Courses SEC541 Students Have Taken
SEC541 students will run the exercises from a virtual machine that is configured with all the tools and documentation needed. All exercises will use Amazon Web Services (AWS).
IMPORTANT: You can use any 64-bit version of Windows, Mac OSX, or Linux as your core operating system that can also install and run VMware virtualization products. You also must have a minimum of 8 GB of RAM or higher for the virtual machines to function properly in the classVerify that under BIOS, Virtual Support is ENABLED.
Mandatory System Requirements
- System running Windows, Linux, or Mac OS X 64-bit version
- At least 8 GB of RAM
- 40 GB of available disk space (more space is recommended)
- Administrator access to the operating system
- Anti-virus software will need to be disabled in order to install some of the tools
- An available USB port
- Wireless NIC for network connectivity
- Machines should NOT contain any personal or company data
- Verify that under BIOS, Virtual Support is ENABLED
Mandatory Downloads Prior to Coming to Class
A 64-bit host operating system is installed (Windows is recommended)
Adobe Acrobat or other PDF reader application
Mandatory AWS Account Prior to Coming to Class:
- An AWS account is required to do the hands-on exercises during this course. The AWS account must be created prior to the start of class. Your ability to execute the exercises will be delayed if you wait to set up the AWS account in class.
- Estimated additional costs for the AWS account should be less than $20
- You will receive detailed instructions for setting up your AWS account before the start of class.
"Cloud service providers are giving us new tools faster than we can learn how to use them. As with any new and complex tool, we need to get past the surface-level how-to in order to radically reshape our infrastructure. This course is an overview of the elements of AWS and Azure that we may have used before but are ready to truly explore. By the end of the class, youll be confident knowing that you have the skills to start looking for the threats and building a true threat detection program in AWS and Azure." - Shaun McCullough and Ryan Nicholson
"I really enjoyed learning more about the AWS data sources and then performing relevant attacks against them to generate events that we could hunt for." - Gavin Knapp, Bridewell Consulting