Chat with our experts on Security Operations (SecOps)

Feeling overwhelmed by everything involved in managing security operations? Security Operations (SecOps) plays a vital role in helping organizations prepare for, detect, and respond to cyber threats. It goes far beyond monitoring and alerting. From penetration testing and red teaming to incident response, SecOps teams are deeply involved in both offensive and defensive aspects of cybersecurity.

To offer a behind-the-scenes look at what SecOps truly involves, we spoke with our specialists, Shawn Vervaeke. In this interview, he shares real-world insights into typical engagements, from testing systems for vulnerabilities to supporting clients through ransomware and data breach scenarios. 

It all starts with the scope the client provides. There are different levels of information we might get, from black box to white box testing. With black box testing, we receive almost nothing - maybe just a domain name, but no credentials or background information. When it’s grey box testing, we get some user accounts and a few endpoints. This helps save time and lets us test beyond just the login screens, like what lies behind them. With white box testing, we get full access: detailed infrastructure information, multiple user roles, and system endpoints.

Regardless of the type, we always aim to deliver a clear and accessible report at the end - not just for technical teams, but also for management. The management summary is especially important to help non-technical stakeholders understand the risks.

Depending on the assignment, we work either remotely or on-site. The scope and information provided by the client guide how we approach the test and how we structure the final report.

Shawn Vervaeke, Senior Advisor, Enterprise Risk Services

For me, the most memorable assignment was a recent penetration test for a foreign government agency. We were given access to test one of their custom-built applications. Not only did we find some notable issues, but we also got to perform a re-test, which showed how much value we added.

What made it exciting was that we uncovered several zero-day vulnerabilities, previously unknown security flaws that had not been detected until now - even though the client thought their system was secure. Once we shared the findings with the vendor, even they were shocked. These were critical issues that could have had a major impact. It was one of those projects where the time was short, but the results were very meaningful.

Yeah, on my first day I was just exploring the office, and by the end of the first week, I was already involved in a real project. During our internship, we had already been attending some meetings at the SecOps lab, so we were somewhat familiar with the work. And because many of the technical questions could only be handled by the SecOps managers, we knew this was the kind of team we wanted to be part of.

After several years in the team, we’ve built up solid hands-on experience across a wide range of projects, from penetration tests to complex incident response cases. As the team continues to grow, there’s always room for more technically driven professionals to join us. People with certifications or deep expertise are a great asset, but we also value those who bring curiosity, a strong foundation, and a willingness to learn.