<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2024.3.1. -->
<schedule>
    <generator name="pretalx" version="2024.3.1" />
    <version>1.0</version>
    <conference>
        <title>WICCON 2026</title>
        <acronym>wiccon-2026</acronym>
        <start>2026-10-29</start>
        <end>2026-10-30</end>
        <days>2</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://program.wiccon.nl</base_url>
        
        <time_zone_name>Europe/Amsterdam</time_zone_name>
        
        
        <track name="Talks" slug="7-talks"  color="#4f1473" />
        
        <track name="Workshops" slug="8-workshops"  color="#9c0000" />
        
    </conference>
    <day index='1' date='2026-10-29' start='2026-10-29T04:00:00+01:00' end='2026-10-30T03:59:00+01:00'>
        <room name='Main Hall' guid='58b66335-fbc4-53e9-9d2e-1b6a998afde9'>
            <event guid='b10b1fff-92be-560d-b550-13c7108e07e9' id='250'>
                <room>Main Hall</room>
                <title>WICCON Opening</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-29T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:05</duration>
                <abstract>Opening the Event</abstract>
                <slug>wiccon-2026-250-wiccon-opening</slug>
                <track>Talks</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/JNQAQS/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/JNQAQS/feedback/</feedback_url>
            </event>
            <event guid='e7464cee-f1de-51dd-a664-084cc365e3a5' id='222'>
                <room>Main Hall</room>
                <title>Will the train stop running? The value of responsible disclosure.</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-29T10:05:00+01:00</date>
                <start>10:05</start>
                <duration>00:25</duration>
                <abstract>In this talk, we share the story of how we almost got breached.
Long before the report came in, we were busy phasing out a legacy system that was used in train operations. A system that multiple internal and external stakeholders used in their primary traffic management processes.</abstract>
                <slug>wiccon-2026-222-will-the-train-stop-running-the-value-of-responsible-disclosure-</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='214'>Ola Jankowska</person><person id='215'>Catharine de Jong</person>
                </persons>
                <language>en</language>
                <description>We had already conducted a risk analysis that highlighted several severe cybersecurity risks, and even though the risks were known, everyone was still surprised when an actual responsible disclosure message came in, notifying us about the vulnerability.
We will show you how we handled this incident, what we learned, and how responsible disclosure helped accelerate the mitigation of cybersecurity risks.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/GMWX3Q/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/GMWX3Q/feedback/</feedback_url>
            </event>
            <event guid='40ffff65-559c-536d-be5c-c5aa70f0a155' id='249'>
                <room>Main Hall</room>
                <title>How to capitalise on other people&#8217;s popularity to distribute malware: Weaponizing CI/CD Pipelines</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-29T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>00:50</duration>
                <abstract>I am going to talk about software supply chain security, more precisely about exploiting CI/CD pipelines in GitHub so as to publish malicious versions of popular open source packages (just for example, on npmjs), write arbitrary code in GitHub repos or steal secrets.</abstract>
                <slug>wiccon-2026-249-how-to-capitalise-on-other-people-s-popularity-to-distribute-malware-weaponizing-ci-cd-pipelines</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='234'>Garance</person>
                </persons>
                <language>en</language>
                <description>Vulnerabilities are not only in your source code. They can hide in the deepest dependency of your project, in a build script, in a tool one of your dev uses. Every single piece of your software supply chain could impact the artefact you distribute. Including the pipelines you trust, the very pipelines that help you develop faster and secure your codebase. Maybe you should check on those to avoid distributing malware without even knowing it...

I&#8217;m going to show you various methods I&#8217;ve used to compromise popular open-source packages by exploiting their GitHub Actions workflows, or those of their dependencies.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/YTMLW9/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/YTMLW9/feedback/</feedback_url>
            </event>
            <event guid='52bc844f-e42f-54e9-9781-17581a37208b' id='205'>
                <room>Main Hall</room>
                <title>Hauntology in the Machine: Reanimating a Dead Language to Blindside Modern Security</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-29T11:30:00+01:00</date>
                <start>11:30</start>
                <duration>00:50</duration>
                <abstract>Jacques Derrida&#8217;s philosophy of hauntology shows that the ghosts of the past always return to life. We explore this concept through FORTH, an ancient programming language from the 1970s. By injecting a minimalist FORTH compiler into just 5KB of shellcode, attackers can operate on the lowest architectural floor. This talk serves as a spooky reminder that our most advanced systems are still governed by the very ghosts we thought we buried.</abstract>
                <slug>wiccon-2026-205-hauntology-in-the-machine-reanimating-a-dead-language-to-blindside-modern-security</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='198'>Marijke Moolenaar</person>
                </persons>
                <language>en</language>
                <description>Today, most security tools only look at the top layers of our computers; AI security tools, monitoring Windows APIs, and checking operating system logs. But what happens when an attacker entirely bypasses this framework by diving straight to the bottom floor (the machine code)?
&#8203;
No deep prior knowledge of low-level programming is required for this talk. We will break down the research step-by-step, explaining basic concepts like compilers and shells, making this session completely beginner-friendly. The technical foundation of this presentation is based on the fascinating offensive research by security researcher Josh Stone.

&#8203;Together, we will analyze this unique technique: injecting a fully functional compiler into just 5KB of shellcode. Instead of using modern languages, this technique resurrects FORTH, a minimalist language from the 1970s.

&#8203;A traditional compiler like GCC is a massive software system that needs to parse code into complex trees and link external libraries. FORTH does none of this. It functions simply as a command shell. Because the execution logic is so small, the entire compiler easily fits into a tiny piece of shellcode.

&#8203;This is where philosophy meets reality. Derrida&#8217;s concept of &apos;hauntology&apos; describes how ghosts of the past return to life to disrupt the present. By bringing back this &quot;dead&quot; language, hackers create temporary tools that modern endpoint scanners cannot see. When a hacker sends basic commands to this injected compiler, it talks directly to the CPU.

&#8203;Join this session to see how digging up ancient code can completely blindside modern security tools. And remember: next time your SIEM dashboard stays quiet but you hear a strange noise coming from your computer, it might just be the ghost of 1970 compiling inside your machine.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/9WMN9B/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/9WMN9B/feedback/</feedback_url>
            </event>
            <event guid='ccae1b93-5b05-532c-9945-730e5fe01201' id='211'>
                <room>Main Hall</room>
                <title>Humour, your Secret Weapon for more effective Cybersecurity Awareness</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-29T13:30:00+01:00</date>
                <start>13:30</start>
                <duration>00:25</duration>
                <abstract>Humour can be a powerful tool in cybersecurity awareness because it makes messages more memorable and engaging, ultimately supporting real behavior change. In this presentation you&apos;ll learn why humour is useful for more effective awareness campaigns. Research shows that humour can enhance understanding and retention when applied thoughtfully. However, it must be used carefully as misunderstanding and different viewpoints on what is considered funny can have the opposite effect of what you want to achieve. The  presentation closes with a short summary of do&#8217;s and dont&#8217;s for using humour in your next awareness campaign.</abstract>
                <slug>wiccon-2026-211-humour-your-secret-weapon-for-more-effective-cybersecurity-awareness</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='157'>Rosanne Pouw</person>
                </persons>
                <language>en</language>
                <description>Cybersecurity awareness is not all fun and games, but adding a bit of fun to the mix could be very beneficial!  Humour can be a very effective tool in creating a stronger connection with the people you&apos;re trying to reach with your awareness campaigns. Intuitively we understand that humour can help us bring the message across, form allies within the organisation and stand out from corporate communication messages. 

But this presentation take you back to why it is effective, especially with the rise of AI. We&apos;ll take a short tour to different parts of the world to see what humour looks like in different cultures. Humour that misses the point can also hurt your campaign. 

If you believe cybersecurity awareness could benefit from a more lighthearted approach, this presentation gives you a foundation to convince the ney-sayers in your organisation, and help you create more effective awareness campaigns.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/F3BVAN/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/F3BVAN/feedback/</feedback_url>
            </event>
            <event guid='adebf3c1-9e3f-5d05-a379-8358d092b815' id='217'>
                <room>Main Hall</room>
                <title>No IT is no IT problem</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-29T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:50</duration>
                <abstract>At 7:42 a.m., the call comes in. A critical supplier is no longer available. A regulation changes overnight. A platform your business depends on suddenly becomes a geopolitical liability. In that moment, one question matters more than any other: Do you still have a choice?

This presentation examines how organizations gradually lose strategic flexibility through everyday architectural decisions, vendor dependencies, operational complexity, and governance structures optimized for stability rather than adaptability.</abstract>
                <slug>wiccon-2026-217-no-it-is-no-it-problem</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='203'>Kim van Wilgen</person>
                </persons>
                <language>en</language>
                <description>Kim van Wilgen examines how hidden dependencies can limit strategic freedom and why resilience should be designed around adaptability rather than control. 

The session combines strategic storytelling, practical examples, and actionable frameworks that help organizations evaluate their resilience against cyber, operational, regulatory, and geopolitical disruption.

The central message is simple: The goal is not absolute control. The goal is preserving optionality.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/G3LJMT/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/G3LJMT/feedback/</feedback_url>
            </event>
            <event guid='2470c859-5e7d-569a-be68-ec9e450fe934' id='215'>
                <room>Main Hall</room>
                <title>Misbehaving while awake: nRF52810 Runtime EM Fault Injection APPROTECT Bypass - (CVE-2025-9709)</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-29T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:50</duration>
                <abstract>Fault injection campaigns normally require a lengthy, complex process that can be difficult to reproduce. Finding trigger timings often requires extended research on the target&apos;s power consumption and side-channel analysis.</abstract>
                <slug>wiccon-2026-215-misbehaving-while-awake-nrf52810-runtime-em-fault-injection-approtect-bypass-cve-2025-9709-</slug>
                <track>Talks</track>
                <logo>/media/wiccon-2026/submissions/CPTZQC/setup2_iQVV5mg.jpeg</logo>
                <persons>
                    <person id='205'>g0mb4ck</person>
                </persons>
                <language>en</language>
                <description>While trying to reproduce CVE-2020-27211 by LimitedResults, I discovered a novel, triggerless runtime attack on Nordic Semi&apos;s nRF52810 System-on-Chip (SoC) using electromagnetic (EM) fault injection. Unlike conventional approaches, this technique requires neither precise timing nor accurately synchronized EM pulses, making it remarkably simple and reproducible. Given the correct injection location, the attack succeeds on average with the first pulse. This is the first triggerless runtime attack ever reported. 
I will walk you through the research process and discuss where this work could lead next. 
This issue was recognized by Toreon as CVE-2025-9709.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/CPTZQC/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/CPTZQC/feedback/</feedback_url>
            </event>
            <event guid='85383004-4e91-50dc-923d-9bc2dc382083' id='195'>
                <room>Main Hall</room>
                <title>Supabase Shenaningans: Extended Edition</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-29T16:30:00+01:00</date>
                <start>16:30</start>
                <duration>00:25</duration>
                <abstract>In one week, Eden pentested two completely separate applications built on Supabase, and both had Row-Level Security disabled. This talk walks through both engagements, the surprising ways developers misunderstand Supabase&apos;s security model, and why this vulnerability class keeps appearing even when the documentation warns you plainly. If you&apos;ve ever shipped a Supabase app and didn&apos;t think twice about RLS, this one&apos;s for you.</abstract>
                <slug>wiccon-2026-195-supabase-shenaningans-extended-edition</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='190'>Eden Stroet</person>
                </persons>
                <language>en</language>
                <description>This talk covers two real-world penetration testing engagements conducted within the same week, both targeting applications built on Supabase. The findings were independently discovered, disclosed responsibly, and are now public on skelli.win.

The talk covers how Supabase&apos;s permissive defaults work and why they exist, the architectural mistake of rolling custom auth instead of using Supabase Auth, common RLS policy gaps, remediation patterns for Supabase developers, and what good responsible disclosure looks like from both sides.
The intended audience is anyone who builds with or recommends modern BaaS platforms, and anyone interested in how subtle architectural decisions create severe vulnerabilities. Technical enough for practitioners, accessible enough for developers just starting to think about security.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/8J8XPT/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/8J8XPT/feedback/</feedback_url>
            </event>
            <event guid='2f17635c-ce8f-5f7b-b14f-46221497ad21' id='175'>
                <room>Main Hall</room>
                <title>Well behaved women seldom make history</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-29T17:00:00+01:00</date>
                <start>17:00</start>
                <duration>00:25</duration>
                <abstract>For a long time I believed cybersecurity was a meritocracy; Work hard. Be good at your job. Speak the truth. The best person gets the role.

That&#8217;s the story we like to tell ourselves.

After more than 10 years in the field, much of it as a CISO, I&#8217;ve collected enough experiences to file a bug report against that idea.
In this talk I&#8217;ll share some of the greatest hits from my career: interviewing for a CISO job that didn&#8217;t actually exist, being told I&#8217;d make a great CISO &#8220;one day&#8221; while already being one, spending six hours in an assessment where my cybersecurity skills were never tested, and being advised by a psychologist to focus on raising my kids instead of pursuing leadership.</abstract>
                <slug>wiccon-2026-175-well-behaved-women-seldom-make-history</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='5'>Fleur van Leusden</person>
                </persons>
                <language>en</language>
                <description>The industry loves to tell women to adapt. Be less loud. Less confrontational. Dress differently. Speak differently. Be more strategic. Be less emotional.

So I tried that.

Spoiler: it doesn&#8217;t work.
Because the problem isn&#8217;t how women behave. The problem is the system evaluating them.

This talk isn&#8217;t about how I beat that system. It&#8217;s about what happens when you stop pretending the system works. It&#8217;s about the quiet ways talented people are pushed out of cybersecurity, and why the industry keeps reproducing the same leadership over and over again. And it&#8217;s about what we can actually do instead: amplify each other, open doors when we have the chance, and refuse to sand down the sharp edges that made us good at this job in the first place.

Cybersecurity loves talking about breaking systems.
Maybe it&#8217;s time we start with this one.

Cybersecurity loves to believe it&#8217;s a meritocracy. Work hard, be good at what you do, and the best person gets the job. But what happens when the system evaluating talent is broken?
In this talk, a CISO with more than a decade of experience shares a series of personal stories from inside the industry: interviewing for jobs that never existed, being told she might become a CISO one day while already being one, and failing a full-day assessment that never tested a single cybersecurity skill.
These experiences reveal uncomfortable truths about how hiring, assessments, and leadership selection actually work in cybersecurity, and who gets left behind.
This is not a talk about fixing yourself to fit the system.
It&#8217;s a bug report about the system itself.
Expect sharp edges, uncomfortable lessons, and a call to start hacking the culture of our own industry.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/9QXSDG/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/9QXSDG/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room' guid='68f47131-6986-5eb4-81ea-4c87ce675da0'>
            <event guid='15eb2d88-63f2-5d2b-9ec1-2473510ee96c' id='176'>
                <room>Workshop Room</room>
                <title>Social engineering techniques of hacking a human being</title>
                <subtitle></subtitle>
                <type>Workshop 120 minutes</type>
                <date>2026-10-29T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>02:00</duration>
                <abstract>Presentation of Social engineering theory, and techniques, going in-depth to learn about elicitation and building rapport with your potential victim. As we navigate the complex world of cybersecurity, it&apos;s essential to understand the tactics employed by social engineers. These attackers use psychological manipulation to influence individuals into divulging sensitive information or performing certain actions that compromise security. In this presentation, we&apos;ll delve into the world of social engineering, exploring its definition, techniques, and strategies for building rapport with potential victims.
Examples of real-life attacks, and final thoughts on who could be a social engineer and how to defend yourself against one.</abstract>
                <slug>wiccon-2026-176-social-engineering-techniques-of-hacking-a-human-being</slug>
                <track>Workshops</track>
                <logo>/media/wiccon-2026/submissions/ZQY987/WIRlogo-removebg_mu4OvGh.png</logo>
                <persons>
                    <person id='168'>Dorota Kozlowska</person>
                </persons>
                <language>en</language>
                <description>1. What is social engineering? Examples.
2. Becoming Anyone you want to be - Pretexting.
3. Four Phases of Social Engineering (Reconnaissance, Engagement, Exploitation, Closure);
4. Building your artwork: What is elicitation? Elicitation Techniques.
5. I know how to make you like me: Building Rapport.
6. Examples of Real Social Engineering Attacks.
7. Now What? Skills you need to become a social engineer, and how to defend yourself.
8. Conclusion, final thoughts

The person listening to my talk will end it with tangible knowledge on social engineering and places to go if they want to learn more. This workshop will include working in groups, and challenges for attendees - to gain some real skills, and better memorization of the techniques presented.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/ZQY987/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/ZQY987/feedback/</feedback_url>
            </event>
            <event guid='482d05c6-6e88-52be-86ee-3e03bb090b69' id='231'>
                <room>Workshop Room</room>
                <title>Want to play a game?</title>
                <subtitle></subtitle>
                <type>Workshop 60 minutes</type>
                <date>2026-10-29T13:30:00+01:00</date>
                <start>13:30</start>
                <duration>01:00</duration>
                <abstract>It&apos;s 02:47 in the morning when the call comes in. Some systems aren&apos;t responding. Customer data may have been stolen. Your phone won&apos;t stop ringing and your colleague asks you with a shiver in his voice: &quot;What do we do now?&quot;

Having watched dozens of leadership teams walk into that exact moment here&#8217;s what stands out: Most of them have crisis plans. Most of them have done a tabletop. Almost none of them stay calm the way they thought they would.</abstract>
                <slug>wiccon-2026-231-want-to-play-a-game-</slug>
                <track>Workshops</track>
                <logo>/media/wiccon-2026/submissions/BQV3AJ/CyberMasterWiccon_DGg6YQf.png</logo>
                <persons>
                    <person id='140'>Kaja M&#246;ller</person>
                </persons>
                <language>en</language>
                <description>This talk is about what happens when the playbook breaks. Not the plan written down, but the reflex underneath it. In gamified fully-immersive simulations we put teams in a room with a live SIEM, a hacker on the chat, social media on fire, a regulator on hold and a ransom on the table. No pause. The clock runs. The information keeps changing.

What we see in that room is not what people tell themselves they would do. What I&apos;ll show you today is what really decides how a team gets through it: The patterns we watch for during a simulation, scored in the moment so we can come back three months later and see who got sharper.

And you won&apos;t be sitting still for all of it either. Somewhere in this hour you&apos;ll be asked to make a decision you can&apos;t unmake. No saws. No lost legs. Just the clock, what you don&apos;t know yet, and no one but you to make that call. The same call those teams faced.

I won&apos;t tell you what they decided.

You&apos;ll have to come see for yourself&#8230;</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/BQV3AJ/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/BQV3AJ/feedback/</feedback_url>
            </event>
            <event guid='66d37923-f820-533b-8d4b-bdb0b3669954' id='181'>
                <room>Workshop Room</room>
                <title>Coverage-guided Fuzzing</title>
                <subtitle></subtitle>
                <type>Workshop 120 minutes</type>
                <date>2026-10-29T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>01:30</duration>
                <abstract>Coverage-guided fuzzing is a software testing methodology that is effective at finding vulnerabilities by automatically and continually making small changes to the program&apos;s input and observing its effect on the path a program takes. This hands-on workshop aims to give you the tools needed to set up a simple working fuzzing environment for your own targets.</abstract>
                <slug>wiccon-2026-181-coverage-guided-fuzzing</slug>
                <track>Workshops</track>
                
                <persons>
                    <person id='170'>Sebastiaan Groot</person><person id='195'>Frank Cozijnsen</person>
                </persons>
                <language>en</language>
                <description>Fuzz testing is a broad area of software testing that involves making many, (informed) random mutations on input with the goal of finding bugs. This workshop focuses on coverage-guided fuzzing methodologies where the path a program takes for specific inputs is used to decide which inputs to further mutate. This method of testing allows for gaining more coverage across the program faster but requires specific preparation for the target.

The following topics will be covered during the session:

- Compiling an instrumented binary
- Creating an initial corpus
- Perform coverage-based fuzzing
- Interpreting results

For this workshop no prior fuzzing knowledge is required, but limited familiarity with C and basic understanding of memory layout are assumed.

IMPORTANT: The workshop requires a laptop with Docker installed.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/9MB79U/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/9MB79U/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='2' date='2026-10-30' start='2026-10-30T04:00:00+01:00' end='2026-10-31T03:59:00+01:00'>
        <room name='Main Hall' guid='58b66335-fbc4-53e9-9d2e-1b6a998afde9'>
            <event guid='e389b3c4-eff8-5cca-a50c-359f9e1d0560' id='214'>
                <room>Main Hall</room>
                <title>The Dark Spell of Trust: How Secure Systems become Enablers of Financial Crime</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-30T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:25</duration>
                <abstract>In today&#8217;s threat landscape, the most dangerous scenarios are not the ones you detect&#8212;but the ones that look perfectly normal.
Cyber Security assumes systems can be compromised. Financial crime frameworks assume systems can be trusted. But what happens when those assumptions collide?

This session explores the hidden intersection where identity compromise, data manipulation, and legitimate system access transform secure environments into enablers of financial crime. Across AML, fraud, sanctions, and corruption risk, attackers are no longer just bypassing controls&#8212;they are operating within them.
It challenges the belief that &#8220;secure systems produce safe outcomes,&#8221; and introduces a new perspective: financial crime risk as a direct consequence of broken trust in identity, data, and behaviour.</abstract>
                <slug>wiccon-2026-214-the-dark-spell-of-trust-how-secure-systems-become-enablers-of-financial-crime</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='187'>Caroline</person>
                </persons>
                <language>en</language>
                <description>In Cyber Security, we design controls assuming attackers are already inside, identities can be compromised, and systems&#8212;even trusted ones&#8212;can be manipulated. 

Financial crime frameworks have evolved differently. Across AML, fraud, sanctions, and anti-bribery &amp; corruption (ABC), controls are built on a more implicit assumption: that identities are real, data is accurate, and systems provide a reliable view of reality. Risk is detected through patterns, rules, and known typologies&#8212;often after events have already taken place.

This session explores what happens when these two worlds meet.
Using real-world examples and cross-domain insights, we will examine how modern attack techniques&#8212;such as identity compromise, synthetic identities, data manipulation, and abuse of legitimate access&#8212;can quietly undermine financial crime controls. In these scenarios, systems continue to operate as designed, transactions appear legitimate, and decisions remain &#8220;compliant&#8221;&#8212;while financial crime risk unfolds undetected beneath the surface.

The talk will: 
- Compare the core assumptions of cybersecurity and financial crime frameworks
- Explore how &#8220;trusted systems&#8221; can become enablers of AML breaches, fraud, sanctions evasion, and corruption risk
- Highlight what cybersecurity can learn from financial crime disciplines, including decision accountability and risk assessment under uncertainty
- Translate these insights into practical actions for CISOs and security teams&#8212;focusing on identity trust, data integrity, and cross-domain detection
- Challenge the audience to rethink how signals, systems, and trust models should be connected
This is not a compliance session. It is a conversation about trust. And how both cybersecurity and financial crime functions must evolve together to respond.

This session is an invitation for cybersecurity professionals to extend their thinking beyond infrastructure and to play a critical role in preventing financial crime risks that traditional controls were never designed to detect.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/YJJ3DR/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/YJJ3DR/feedback/</feedback_url>
            </event>
            <event guid='859e2544-6a0a-5c21-82a6-b34bcebe3747' id='207'>
                <room>Main Hall</room>
                <title>War and Unpeace: How Russia became one of the world&apos;s most advanced cyber threat actors</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-30T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>00:50</duration>
                <abstract>One cannot open an annual report on advanced persistent threats without finding Russia listed as one of the top threats in the cyberdomain. This talk examines Russia&apos;s evolution as a threat actor from a broader perspective, drawing on historical, socio-economic and cultural factors. Viewed through this broad lens, the tactics, techniques and procedures of Russian APTs emerge not as random aggression, but as the expression of a coherent - if at times failing - doctrine.</abstract>
                <slug>wiccon-2026-207-war-and-unpeace-how-russia-became-one-of-the-world-s-most-advanced-cyber-threat-actors</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='200'>Dominique Heuff</person>
                </persons>
                <language>en</language>
                <description>Russia&apos;s emergence as a top-tier cyber threat actor is not a coincidence or a purely technical achievement &#8212; it is the product of a historically grown state logic in which geopolitical ambitions, economic constraints, and a deep cultural distrust converge. This talk traces that logic across five interconnected dimensions: the Soviet and post-Soviet institutional heritage, economic marginalisation, political consolidation under Putin, socio-cultural narratives of encirclement, and deliberate technological capacity-building. The Ukrainian war serves as the critical stress test &#8212; revealing both the destructive potential and the surprising limitations of Russian cyber operations in a combined-arms conflict. Russia&apos;s Tactics, Techniques and Procedures are then examined through this strategic lens, showing how they reflect not random aggression but a coherent, if sometimes failing, doctrine.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/MFEAAW/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/MFEAAW/feedback/</feedback_url>
            </event>
            <event guid='c7a50cdb-d97b-5c2f-abc9-4374fdd0da40' id='182'>
                <room>Main Hall</room>
                <title>The end of human pentesting?</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-30T11:30:00+01:00</date>
                <start>11:30</start>
                <duration>00:50</duration>
                <abstract>I built a homemade offensive pipeline from free tools, a few hundred lines of Python, and an LLM that reads attack data and tells you where to strike next. In this talk I show what it can do, where it fails, and what that gap reveals about the future of offensive security. Every tool is free, every concept is reproducible, and the answer to the title question is more interesting than you expect.</abstract>
                <slug>wiccon-2026-182-the-end-of-human-pentesting-</slug>
                <track>Talks</track>
                <logo>/media/wiccon-2026/submissions/DEJSUZ/end_of_pentester_q3xMG1k.png</logo>
                <persons>
                    <person id='171'>An Van Leuven</person>
                </persons>
                <language>en</language>
                <description>Everyone is asking whether AI will replace hackers. Most answers come from vendors selling platforms, analysts writing reports, or defenders worried about their budgets. This one comes from someone who actually built the thing and ran it against real targets.

The results are unsettling in ways nobody is talking about yet. Not because AI is as good as the pitch decks claim, but because the gap between what it can do and what it cannot do reveals something important about where offensive expertise actually lives in 2026.

This talk is practical, opinionated, technical and built on real experience. You will leave knowing exactly which parts of your workflow to hand to a machine, which parts to protect fiercely, and why the most dangerous person in the room is not the one with the biggest toolset.

Come with curiosity. Leave with a new way of thinking about what it means to be a hacker today.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/DEJSUZ/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/DEJSUZ/feedback/</feedback_url>
            </event>
            <event guid='486f7449-a593-5be3-98cb-71fa46ba3b02' id='229'>
                <room>Main Hall</room>
                <title>I jailbroke a scam bot with 1 prompt, and so can you</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-30T13:30:00+01:00</date>
                <start>13:30</start>
                <duration>00:50</duration>
                <abstract>Getting an LLM to spill its secrets is a subtle artform, part social engineering of the application, and part social engineering of the humans (and other LLMs) who built it. It&apos;s witchy magic that&apos;s both gentle and assertive: you ask nicely to stay under the abuse radar, then tell the bot to step outside its role entirely. 
In this talk I&apos;ll walk through what I&apos;ve learned testing LLMs across chatbots, lifestyle assistants, and enterprise tools - from leaking system prompts and hunting indirect, no-authentication prompt injection, to chaining an AI&apos;s own &quot;legitimate&quot; tools into something destructive. I&apos;ll cover real attacks like using the AI&apos;s own tools to ransom a company, turning connected integrations into exfiltration channels, and the crossover where this all starts to look a lot like traditional web application testing. They told us SQL injection was dead, and we just reimagined it, gave it a new name, and pointed it at the model. 
Expect practical techniques, a healthy respect for how confidently these systems lie, and a reminder that organisations need people who think this way because people with worse intentions are already doing it.</abstract>
                <slug>wiccon-2026-229-i-jailbroke-a-scam-bot-with-1-prompt-and-so-can-you</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='15'>Yianna Paris</person>
                </persons>
                <language>en</language>
                <description>Modern LLM deployments aren&apos;t risky because of the model - they&apos;re risky because of what the model is connected to and how we try to put guardrails around them. You no longer have to imagine a machine with agency over your emails, calendars, Slack, Jira, Confluence, and GitHub because we already live in that reality. I explore how these systems delight users with unexpected solutions, and how users become comfortable (or fatigued) with giving more and more access. The moment a system can read untrusted content, access private data, and communicate externally, you&apos;ve got indirect prompt injection as a feature no matter how well-aligned the model is. I&apos;ll walk through how malicious instructions get in and how stolen data gets out through those same integrations.

Then we&apos;ll get to the part I find most interesting: you often don&apos;t need to make the model do anything obviously malicious. Each legitimate tool an LLM has like a code execution sandbox, file access, crypto functions, and web requests become the capabilities we take advantage of. Chain them in the right order and you get outcomes the developers never imagined. I&apos;ll cover sequential tool-chaining attacks, where individually harmless steps add up to data held hostage.

I&apos;ll also spend time on the things that make this work in practice. Why a prompt that fails ninety-nine times succeeds on the hundredth, is still a vulnerability. And why you should treat everything a bot tells you about itself as a lead, never a fact, because LLMs &quot;hallucinate&quot; information about themselves, and lie with total confidence.

You&apos;ll leave with concrete testing and design techniques you can use the next time you&apos;re handed an AI-powered application and asked whether it&apos;s safe.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/DGAYA3/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/DGAYA3/feedback/</feedback_url>
            </event>
            <event guid='726ae3bd-6e94-5bbb-9b25-4cdd7c0f6566' id='225'>
                <room>Main Hall</room>
                <title>The largest social engineering attack ever? The hidden effects of AI on the human mind</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-30T14:30:00+01:00</date>
                <start>14:30</start>
                <duration>00:25</duration>
                <abstract>Social engineers aim at one target: a human whose judgement has gone offline. They pull known levers, like authority, liking and urgency, to make their target compliant. Generative AI frequently pulls the same levers, whether by design or accident, while slowly eroding the very skills we would use to protect ourselves. Coming at this from an odd mix of social engineering, a year of psychology, some basic knowledge of tradecraft, and the AI work I do now, I will lay out the eerie overlap between long-game social engineering and everyday LLM use, the research on how it erodes human skill and what it does to our judgement. While cyber security&#8217;s usual defences were built for louder, one-shot attacks, tradecraft may have some useful techniques that could apply here.</abstract>
                <slug>wiccon-2026-225-the-largest-social-engineering-attack-ever-the-hidden-effects-of-ai-on-the-human-mind</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='217'>Monika Stewart</person>
                </persons>
                <language>en</language>
                <description>Besides my daily work as a data and AI consultant I have a handful of eclectic interests: a hobby level interest in social engineering, a single course in tradecraft and a year of psychology. Lately I noticed an overlap I had not expected. 

As cyber security experts know, humans are a great attack surface, and social engineering can be an incredibly effective attack. There are the corporate clich&#233;s of the classic phishing email, or the phone call from a very polite supposed customer with a really urgent issue and maybe a screaming infant in the background. Then there are the classic consumer facing attacks, like calls from someone impersonating a loved one who urgently needs money, or &#8220;Windows&#8221; calling your grandmother personally to help with that unknown danger on her computer.

What gets talked about far less is long-game social engineering. Slowly gaining someone&apos;s trust, building rapport over time. Bit by bit their opinions start to carry weight, they start to matter to you, and you find their input invaluable. In the corporate world this may be a new coworker playing a long game and has a surprising amount of overlap with some parts of tradecraft. So where is the overlap with AI? Strangely large language models have been pulling a lot of the same levers in their large customer base for a while now. While the goal is unclear there is the classic large scale gathering of information, the winning of trust through manufactured authority, the relationship building through sycophancy, and manufactured urgency (largely from 3rd parties) to &#8220;adopt AI now to boost your productivity&#8221;. 

What we end up with are study after study on the effects of long-term AI use on human thinking, human skills, human isolation, and in the most extreme cases reported AI psychosis. I am not claiming there is some big conspiracy underfoot. I am pointing out that the disproportionate effects LLMs are having on people may lie in the disproportionate overlap their behaviours have with known techniques from social engineering and tradecraft for the explicit manipulation of humans. I will also touch on some old-school intelligence methods for keeping human judgement intact under surprisingly similar kinds of pressure.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/ZU83AN/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/ZU83AN/feedback/</feedback_url>
            </event>
            <event guid='a520837d-abde-5267-a7af-05077d25259f' id='186'>
                <room>Main Hall</room>
                <title>What Negotiation Chats Reveal About Ransomware-as-a-Service</title>
                <subtitle></subtitle>
                <type>Talk - 50 minutes</type>
                <date>2026-10-30T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:50</duration>
                <abstract>Ransomware is no longer the work of isolated hackers, but an organised criminal ecosystem operating on a service-based model. This talk explores the realities of ransomware-as-a-service (RaaS), where developers, affiliates and negotiators work together to deliver attacks. Using real data from ransomware leak sites, including ransom notes and negotiation chats, I&apos;ll examines how these groups operate and the psychology behind their attacks. The talk cuts through common misconceptions and shows why organisations should be more prepared than ever.</abstract>
                <slug>wiccon-2026-186-what-negotiation-chats-reveal-about-ransomware-as-a-service</slug>
                <track>Talks</track>
                <logo>/media/wiccon-2026/submissions/PSBEKS/1000117847_SsivRe8.jpg</logo>
                <persons>
                    <person id='179'>Becky Stacey</person>
                </persons>
                <language>en</language>
                <description>During my placement at the West Midlands Regional Cyber Crime Unit within West Midlands Police, I gained first-hand insight into the realities of ransomware incidents and became particularly interested in how modern ransomware groups operate less like isolated hackers and more as sophisticated criminal enterprises. This talk draws on research I have conducted into ransomware-as-a-service (RaaS) groups, including analysis of victim leak sites, ransom notes, and real negotiation chats associated with groups such as Scattered Spider and Akira.

The presentation will explore what negotiation chats reveal about extortion tactics and the use of human psychology to apply pressure during incidents. Using a real negotiation case study, I will highlight indicators of manipulation and operational structure within these groups. The talk will also challenge common misconceptions about ransomware and show how understanding attacker behaviour can strengthen organisational preparation. It will conclude with lessons for organisations on response planning and reducing the impact of ransomware attacks.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/PSBEKS/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/PSBEKS/feedback/</feedback_url>
            </event>
            <event guid='11c0435f-0ad3-5650-bde0-9325a77792f5' id='219'>
                <room>Main Hall</room>
                <title>The Attacker Posted First: The Breach Wasn&apos;t the Expensive Part</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-30T16:30:00+01:00</date>
                <start>16:30</start>
                <duration>00:25</duration>
                <abstract>During a major cyber incident, who actually controls the story? Increasingly, it&apos;s not the victim. Threat actors have figured out that narrative damage, like reputational collapse or a stock price in freefall, can hurt worse than the breach itself and it can be built in parallel to the attack. By the time legal has cleared a statement, the attacker may have already spread a confident, detailed account of catastrophic impact, and the media has run with it.</abstract>
                <slug>wiccon-2026-219-the-attacker-posted-first-the-breach-wasn-t-the-expensive-part</slug>
                <track>Talks</track>
                
                <persons>
                    <person id='211'>Ieva Salnaite</person>
                </persons>
                <language>en</language>
                <description>This talk looks at case studies like the 2014 Ukraine elections and the 2023 MGM Resorts breach to discuss how cyber operations and narrative attacks can get synchronized on purpose, asking who in your crisis structure is actually responsible for closing that gap.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/9DDU73/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/9DDU73/feedback/</feedback_url>
            </event>
            <event guid='53a50931-7700-50b4-84b4-5c10a7a7b75e' id='251'>
                <room>Main Hall</room>
                <title>WICCON Closing</title>
                <subtitle></subtitle>
                <type>Talk - 25 minutes</type>
                <date>2026-10-30T16:55:00+01:00</date>
                <start>16:55</start>
                <duration>00:05</duration>
                <abstract>WICCON Closing</abstract>
                <slug>wiccon-2026-251-wiccon-closing</slug>
                <track>Talks</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/ZBZKTR/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/ZBZKTR/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room' guid='68f47131-6986-5eb4-81ea-4c87ce675da0'>
            <event guid='1bc07fea-ca51-5967-aecc-f3cebf1b5166' id='185'>
                <room>Workshop Room</room>
                <title>CTF introduction workshop with Challenge the Cyber</title>
                <subtitle></subtitle>
                <type>Workshop 120 minutes</type>
                <date>2026-10-30T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>02:00</duration>
                <abstract>Get to know the Capture the flag (CTF) game without stressing out!
In this workshop, we&apos;ll look at a couple of examples of CTF categories. After a short tech introduction, you&apos;ll practice solving a challenge. You can work togethere, there&apos;s people to help, the only thing you need to do is be brave and start hacking!</abstract>
                <slug>wiccon-2026-185-ctf-introduction-workshop-with-challenge-the-cyber</slug>
                <track>Workshops</track>
                
                <persons>
                    <person id='7'>Maja Reissner</person><person id='238'>Danique Lummen</person>
                </persons>
                <language>en</language>
                <description>Get to know the Capture the flag (CTF) game without stressing out!
In this workshop, we&apos;ll look at a couple of examples of CTF categories. After a short tech introduction, you&apos;ll practice solving a challenge. You can work togethere, there&apos;s people to help, the only thing you need to do is be brave and start hacking!

We&apos;ll use challenges that have been used in former national Challenge the Cyber competitions.
Probably of the following categories:
- networking
- reversing
- crypto</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/AJBMFK/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/AJBMFK/feedback/</feedback_url>
            </event>
            <event guid='781f2732-dc7f-5ac8-af09-c7aa64c50f11' id='216'>
                <room>Workshop Room</room>
                <title>LLM Hacking and Latest vulnerabilities on AI agents - OWASP Top 10 for LLM Applications</title>
                <subtitle></subtitle>
                <type>Workshop 120 minutes</type>
                <date>2026-10-30T13:30:00+01:00</date>
                <start>13:30</start>
                <duration>01:30</duration>
                <abstract>LLMs are already in your products, your workflows, and your infrastructure. But are they secure? Probably not &#8212; and attackers already know it.
This workshop walks you through every vulnerability in the OWASP Top 10 for LLM Applications (2025), with real-world examples that will make you uncomfortable in the best possible way. You&apos;ll get hands-on time with a live hacking platform built specifically for this session, so you don&apos;t just watch &#8212; you do.
We&apos;ll close out by exploring AI agent vulnerabilities, the emerging threat category that&apos;s changing everything we thought we knew about application security.</abstract>
                <slug>wiccon-2026-216-llm-hacking-and-latest-vulnerabilities-on-ai-agents-owasp-top-10-for-llm-applications</slug>
                <track>Workshops</track>
                <logo>/media/wiccon-2026/submissions/HV9H9C/LLM_HackingAI_Agents_P9946Mm.jpeg</logo>
                <persons>
                    <person id='209'>Anca Maria Capota</person>
                </persons>
                <language>en</language>
                <description>LLMs are no longer experimental &#8212; they are embedded in production systems, customer-facing products, and critical infrastructure. And yet, the security community is still catching up to what that actually means in practice.

This workshop is designed to close that gap.

We&apos;ll work through the complete OWASP Top 10 for LLM Applications (2025 edition) &#8212; not as a checklist, but as a hands-on investigation. Each vulnerability comes with real-world context, a live demonstration, and the kind of technical depth that turns awareness into action.

But knowing isn&apos;t enough. That&apos;s why participants get access to a purpose-built hacking platform &#8212; a safe, interactive environment with no complex setup designed specifically for this workshop &#8212; where you can move from observer to attacker and experience each vulnerability firsthand.

In the final chapter, we go beyond the OWASP list entirely. AI agents are introducing a new class of vulnerabilities that existing frameworks weren&apos;t built to handle. We&apos;ll look at what makes agentic architectures uniquely dangerous and discuss what defenders and developers need to start thinking about right now.

Whether you&apos;re a security professional trying to stay ahead of the curve, a developer building on top of LLMs, or simply someone who wants to understand the risks before they become incidents &#8212; this workshop was built for you.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.wiccon.nl/wiccon-2026/talk/HV9H9C/</url>
                <feedback_url>https://program.wiccon.nl/wiccon-2026/talk/HV9H9C/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
