Back in 2023, there was this question: what if we had an open space conference in the cybersecurity space, that's open for everyone interested? This idea came to life with osco, the Open Security Conference. The first event was an experiment to see if other people felt that this gap was worth filling. People showed up at our little conference and liked it, so we continued. The second edition helped us understand better if more people would be willing to make that leap of faith and join this new open space conference focused on cybersecurity. They did indeed, and started telling more people about osco, helping us spread the word. Now we just had the third Open Security Conference and we knew it would be the decisive one. Would the wider community support this initiative, hence allow us to move into a sustainable future and establish osco for the long run? We were at a crossroad. I can't tell you how incredibly happy I was when participants showed us this year that there's clear demand, interest and appreciation. osco is here for the long run! If this sounds intriguing to you, you can already save the dates for next year (7 - 10 October 2027) and pre-register to get informed once the official registration opens.
All of us organizers are also active participants in this open space conference. So here's my personal experience report of osco26.
Preparing for a Good Start
Some of us organizers arrived a day ahead of the conference. It was lovely to check in with those folks again in person, having talked with them basically every week of the year remotely. We had a nice dinner together and just enjoyed each other's company. We clarified a few last things with the venue, we aligned on the last tasks, we prepared some material already for the next day.
After a good night's sleep, we continued in the late morning with further preparations. It was pretty calm; all things had been agreed and aligned on beforehand anyways. With lots of helping hands everything could be done quickly. Just like the last years, once things were ready, it felt like there's a lot of time ahead before the official start. Then you blink, and suddenly people are coming and now the busiest period starts. Welcoming folks, registering them, explaining which options they have to indicate certain things like photo consent, and ensuring they can now settle in and join first conversation with the community. I really enjoy this part and yet it's also pretty taxing. Good thing is that we're a way bigger team this year compared to last year, and while there's still room for improvement, we could share the load a lot better already.
From participants' side, I just loved seeing both alumni and new folks I haven't met yet. We had a whole variety of roles represented: from people working in security roles like AppSec engineers, penetration testers, security consultants and CISOs, to people working in other tech roles like developers, system administrators, DevOps folks and more, to people who either work in non-tech roles or who are still students. Diversity also showed up in various other factors, perceivably more than the previous years. All of it fit well to what we want to see osco become.
Time for dinner. The venue is not only in a beautiful location and generally a nice place to be, it also offers really tasty food and caters to the various needs of participants. For me it had to be a quick meal that evening, as my next duty was to officially open the conference together with Kristof Van Kriekingen. And we did! This year, the number of participants had once again grown, and we had the biggest room of the venue booked for everything - which also offered a pretty nice atmosphere to kick this off. We welcomed everyone and explained how we're going to do things over the next days, crafting this space together and attempting to make it a pleasant and insightful experience for everyone.
I had the pleasure to introduce our first keynote speaker, Stephanie Carstensen, telling us about "The Day Everything Stops: Preparing for the Cyber Crisis You Hope Never Comes". She painted a challenging scenario: you're working in the operational technology (OT) domain in the industrial sector. There is a ransomware attack. What do you do? The answer is far from straightforward and will differ in each specific context for each specific time. The stakes are high as any move you make might endanger the safety of people - at the same time you have to make decisions. The important part is to have this conversation and practice the scenario in a crisis simulation before you have to make those seemingly impossible decisions in the heat of the moment. It's crucial to foster a safe space, though - as only then we can raise uncomfortable questions, acknowledge our own uncertainty, being okay with not having the right answer. I loved how Stephanie emphasized that an exercise is only useful if something changes so we need to go from observations to capability. The difference is not better people - it is prepared people. What can I say, I knew Stephanie would rock this and she absolutely did! The perfect opening for osco, as it raised awareness on a field people might not be too familiar with, had folks question how things are in their own environment, and made people want to know more how to prepare themselves for crisis situations.
Jahmel Harris followed as our second keynote speaker and it was my honor to introduce him as well. His keynote shone a light on "Building a Penetration Testing Lab in 2026". Jahmel took the audience down memory lane, showing where he started building home labs and taking us with him to where he is now. He made very clear that each home lab will look different for very good reasons, there's not one definition of good. It depends a lot on your actual use case. If you only need to lab to practice your skills, it won't need as much. Yet if you do professional penetration testing on mobile apps or IoT devices, the requirements change a lot. For cloud services you need respective networks and segmentations - client data must stay separate from your home network and devices. And if you're into malware analysis, things change once again. Jahmel also showed us how things evolved over time. Virtualization, containers, networking, hardware - but prices increased heavily too, like for energy. Licensing changes impact things. Scope creep is way harder to prevent as there are so many things to train on these days. From Jahmel's perspective the requirements for a modern penetration testing lab are that it is separate from your home network, it can run malicious code and vulnerable software, has enough storage and RAM, and is easy to reconfigure. He emphasized that network segmentation is the most important part. Think of the network zones to have and have all of them as different virtual networks.
The day was long but not over yet. Conversations continued in the bar, first games were played, people letting things sink in. I would have wished to join them already that night, yet a few more organizing tasks kept me from it. As shared, the first day is always the busiest from organizer point of view.
Open Space Day 1
The first full conference day started with an introduction to what an open space means and how we co-create a space that offers value, agency, and a welcoming learning environment for everyone. Then it was time for the first marketplace of ideas. This is the place where people think about sessions they want to host and briefly present them, so folks know what it's going to be about to build up their own schedule. Sessions could be anything, ranging from more classic "push sessions" like talks, workshops or an ask me anything, to "pull sessions" like where the host could ask participants for help on a challenge, or invite people to a knowledge exchange or discussion, or try out a tool together, do an exercise, and so on. Sessions could also be any place outside of this spectrum like going for a walk and talk, doing sports together, flying kites, ballroom dancing, you name it. This kind of variety and freedom is part of the beauty of open spaces. Usually, a lot of valuable insights come out of more informal sessions that most likely would have never entered a more traditional conference program.
Here are the sessions I chose myself on this first day.
- "Security Card Game" by Martin Schmidt and me. Well, we definitely missed the third in our little group, Philipp Zug. Together, we had developed a card game to raise awareness on all too common security issues and at the same time have people practice decision making on what to do with those issues. Not every scenario is alike and would lead to the same decisions - and as the game is played collaboratively, you also have to align on which strategy and tactics to use to reach the goal. In this session, Martin and I explained the game and had the group play a full round together. We encouraged them to give feedback and share ideas as we continuously try to make this little side project better. And indeed, we gained a bunch of new insights from participants!
- "Smart Adult Toys" by Kristof Van Kriekingen. Kristof is heavily invested in security, penetration testing, OSINT and more. And every talk I heard of him was not only eye-opening but also pretty scary - in the way that makes you change your behavior. This time, Kristof talked about his free time endeavor to test adult toys that were connected to the internet, for example to be controllable remotely. You can already imagine how sensitive this whole topic is and also how safety-relevant the quality and security of such toys are. Unfortunately, a lot of them are really lacking in exactly those aspects, even for very basic things. Even more scary: a full year after Kristof reported his findings to the respective company, the issues are still not addressed.
- "LLM Destroyed My Team" by Martin Schmidt. Martin invited all of us to reflect on changes we've observed in our teams due to the usage of LLMs. I loved that he made this very inclusive by granting us time to think first in silence before sharing our experiences and by making sure every person has the opportunity to voice their thoughts. It was really interesting to hear each other's perspectives on how things didn't change for the better and how people struggle with the behavior of others. Like literally having the LLM answer everything, refusing to learn themselves. What I've seen myself is that written communication became super verbose and that more and more overengineered solutions came up just because they could. People also shared what they found to be working in this situation, like focusing more on refinements and general collaboration with humans.
- "Security Champions Knowledge Gathering" by Mireia Cano and another person (I'm refraining from naming folks where I'm unclear whether they are okay to be named). This was a cool session exchanging experience and knowledge on all things security champions programs. As I was a security champion myself back in the days and as we happen to have our own program running in my company, this was a clear pick for me to learn what else we should consider doing. We talked about cornerstones of such programs like how many champions per team, are these volunteers or was it mandated. We talked about how many live sessions you have with champions, at which cadence, how to provide the content. How to interconnect champions in a community, how to show and measure value. Culture change was a big theme and also purpose for such programs, so was management buy-in, training budget, rewards and incentives for champions. Mireia shared an interesting model: 20% of champions will be super active, 60% interested, and 20% absent - and we're trying to reach the 60%.
- "Capture the Flag Together (Beginners Edition)" by me. What can I say, I just love hosting these sessions. Introducing folks to what flags stand for, how to practice safely, and also get them get their hands on trying this out together. I do those exercises in a collaborative way as a big ensemble, with me being the hands at the keyboard for everyone. It's fun as it's a puzzle to solve. It's educational as you encounter new tools and especially new thinking approaches on finding out more information about a target to break into and exploiting its capabilities to do so. It's enlightening as more often than not you experience the reasoning behind defensive measures like input validation and why it's important to get it right. This time, the group was a nice mix of folks, all interested in figuring this out and learning together on the way. As we had a hard time limit, we didn't get the flag immediately in this session - it had to wait until the evening.
Speaking of the evening. We ended the first day sessions with an evening news round. Folks offered thoughts on what they learned, what they appreciated, what surprised them. Then it was time for another round of marketplace, this time for either evening or early morning sessions - after dinner, before the official marketplace of the next day. I just loved seeing people propose lots of awesome things. We had a magic tricks session, boardgames (a classic!), lock picking, playing with radios, and more. I proposed the sequel to the afternoon's capture the flag session - I wanted to find closure on the unsolved challenge. After a really nice dinner and a short card game round, it was time for this session. Lots of folks returned and wanted to continue as well! We also had others join in, and after we solved the first challenge, we started a bigger, more difficult one. It's always fascinating how many other people also enjoy doing this for hours in the middle of the night. The group was great and it was super cool to see people coming from different backgrounds and different roles, like developers, penetration testers, students, ops folks and more, all sharing their knowledge and ideas. No one had the solution on their own, everyone had contributions to find all the pieces of the puzzle. I had an awesome time, and we indeed managed to crack the other machine as well and capture those flags together. Finally, time to go to bed! Another full day was waiting for us ahead.
Open Space Day 2
Another marketplace brought us a bunch of new awesome sessions. It's always cool to see when people who had never been to an open space conference before already dare to host their own sessions on the second day. Happened here as well! Once again, it wasn't an easy choice which sessions to join, yet here's what I picked when organizer duties allowed.
- "How to osco" by all of us osco organizers. We already hosted such "ask us anything / behind the scenes" sessions on the conference the last years. We had gained great feedback and learned about the ideas people had, while they gained insights on how we do things, which choices we made, what are our plans for the future. This year, we wanted to do the same again, and once again people came and asked curious questions and shared their thoughts. Thanks to everyone who came! We took in all the feedback (along with other sources we gathered throughout the conference) and will consider what we can do for the 2027 edition to make it once again a bit better than the last one.
- "Stop Judging and Tear Down Your Gates – Make Humans the Strongest Link in Security" by me. I've recently given this talk at BREWTCON and I was scheduled to do it again at Agile Testing Days. So I felt, why not do another run at osco and see how it lands with this mix of an audience? I was glad to see it inspired a very engaged, long discussion after the talk. Huge thanks to everyone who shared their thoughts, it was invaluable for me to see that the talk indeed got people thinking!
- "Security in OSS". This was a great talk on the intersection of two all too important topics: open-source software and the Cyber Resilience Act (CRA), and how both are and are not related. I loved that they walked us through the current situation regarding open-source, including what organizations should do, what hinders contributions, and what challenges the community faces. They introduced people to the CRA, how open-source software is mostly out of scope while there are still some aspects to consider and be mindful of.
- "Threat Modelling for Dummies". This was a really cool group exercise of thinking out loud together on a real MCP server scenario. Interestingly, the crowd was tempted to jump to solutions before understanding the context well enough. Yet once established, we gathered lots of interesting scenarios what could go wrong. Guess what - MCP servers are basically an API and need to be secured as such.
- "Threat Modelling Game" by Claudius Link. Claudius had offered sessions about security games in the past and I was glad he did so again at osco26. This time, he brought the Elevation of Privilege game in its classic and the machine learning variants. I've read a lot about this game for years yet this was finally my first chance to actually play it. We chose the collaborative mode and worked on a classic scenario. I really liked that it included some background and context of already known weaknesses, which made it a lot more accessible and tangible to use as a practice case when it's not our own system. The game did indeed inspire great conversations in short time!
The day passed super quickly. It was already time for the official conference closing and retrospective. I really enjoyed that it allowed us to reflect together on what we will take with us from the conference and that we could exchange those thoughts with other participants. We also gathered lots of feedback on the conference that will serve us well when preparing the next edition for 2027.
While this was the official closing, of course there were still more evening and morning sessions to be held, more conversations to be enjoyed! Also this evening, lots of different things took place. From Powerpoint karaoke to ballroom dancing, people just enjoyed their time. I had been asked earlier that day whether I'd be up for another round of "Capture the Flag Together" - and how could I say no to that! So we gathered once again; both folks who'd been there the last days as well as people who tried their hands on it for the first time. We tackled another machine, learned even more and managed to capture the respective flags together. Such a nice closing for the conference for sure!
Departure Day
At first, you think you have a lot of time to talk with everyone, do a lot, still check this other thing out - and then suddenly it's already time for final goodbyes. The morning was slow and smooth with last conversations and informal sessions. Like a game evolution proposal session offered by a kind person on Martin's, Philipp's and my security card deck game - we're super grateful for the ideas and excited to level up the game in a whole new manner!
After cleaning up things and handing over the conference room keys to the venue, we enjoyed a last lunch together with everyone who had a shorter trip and hence could leave later. One more time to share stories and stay in the osco spirit for a while longer. We finally departed - and while the train ride home took way longer than expected, it was still nice to share this last leg with Martin and Mireia.
Then osco was indeed over. The third edition was a success - so it won't be the last one! Is there room for improvement? Of course there is and we have lots of feedback and ideas. Yet we could see this initial idea has now become a real place for folks and we're happy to hereby establish this new conference on the block. I'm thankful for all my fellow organizers and for what we've built together. Yet that place wouldn't live without participants. We're really grateful for all of you and can't wait to have you again next year!