Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

7/26/2019
09:00 AM
Alex Wawro, Special to Dark Reading
Alex Wawro, Special to Dark Reading
News
50%
50%

Black Hat Q&A: Inside the Black Hat NOC

Cybersecurity expert Bart Stump explains what it's like to reliably deliver a useful, high-security network for one of the toughest audiences in the world.

When you sign up to attend Black Hat USA in Las Vegas next month, make sure to leave time in your busy schedule to check out the Black Hat Network Operations Center (NOC), the heart of the Black Hat network.

The Black Hat NOC team meet months before the event to strategize the best way to deliver a high-security, high-availability network to one of the biggest cybersecurity events in the world. The fact that this event is packed with security researchers, hackers, and network experts makes the process of deploying and securing the NOC just that much more exciting.

In addition to visiting the NOC itself, Black Hat attendees are invited to attend the special debriefing session offered at the end of the show.

In this popular Briefing, NOC crewmembers run down the tools and techniques they use to set up, stabilize, and secure the network, and describe what improvements they’ve made over the past year. I recently asked NOC leader Bart Stump offers to share his insight into what the NOC crew does and why Black Hat attendees should pay attention.

Alex Wawro: Hey there! Can you tell us a bit about who you are and what you do

Bart Stump: Hello! My name is Bart Stump and I am one half of the NOC leadership at Black Hat. I have been working with Black Hat for 12 years now.

Alex: What does your average workload look like at a Black Hat event?

Bart: The US show is obviously our flagship show and brings a much higher workload leading up to and during the event. Myself, and a small skeleton crew arrive four days before the show starts to begin setting up the network. During the show, there is the regular maintenance and issues that we work to deal with as quickly as possible. We also have obligations with tours, media, and our NOC debrief at the end of the show.

Alex: What's the most challenging thing about working in the Black Hat Network Operations Center?

Bart: I would say it's being able to think on your toes as issues arise [because] they need to be resolved in order to not impact attendees or trainers and speakers. Being able to work as a team and trust those around me to do their part is what makes the NOC go, and keep everything as stable as we do!

Alex: What should attendees know about the NOC that they probably don't?

Bart: Everyone is welcome to come see us, ask questions and stay involved with the work we do. If you have any questions, comments or concerns - we want to hear them! So come visit us and see what we do to keep Black Hat attendees safe!

Alex: Any fun stories from your time on the NOC Crew?

Tons! We have had many experiences over the years as the show continues to grow. From the friendships that I have gained and grown because of Black Hat, to the crazy network traffic we see every show, it is always fun and entertaining for sure!

P.S. we always have stories to tell at our debrief (which always helps close out Black Hat) and would be happy to share more there.

Black Hat USA returns to the Mandalay Bay in Las Vegas August 3-8, 2019. For more information on what’s happening at the event and how to register, check out the Black Hat website.

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

 

 

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14832
PUBLISHED: 2019-10-15
A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.
CVE-2017-10022
PUBLISHED: 2019-10-15
In haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like < > " ' must be escaped properly. In this case, the ' character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing ...
CVE-2019-10759
PUBLISHED: 2019-10-15
safer-eval before 1.3.4 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-10760
PUBLISHED: 2019-10-15
safer-eval before 1.3.2 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-17397
PUBLISHED: 2019-10-15
In the DoorDash application through 11.5.2 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.