Skip to main content

🎥 Webinar - AWS and Suricata (Fundamentals)

We will be hosting an open webinar about the applicability and usage of Network Intrusion Detection Systems (specifically Suricata) and traffic analyses in AWS environments.

In it we'll cover the role network intrusion detection systems play in the MITRE ATT&CK AWS Matrix, networking, deploying and configuring Suricata as well as spending some time with 3CS AutoMirror to create an automated workflow that increases resiliency and security of your NIDS deployments.

The event is interactive and attendees are encouraged to participate as much as possible.


We'll be covering the following topics in the event:
  1. Applicability of NIDS and Traffic Analyses in AWS
    1. NIDS role in MITRE ATT&CK® AWS Matrix 
  2. Introduction to AWS VPC and its components 
    1. Subnetting; DHCP options; Access Control Lists
    2. NAT Instances
    3. Bastion Hosts
  3. Introduction to AWS EC2 in the context of NIDS and traffic capture
    1. Instance Types
    2. Security Groups
    3. Placement Groups & HPC
  4. Deployment and configuration of Suricata
    1. VXLAN 
    2. ENI - Elastic Network Interface
  5. AWS Traffic Mirroring
  6. Deployment and configuration of 3CS AutoMirror
    1. Automation
    2. High Availability 


20th of April @ 4PM UTC. Additional timezones.

Duration of the webinar: 2 hours


The event is open to everyone, even though we will not invite accounts that were created solely to interfere or spam the event. By the time registration closes, if you did not receive an invitation, please reach out to us.


Using a Google/YouTube-enabled e-mail address:

Registration closes on the 18th of April.


Simply visit the URL listed above at the time of the event. Even though you'll receive an email from YouTube inviting you to the stream a few days before the event date, the stream will only be live at the scheduled date.


There are many different ways that you can interact with us during the event, allowing you to chose the one you're most comfortable with.

The following will be monitored during the event to answer your questions:
Unfortunately YouTube Live Chat is not available in private streams.

Popular posts from this blog

Community Update - 3CORESec Blacklist 📓 🍯

Recently we tweeted about some issues we had with 3CORESec Blacklist , a platform that shares - openly and freely - a subset of the information seen and processed by our honeypot network.  While those issues have been addressed, and seeing as significant changes were made to how we monitor the generation of the lists (which is reflected in our status page ) and how we determine if an IP should be listed as an offending IP or not, this felt like a good opportunity to write a bit more about the platform as well as the changes we made.   For regular users of Blacklist 📓 the first thing they’ll notice is an increase on the numbers of IPs we include. That is a direct result of the changes we made and the growth of the honeypot network itself. We have not - and will not - ever increase the period for which we query the honeypot network, as we believe anything higher than 24h (as specified in the project page) for IP addresses can quickly fall into a decaying state that adds little value

Detection as Code (DaC) challenges - Introducing Automata

This blog post is the second part of our Detection as Code (DaC) challenges series. You can read part one here . The development process of detections by itself doesn't pose a lot of barriers for security engineering teams, as they are typically done in a lab/controlled environment, but after tuning and deploying rules to a SIEM, the work is only starting. Many things can go wrong after this, and a process of continued and automated testing is crucial. Detection Validation In an ideal (and fictional) world, once the datasets are parsed, normalized, and put into production, detections developed by your team would work forever. Still, the reality is quite different. Maintenance is heavy work that needs to be done frequently - especially if you work on an MSP - but the reality is that the ecosystem lacks tooling and processes to do it proactively. Effectiveness is an important metric and crucial to the successful response of incidents in time, and effectiveness is what we aim to ensu

Trapdoor - The serverless HTTP honeypot

  Today we are announcing the release of Trapdoor , our AWS-based serverless honeypot.  The idea of a serverless honeytoken isn't new. Adel released his honeyLambda a few years ago and we've been working with it for quite some time. It was because of this experience and the goal of improving on what was already a great idea that we decided to go to the drawing board and see how we would change and tweak the concept.  What is it? Trapdoor is a serverless application that can be deployed in any AWS environment. Its goal is to receive HTTP requests with the intent of identifying, and alerting, on its visitors. The URLs generated by Trapdoor can also be referred to as honeytokens .  While you can get creative on how to use it, one of the goals of a honeytoken is to be hidden or stored in a "safe" place and, if accessed, fire of an alarm, as access to the token would be considered a compromise or unauthorized access.  This example is the passive way of using deception ta