<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by James Holland on Medium]]></title>
        <description><![CDATA[Stories by James Holland on Medium]]></description>
        <link>https://medium.com/@jamesholland-uk?source=rss-975d610efb22------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*swJMV3DwkVftb8S3</url>
            <title>Stories by James Holland on Medium</title>
            <link>https://medium.com/@jamesholland-uk?source=rss-975d610efb22------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:40:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamesholland-uk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automation in the Black Hat NOC: From Lone Bottleneck to Collective Brain]]></title>
            <link>https://medium.com/palo-alto-networks-developer-blog/automation-in-the-black-hat-noc-from-lone-bottleneck-to-collective-brain-cb939f377515?source=rss-975d610efb22------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb939f377515</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[blackhat]]></category>
            <category><![CDATA[palo-alto-networks]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[operations]]></category>
            <dc:creator><![CDATA[James Holland]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 11:23:33 GMT</pubDate>
            <atom:updated>2026-01-23T15:48:17.407Z</atom:updated>
            <content:encoded><![CDATA[<h3>Black Hat’s Unforgettable Network</h3><p>The <a href="https://www.blackhat.com/">Black Hat</a> <a href="https://www.blackhat.com/us-25/noc.html">Network Operations Centre (NOC)</a> is not your typical corporate IT department. It is an annual proving ground where a carefully selected group of cybersecurity partners — including Palo Alto Networks, Arista, Cisco, Corelight and JAMF — collaborate on a unique test: defending against threats that emerge the very moment they are disclosed on stage.</p><p>Founded in 1997, Black Hat is an internationally recognised cybersecurity event series, with multi-day events showcasing the latest cutting-edge security research, developments, and trends.</p><p>For a decade, Palo Alto Networks has been a key partner in the Black Hat NOC, providing <a href="https://www.paloaltonetworks.co.uk/network-security">network firewall services and segmentation</a>. Furthermore, its comprehensive <a href="https://www.paloaltonetworks.co.uk/cortex">security operations platform</a> delivers SOAR (security orchestration, automation and response), log aggregation, and a centralised capability for security analytics, threat detection, and threat hunting.</p><p>The Black Hat NOC team’s primary objective is to provide a high-availability network that can withstand the intense, deliberate, and often surprising barrage of activity from thousands of attendees.</p><figure><img alt="Palo Alto Networks Next-Generation Firewalls at Black Hat USA" src="https://cdn-images-1.medium.com/max/1024/1*SVd0mRvKVuDzjomllVZN-Q.jpeg" /><figcaption>Palo Alto Networks Next-Generation Firewalls at Black Hat USA</figcaption></figure><p>This is a unique landscape. Unlike a traditional corporate network where any hacking activity is immediately deemed malicious, the Black Hat conferences are a nexus for cybersecurity research and ethical hacking. This means the NOC must operate in a perpetual state of “zero-hour response”, blending the normal flow of truly malicious threats with an extraordinary level of adversarial simulation. Attendees regularly conduct various forms of scanning and exploitation attempts as part of official trainings or independent research. The Black Hat NOC team developed the concept of “Black Hat positives” (as opposed to true or false positives) to distinguish benign student activity from genuinely malicious threats, a challenge that requires continuous vigilance and a deep understanding of the environment and the global threat landscape.</p><h4>The Challenge with Permanence in an Ephemeral World</h4><p>One of the most profound challenges facing the NOC is the ephemeral nature of its infrastructure. The entire network must be built from the ground up in a matter of days, and is dismantled just as quickly when the conference ends. This means traditional, static security and management practices become obsolete.</p><p>Beyond the temporary nature of the infrastructure, the team faces other significant operational complexities:</p><ul><li><strong>Bring Your Own Device (BYOD) Environment:</strong> The conference network is a BYOD free-for-all, with attendees connecting a vast array of personal devices. This makes traditional endpoint detection and response (EDR) solutions a significant challenge, effectively a non-starter except for a small number of Black Hat owned devices on the network. This forces the NOC to focus on robust network-based telemetry for detection and threat hunting.</li><li><strong>Zero-Day Threats:</strong> The NOC operates in a truly live-fire environment. There can be an urgent need to rapidly deploy detections for threats that do not yet exist in any signature database. Security researchers have previously disclosed new vulnerabilities just before or even during a Black Hat conference, forcing the team to create custom detections in real time.</li><li><strong>Controlled Chaos:</strong> The conference network is a nexus for cybersecurity research, where both benign and malicious activity are expected.</li><li><strong>Massive Data Volumes:</strong> The Black Hat network generates an immense volume of data, with close to a billion threat events annually. The sheer volume of this traffic creates a significant “signal-to-noise” problem for analysts.</li></ul><figure><img alt="Preparing Wireless Monitoring Devices for an Ephemeral Network" src="https://cdn-images-1.medium.com/max/1024/1*OWVL814DloUPJLLa6T8hvA.jpeg" /><figcaption>Preparing Wireless ThousandEyes Monitoring Devices for an Ephemeral Network</figcaption></figure><h3>The Old Way: Perils of the CLI and the Lone Automator</h3><p>Palo Alto Networks’ network security operations at the Black Hat NOC had previously relied on a traditional, manual process centred on a couple of engineers and CLI-based workflows. This process, while seemingly effective, was effectively single point of failure, and was fundamentally ill-suited for the scale, speed, and collaborative demands of a modern security operations centre.</p><h4>The Lone Automator’s Toolkit</h4><p>The traditional approach was heavily reliant on the Command-Line Interface (CLI). For a single expert, the CLI is a powerful and fast tool. However, the efficiency of a CLI is contingent upon the user’s familiarity with a large number of commands and a strong understanding of the syntax. While efficient for an expert, the steep learning curve and reliance on memorisation made it difficult to onboard new engineers.</p><h4>The Unscalable Solution</h4><p>The core drawbacks of this legacy approach were clear:</p><ul><li><strong>Error-Prone Manual Work:</strong> Manual typing is inherently error-prone, especially when managing complex deployments. A single typo in a configuration script can cascade into outages, misconfigurations, or security vulnerabilities. With no built-in guardrails or automated validation, tracing these human errors can be time-consuming.</li><li><strong>Poor Visibility:</strong> The CLI is a device-centric tool. It requires engineers to log into devices one by one to retrieve information, which creates a fragmented view of the network. It is almost impossible to spot patterns or anticipate problems across the entire infrastructure from this single-device perspective.</li><li><strong>Limited Collaboration:</strong> Since each engineer’s work often lives in individual sessions or personal scripts, sharing knowledge or configuration standards across a team becomes cumbersome. This increases the likelihood of inconsistent configurations and makes it difficult to replicate successful troubleshooting processes, hindering a unified team response.</li></ul><p>The shift away from a CLI-based workflow was not just a technological decision; it was a cultural one. The old model centred on individual experts and created “knowledge silos,” making it difficult to onboard new team members.</p><h3>The New Approach: Democratising Automation</h3><p>The Palo Alto Networks team within the Black Hat NOC realised that to protect an environment defined by its complexity and impermanence, they had to democratise automation. The power of the “lone bottleneck” engineer needed to be harnessed and distributed across the entire team, making automation accessible and safe for everyone to use. This strategic pivot marked a turning point, leading to the adoption of two powerful tools: Ansible and Semaphore.</p><h4>Ansible: The Universal Network Language</h4><p><a href="https://docs.ansible.com/">Ansible</a> was chosen as the primary automation engine for several compelling reasons. At its core, Ansible is an open-source, agentless configuration management tool.</p><p>Ansible also uses a simple, declarative language known as YAML, which is designed to be “human-readable” and easy for both developers and system administrators to understand. This simplicity lowers the barrier to entry, allowing team members with different skill sets to contribute to automation efforts. The availability of <a href="https://catalog.redhat.com/en/software/collection/paloaltonetworks/panos?tab=overview">Palo Alto Networks’ official and certified Ansible collection</a> made the integration seamless; the underlying protocol uses API calls wrapped within the Ansible framework, providing a consistent experience across different security devices.</p><figure><img alt="Heavily Redacted Example of Ansible in “CLI Mode”, Performaing Security Zone Configutation" src="https://cdn-images-1.medium.com/max/1024/1*gzdp3w70aVTrs4co9fNtsQ.png" /><figcaption>Heavily Redacted Example of Ansible in “CLI Mode”, Performing Security Zone Configuration</figcaption></figure><h4>Semaphore: The Collaboration Hub</h4><p>While Ansible provided the automation power, it was still, at its core, a command-line tool. The final piece of the puzzle was the adoption of <a href="https://semaphoreui.com/">Semaphore</a>, which provides an open-source and user-friendly, web-based interface for managing Ansible, as well as other automation tools like Terraform. It transformed Ansible from a CLI-based automation tool into a platform, solving the key problems of limited collaboration and poor visibility that plagued the old way of doing things.</p><figure><img alt="Semaphore UI Showing A Task List" src="https://cdn-images-1.medium.com/max/1024/1*2dUalSqX4Q6DbmkWBSDnrQ.png" /><figcaption>Semaphore UI Showing A Task List</figcaption></figure><p>Semaphore provided the essential features needed to democratise automation securely and effectively:</p><ul><li><strong>User-Friendly Interface:</strong> A GUI accessible to team members who may be less comfortable with the command line. This allowed the entire team to participate in the automation workflow, significantly lowering the learning curve and distributing operational knowledge.</li><li><strong>Robust Access Control:</strong> A fine-grained access control system, allowing administrators to control who can access specific resources and projects.</li><li><strong>Activity Audit:</strong> All activity is recorded, creating an audit trail. This provides crucial accountability and allows the team to easily restore the sequence of events if needed.</li><li><strong>Git Integration:</strong> Integration with git repositories, allowing the team to manage their playbooks and configurations as version-controlled code. This ensures that the automation logic is consistent, peer-reviewed, and easily recoverable.</li></ul><h3>The Modern Workflow in Action: From Code to Deployment</h3><p>With Ansible and Semaphore in place, the NOC team’s operational workflow began to move towards a code-driven approach. The core of this new process was the establishment of a single source of truth for the network.</p><h4>Building a Single Source of Truth</h4><p>Whilst some network configuration is still stored using Google Sheets, the Black Hat team are progressing towards “configuration as code”, storing network configuration data in a version-controlled git repository. This repository becomes the authoritative “source of truth” (SoT), a centralised repository of accurate, up-to-date information about the desired state of the relevant network and security posture.</p><p>This philosophical shift is paramount. The network configuration is no longer a set of commands residing on a device; it is a peer-reviewed file in a repository. This enables proactive management and automated remediation of configuration drift. For instance, via Semaphore, Ansible can compare a device’s configuration to the desired state in the git repository, and rectify any differences. This allows the team to enforce consistency and security policies automatically, moving them from a reactive to a proactive security posture.</p><figure><img alt="Updating Firewall Rules for Corelight, with Confoiguration Data Pulled From Git" src="https://cdn-images-1.medium.com/max/1024/1*ywH-sez7E9sHzzaZrcAo7Q.png" /><figcaption>Updating Firewall Rules for Corelight, with Configuration Data Pulled From Git</figcaption></figure><p>The git repository, integrated with Semaphore, serves as the single, verifiable “desired state.” The automation tools then enforce this state across the network, eliminating the root cause of many configuration issues and ensuring that the ephemeral infrastructure is built correctly and consistently, every time.</p><h3>Lessons for the Enterprise</h3><p>The Palo Alto Networks team’s journey in the Black Hat NOC, from a manual and CLI-driven process to a modern automated framework, is more than a technical anecdote. It is a case study for any enterprise grappling with the complexities of modern infrastructure. It shows that the challenges of ephemeral infrastructure, massive data volumes, and zero-day threats are not insurmountable when the right strategy is applied.</p><ul><li><strong>Manual approaches cannot keep pace with the speed and scale of today’s threats.</strong> The NOC’s experience proves that the only way to survive a high-volume threat environment is through intelligent automation. This is not just about speed; it is about reducing errors, freeing up human analysts to focus on critical decisions, and ultimately building a more resilient and agile security posture.</li><li><strong>The shift from “lone bottleneck” engineers to a collaborative “collective brain” is a strategic advantage.</strong> By democratising access to automation tools, the team moved beyond a single point of failure and created a culture of shared responsibility and knowledge. This was made possible by adopting user-friendly platforms and common languages that make automation accessible to the entire team.</li><li><strong>The importance of establishing a single source of truth for network configuration.</strong> By treating network configuration “as code” and managing it in a version-controlled repository, the team ensured consistency and security across their ephemeral network. This approach enabled them to move from constantly reacting to configuration drift to proactively enforcing the desired state of their infrastructure, a lesson that is universally applicable to any enterprise.</li></ul><p>This Black Hat NOC story is ultimately a testament to the power of people, process, and technology working in concert. It demonstrates that by embracing collaboration and automation, security teams can transform their operations, moving from a reactive model to a proactive and strategic one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95rm3hF5KooIC0yW3Kd0qg.jpeg" /><figcaption>Black Hat NOC Logo from Black Hat USA 2025</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb939f377515" width="1" height="1" alt=""><hr><p><a href="https://medium.com/palo-alto-networks-developer-blog/automation-in-the-black-hat-noc-from-lone-bottleneck-to-collective-brain-cb939f377515">Automation in the Black Hat NOC: From Lone Bottleneck to Collective Brain</a> was originally published in <a href="https://medium.com/palo-alto-networks-developer-blog">Palo Alto Networks Innovation Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security Automation at BlackHat Europe 2022: Part 2]]></title>
            <link>https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-2-cafd9bb913fe?source=rss-975d610efb22------2</link>
            <guid isPermaLink="false">https://medium.com/p/cafd9bb913fe</guid>
            <category><![CDATA[cortex]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[soar]]></category>
            <category><![CDATA[blackhat]]></category>
            <category><![CDATA[palo-alto-networks]]></category>
            <dc:creator><![CDATA[James Holland]]></dc:creator>
            <pubDate>Fri, 23 Dec 2022 09:01:35 GMT</pubDate>
            <atom:updated>2023-01-11T09:22:12.632Z</atom:updated>
            <content:encoded><![CDATA[<h4>In part 2 of this double-header, we look at the operations side of the conference infrastructure. If you missed part one, <a href="https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-1-ebee5ee88fb3">it’s here</a>.</h4><h4>Automating Security Operations Use Cases with Cortex XSOAR</h4><p>To reiterate from the previous post, on the Black Hat conference network we are likely to see malicious activity, in fact it is expected. As the Black Hat leadership team say, occasionally we find a “needle in a needlestack”, someone with true malicious intent. But how do you go about finding malicious activity with real intent within a sea of offensive security demonstrations and training exercises?</p><p>Without being able to proactively block the majority of malicious activity (in case we disrupt training exercises, or break someone’s exploitation demo in the Arsenal), we hunt. To hunt more efficiently we automate. It’s a multi-vendor approach, with hunters from Palo Alto Networks, Cisco, RSA Netwitness and Ironnet all on-site and collaborating. Cortex XSOAR provides the glue between all the deployed inline and out-of-band security tooling, as well as being the conduit into Slack for the analysts to collaborate and communicate.</p><p>An investigation may start from various angles and different indicators, and being able to quickly classify if the source of the incident is a training class is a great start. Without leaving Slack, an Cortex XSOAR chatbot is able to provide an automated lookup of a machine’s MAC address, and tell the analyst: the IP address, the vendor assigned to that MAC address where applicable, the wireless access point the host is connected to (thanks to the <a href="https://cortex.marketplace.pan.dev/marketplace/details/ciscomeraki/">Cortex XSOAR integration with Cisco Meraki</a>, docs <a href="https://xsoar.pan.dev/docs/reference/integrations/cisco-meraki">here</a>), and crucially the firewall zone where the machine is located. In the example below, the “tr_digi_forens_ir” zone tells us this machine is in a training class, specifically the <a href="https://www.blackhat.com/eu-22/training/schedule/index.html#digital-forensics-and-incident-response---tactical-edition-28151">digital forensics and incident response class</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*OahycQUzcLOjvTZkFS0qSg.png" /></figure><p>That’s really useful information when examining internal hosts, but how about a lookup for IP addresses which are sending traffic towards the Black Hat conference infrastructure in a suspicious way from the outside, from the Internet? To see if any of the variety of available Threat Intelligence sources have specific information available, and the level of confidence. There’s a Slack chatbot query for that too, powered by Cortex XSOAR:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*T8GRCtOgIke-J5vULDkliQ.png" /></figure><p>Or checking Threat Intellignce sources for information about a domain being contacted by a machine in the visitor wireless network which is potentially compromised, and analysing it in a sandbox too?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*fo1mm21FJoauByi9wGK9vA.png" /></figure><p>The chatbot has many features, all available to any analyst from any vendor working in the NOC, with no requirement to learn any product’s user interface, just a simple Slack chatbot:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*i3qPwDYxzTOejSJ-9DxsYQ.png" /></figure><p>Other ways of automating our operations included ingestion of the data from other deployed toolsets, like the <a href="https://www.paloaltonetworks.com/network-security/enterprise-iot-security">Palo Alto Networks IoT platform</a>, which below is shown creating incidents in Cortex XSOAR based on the passive device and application profiling it does on the network traffic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/1*yl0N7XPOk1RfoZMMeRwNeQ.png" /></figure><p>The data from the IoT platform enriches the incident, providing the analyst wish a page of information to quickly understand the context of the incident and what action would be appropriate:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*60oyw27v6Oh9IrV4M33QCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nMUI7d3mzn4QrM0CgFD8fg.png" /></figure><p>As well as integrating Cortex XSOAR with Cisco Meraki, we also <a href="https://cortex.marketplace.pan.dev/marketplace/details/RSANetWitness_v11_1/">integrated Cortex XSOAR with RSA Netwitness</a>, and were able to use alerts from Netwitness to generate and work through any incidents that looked like potentially malicious behaviour.</p><p>We also utilised Cortex XSOAR for some more network-focused use cases. For instance, by leveraging the intelligence data maintained within the PAN-OS NGFWs, we were interested to see if there was any traffic approaching the Black Hat infrastructure’s public facing services from TOR exit nodes, and we weren’t disappointed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*twZPcgI1HnYmyTAVu2UVRA.png" /></figure><p>We also leveraged Cortex XSOAR playbooks to provide an OSINT news into a dedicated Slack channel, so analysts could see breaking stories as they happen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*7LvfE1qKyn2nyxZdF2bWxw.png" /></figure><p>And we even used a Cortex XSOAR playbook to proactively monitor device uptime, which would alert into Slack if a critical device stopped responding and was suspected to be “down”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhOIuYlehIyJ3h_nM01kmg.png" /></figure><h4>Summary</h4><p>It’s an infrastructure full of malicious activity, on purpose. It gets built, rapidly, to a bespoke set of requirements for each conference. It is then operated by a collaboration of Black Hat staff and multiple security vendors’ staff.</p><p>That can only happen successfully with high levels of automation, in both the build and the operation phases of the conference. With the automation capabilities of the PAN-OS network security platform, the orchestration from Cortex XSOAR, and the collaboration across vendors, the Black Hat conference was once again a safe and reliable environment for all who attended.</p><h4>Acknowledgements</h4><p>Palo Alto Networks would like to once again thank Black Hat for choosing us to provide network security, as well as the automation and orchestration platform, for the operations centres of the conferences this year in Singapore, Las Vegas and London ♥</p><p>Thank you <a href="https://www.linkedin.com/in/ACoAACFPMvsBowbQY7BVIT7yxAo5i-AWTpIu59M">Jessica Stafford</a>, <a href="https://www.linkedin.com/in/ACoAAAFLCgoBJ4CNlmbnLfQQNRfMUZzqhIo8CvA">Bart Stump</a>, Steve Fink, <a href="https://www.linkedin.com/in/ACoAAAEh9yQBtYw4kEC1NNwwiFTHUc_jF5augV4">Neil R. Wyler</a> and <a href="https://www.linkedin.com/in/idisadmin/">ᴘᴏᴘᴇ</a> for your leadership and guidance. Thank you <a href="https://www.linkedin.com/in/ACoAAABS0PgBKYbrTVdE8kMfyZQW6bcsyETlfJo">Jessica Bair Oppenheimer</a>, <a href="https://www.linkedin.com/in/ACoAABLC3VYBRQsMIVNJyD1_e2JnE8uU6-zWpf4">Evan Basta</a>, <a href="https://www.linkedin.com/in/ACoAAAAK8EEBGz9veRC9GyQ2PSWs5h-VTivq2nY">Dave Glover</a>, <a href="https://www.linkedin.com/in/ACoAAByWGlQBRAR6OWH1hCVvmUXtJeJ0zqSSI0w">Peter Rydzynski</a> and <a href="https://www.linkedin.com/in/ACoAAAFWVFQBeQDpiQIPI-wPFI6IuGIR_ZuHSPg">Muhammad Durrani</a> for all the cross-vendor collaboration along with your teams including <a href="https://www.linkedin.com/in/ACoAAAWIq_4BogJKfkqk7nXaHMme8xK4rnAfmIo">Rossi Rosario</a>, <a href="https://www.linkedin.com/in/ACoAAAD5ol4BUJqYTZEgvW0c8sfPLDj9ZPfrAvE">Paul Fidler</a>, <a href="https://www.linkedin.com/in/ACoAABHTrGEB9bs86-oTBTo0xYO_drVGwkdbTuE">Panagiotis (Otis) Ioannou</a>, <a href="https://www.linkedin.com/in/ACoAAABTsgUBQsjXYF_fvC8fD8-M6SQ4HxbQwcM">Paul Mulvihill</a>, <a href="https://www.linkedin.com/in/ACoAAAH5tkMBUfVN7e3WYZiwT858XFpuSb-BiDQ">Iain Davison</a>, and (sorry) everyone else who may be lurking on other social media platforms where I couldn’t find them!</p><p>And of course, thanks so much to the amazing folks representing <a href="https://www.linkedin.com/company/palo-alto-networks/">Palo Alto Networks</a> in London, great job team; <a href="https://www.linkedin.com/in/ACoAAAMBaJUBiNqvIEKqgaR4coyNeQH7_FJDNDA">Matt Ford</a>, <a href="https://www.linkedin.com/in/ACoAAAJThRcB0ygupTextbGfH_IMQKzo3Heeqf0">Ayman Mahmoud</a>, <a href="https://www.linkedin.com/in/ACoAAAvIw10BQGHQOY3j89SwwZ-ztsfaiO_2DKU">Matt Smith</a>, <a href="https://www.linkedin.com/in/ACoAAAOQrjoBJ4en7tYa8iimYUq7so6FQMoAL3c">Simeon Maggioni</a> and <a href="https://www.linkedin.com/in/ACoAABR6G3UBnQ1EkCb5ACPkzAukWdBh5Zbznik">Doug Tooth</a>. Also <a href="https://www.linkedin.com/in/scottbrumley/">Scott Brumley</a> for his work on the Cortex XSOAR Slack chatbot during the USA conference earlier this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4s4-nDYDBoJqdm2aykc_w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cafd9bb913fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-2-cafd9bb913fe">Security Automation at BlackHat Europe 2022: Part 2</a> was originally published in <a href="https://medium.com/palo-alto-networks-developer-blog">Palo Alto Networks Innovation Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security Automation at BlackHat Europe 2022: Part 1]]></title>
            <link>https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-1-ebee5ee88fb3?source=rss-975d610efb22------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebee5ee88fb3</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[palo-alto-networks]]></category>
            <category><![CDATA[cortex]]></category>
            <category><![CDATA[blackhat]]></category>
            <category><![CDATA[ansible]]></category>
            <dc:creator><![CDATA[James Holland]]></dc:creator>
            <pubDate>Thu, 22 Dec 2022 10:09:52 GMT</pubDate>
            <atom:updated>2023-01-11T09:22:51.925Z</atom:updated>
            <content:encoded><![CDATA[<h4>In part 1 of this double-header, we look at the build and configuration tasks for the conference.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZqNaUzs9CydAFE3vbJW7g.jpeg" /></figure><p><strong>It’s been called one of the most dangerous networks in the world</strong>, and there are many good reasons why each Black Hat conference has its own IT infrastructure built from the ground up.</p><p>There are <a href="https://www.blackhat.com/eu-22/training/schedule/index.html">training classes</a>, where attendees learn offensive security techniques, from hacking infrastructure to attacking the Linux kernel, exploiting IIoT, and abusing directory services. There is the <a href="https://www.blackhat.com/eu-22/arsenal/schedule/index.html">Arsenal</a>, where researchers demonstrate the latest techniques, as well as <a href="https://www.blackhat.com/eu-22/briefings/schedule/index.html">briefings</a> from experts in a variety of security domains. Then add hundreds of eager and interested attendees, who are not only learning from the content at the conference, but may have their own tricks to bring to the party too.</p><h4>Roll Your Own</h4><p>A dedicated infrastructure that does not rely (as far as is possible) on the venue’s own network and security capabilities is the only feasible way to host this kind of community of keen security professionals. Building an infrastructure per conference means that a multi-disciplined team, from a variety of vendors and backgrounds, must find ways to make the build as streamlined as possible. <strong>Automation is key to the approach.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mm8kibxecsZ6lDwSiOKo9g.jpeg" /></figure><p>The Black Hat team <a href="https://www.blackhat.com/eu-22/noc.html">chose Palo Alto Networks</a> to provide network security for all three of their conferences during 2022, renewing an annual partnership which now spans 6 years. The partnership includes Palo Alto Networks supplying their staff to work in the conference NOCs, configuring and operating several <a href="https://www.paloaltonetworks.com/network-security/next-generation-firewall">PA-Series hardware next-generation firewalls (NGFWs)</a>. In 2022, the partnership expanded to include the use of <a href="https://www.paloaltonetworks.com/cortex/cortex-xsoar">Cortex XSOAR</a> to automate security operations.</p><h4>Automating the Build Process</h4><p>The build happens in a short period of time; the core infrastructure went <strong>from cardboard boxes to “live” in just over one day</strong> for the Europe 2022 conference. A design including complete segmentation of each conference area (including segmenting each training class, the Arsenal, the exhibiting vendors, the registration area, the NOC itself, and more), requires a lot of IP subnets and VLANs, multiple wireless SSIDs, and several DHCP servers and scopes. Some DHCP scopes require reservations, particularly where infrastructure components require predictable IP addressing, but there are too many of them for configuration of static addressing to be feasible. And change happens; IT security is a fast-paced industry, and we knew from experience that we would be adding, moving or changing the configuration data as the conference progressed.</p><p>With a single source for all of that configuration data, and a PAN-OS network security platform with plenty of automation capability, automation was inevitable, the only choice was the flavour!</p><p><strong>Step forward </strong><a href="https://www.ansible.com/"><strong>Ansible</strong></a><strong>.</strong> With its task-based approach, its ability to bring in configuration data from almost any structured source, and a <a href="https://pan.dev/ansible/docs/panos/">collection of modules for idempotent configuration of PAN-OS</a>, it was the perfect match for the requirements.</p><p>All of those segmented subnets needed configuring with IP addresses, as well as security zones. Here you can see some excerpts from a playbook execution, where Ansible observed modifications in the configuration data source, and changes were made to only to the required items, with the rest being of the configuration left in original state:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yP_LaDrV7eiVDgzIGgn1SQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gzdp3w70aVTrs4co9fNtsQ.png" /></figure><p>This is important; the initial configuration would not be the final configuration, so when re-executing Ansible to make incremental changes, we only want to make modifications where they are needed. This approach also speeds up the processing time for changes.</p><p>Below you can also see a long (and truncated, for brevity) list of DHCP reservations required for some of the infrastructure components. They are being configured with a single Ansible task; this is a list of MAC addresses and IP address that definitely does not want to be configured by hand!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rMW98_6wF_zVDTWeQgNWPQ.png" /></figure><p>The PAN-OS next-generation firewalls are the DHCP servers for every subnet, and at scale, such a large quantity of DHCP servers is also something which nobody would want to configure by hand, so again, Ansible did that for us automatically:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8p3rmk9VCLVTQC44afWdQ.png" /></figure><h4>Automatically Keeping an Eye on Suspicious Hosts</h4><p>It is rare that the Black Hat team has to take any action against a conference attendee; the majority of seemingly malicious activity is usually part of the trainings, a demo in the Arsenal, or something else “expected”. Occasionally attendees approach or cross the line of acceptable behaviour, and during those instances and investigations it is very useful to be able to view the historical data across the conference.</p><p><a href="https://www.paloaltonetworks.com/technologies/user-id">User-ID</a> provides a huge benefit when the network should include known and authenticated users, but at Black Hat conferences, that is not the case. There is no authentication past the pre-shared key to join the wireless network, and no tracking of any person that attends the conference. However, we chose to modify the <strong>user-to-IP</strong> mapping capability of User-ID to become <strong>MAC-to-IP</strong> mappings. Being the DHCP server, the PAN-OS NGFWs knew the MAC address of each host as it requested an IP address, so we routed that information into the mapping database. This meant we were able to observe a host machine (without any knowledge of the person using it) as it moved throughout the conference. Even if the machine left the network and joined again later (after lunch!?) with a new DHCP IP address, or if the machine moved between different wireless SSIDs and hence different IP subnets.</p><p>Should action be required when a machine is exhibiting unacceptable behaviour, one option is to utilise network security controls based on the MAC address of the host, instead of the IP address. These controls would be applicable no matter which network the host moved into.</p><h4>Part Two</h4><p>The second part of this double-header will focus on the operations side of the conference infrastructure, as the team (below) move into threat hunting mode. <a href="https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-2-cafd9bb913fe">Carry on reading here…</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4s4-nDYDBoJqdm2aykc_w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebee5ee88fb3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/palo-alto-networks-developer-blog/security-automation-at-blackhat-europe-2022-part-1-ebee5ee88fb3">Security Automation at BlackHat Europe 2022: Part 1</a> was originally published in <a href="https://medium.com/palo-alto-networks-developer-blog">Palo Alto Networks Innovation Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>