Joining Tom this time are Jules Wouters, Solutions Engineer at TrendAI, and Joris Rooijackers, Solution Consultant Security at Bechtle. In their work, they regularly encounter organisations that feel confident in their security posture, only for a closer look to reveal gaps and vulnerabilities. Their advice is simple: start with the business processes you want to protect. From there, you can determine which security measures are required and how to verify that they will perform when it matters most.
In the podcast, Joris talks about the risk of taking security at face value. Organisations often point to certifications, security products or a Security Operations Centre (SOC) as evidence that everything is under control, even though a closer assessment may reveal vulnerabilities that have gone unnoticed for years.
Joris explains: “But when we carry out an assessment at Bechtle and look beneath the surface, we regularly uncover shortcomings. Those weaknesses were already there, they just hadn’t yet become a reason to take action.” Assessments help turn those issues into something tangible enough to discuss improvements, priorities and budget.
That confidence isn’t always the result of complacency, however. Jules also works with organisations where security is just one of many responsibilities carried by an IT generalist. As he explains: “That person is expected to keep systems running, support users and stay on top of constantly evolving attack techniques at the same time. That requires more time and specialist knowledge than most organisations have available. Buying a security product is one thing, but continuously assessing whether it remains configured to address current risks requires ongoing attention.”
The attack scenario discussed by Joris and Jules shows why the initial login is only one part of the security story:
- An attacker obtains a password,
- poses as a member of the IT team over the phone,
- persuades the user to approve a second authentication factor,
- and gains access to an account that was never intended for them.
Training remains essential, Jules stresses. “At the same time, you have to assume that, under pressure, an employee may make the wrong decision. The real question is what an attacker can do with that account afterwards and which data become accessible as a result.” Unusually high levels of record access within a short period, for example, could indicate that something isn’t right.
That’s why Jules emphasises limiting access rights to what people genuinely need to do their jobs, while Joris highlights the importance of detecting and containing unusual behaviour. “An employee may legitimately need access to large volumes of customer data, but accessing all of it one record after another should raise concerns.”
Looking at security through this lens makes the discussion about human behaviour far more tangible. Beyond training people to recognise suspicious emails, messages and phone calls, organisations should also examine the impact a single compromised account could have, bringing access management, application design and threat detection together.
Attacks rarely stay within the boundaries of a single security solution. They may start with a phishing email before moving to an endpoint and spreading further through the environment, leaving security teams to piece together the full picture when each tool only shows part of the story.
That’s where Extended Detection and Response (XDR) comes in:
- XDR collects and correlates data from multiple security layers, including email, endpoints, servers, cloud environments and networks.
- This enables security teams to investigate patterns and relationships that may be difficult to spot when alerts are viewed in isolation.
- The data sources included ultimately depend on the platform and how it has been configured.
According to Joris, a broader view makes it much easier to investigate other parts of the environment when suspicious activity is detected. “When suspicious activity appears in one area, you can immediately investigate whether related activity is occurring elsewhere as well. That makes it much easier to recognise when seemingly separate events are actually part of the same attack. An alert only becomes meaningful when you can see both what led up to it and what happened afterwards.”
This changes the way organisations should evaluate security tools. Beyond the capabilities of an individual product, it’s important to understand how well it contributes to a complete view of your environment. What information is still missing? And who investigates when multiple signals point to the same attack?
In the episode, Jules refers to a dwell time of 22 days. Dwell time measures the length of time an attacker remains in an IT environment before being detected. That figure comes from Mandiant’s M-Trends 2024 report and reflects the median dwell time for incidents investigated across Europe, the Middle East and Africa in 2023. It should not be interpreted as an average for every attack.
More recent figures are now available. M-Trends 2026 reports a median dwell time of 14 days for incidents investigated globally in 2025, compared with 11 days the previous year. According to the researchers, some attackers aim to create immediate impact, while others focus on remaining undetected for extended periods.
These regional and global figures cannot be compared directly. Nor should dwell time be viewed as a window during which an organisation can afford to relax. What matters is whether your organisation can detect and contain suspicious activity before it escalates, because valuable data may already have been stolen or damage may already have been done long before an attack is discovered.
Greater visibility only matters if you're able to act on what you see. According to Jules, the real challenge lies not just in detection, but in response as well. “Once suspicious activity has been identified, someone still needs to determine what happened and decide what action should be taken.” That requires clear processes that go far beyond simply forwarding an alert.
- Who investigates the alert?
- Who is authorised to block access or isolate a device?
- When should the owner of the affected business process be involved?
Jules explains: “These are decisions you want to discuss in advance, especially when taking action could also affect business operations.” It’s one reason why interest in managed security services and security platforms continues to grow. “Specialist support can make all the difference when you don’t have sufficient expertise or capacity in-house.”
If you work with an external provider, it's important to agree in advance who does what and which decisions remain the responsibility of your own IT team. AI can help by identifying signals more quickly and analysing events faster, but it doesn’t remove the need for specialist expertise.
“I believe there will always be a human element involved,” says Jules. “Someone still needs to assess the situation, and you need to understand the impact any action could have on your organisation.”
Which risks deserve your attention first? Jules keeps it simple: “Start with your critical business processes. Identify where disruption would hurt most and align your security efforts accordingly.”
Together with the owner of a critical process, review one key service or business activity:
- Which systems and data does it depend on?
- Who has access to them?
- What happens if that access is misused or the service becomes unavailable?
Those answers make it much easier to identify where additional security measures or investigation are needed. Joris recommends starting with your assets and verifying that your inventory is complete, because, as he points out, “It’s easy to overlook a system you don’t know exists. That’s why asset inventory matters at board level as well. It provides visibility into the systems your business depends on.”
The next step is to involve Finance and senior leadership in the discussion. IT can identify vulnerabilities, but deciding how much risk the organisation is willing to accept requires a broader conversation. Jules regularly sees organisations making security more expensive than it needs to be. “For example, by failing to make choices based on their actual business risks.” He also sees organisations reducing costs by adopting a security approach that better matches their needs and risk profile. Effective investment starts with understanding which risks you’re trying to reduce.
Assessments, penetration tests and tabletop exercises can then be used to challenge assumptions. The key is choosing a method that matches the question you want answered. Document the outcomes, assign ownership for improvements and define how success will be measured afterwards.
Joris concludes: “Even if you have a great deal of confidence in your security posture, exercises like these still provide value. No matter how mature your security may be, it always pays to keep challenging it.”
Ask yourself this: If an account with access to a critical business process were compromised tomorrow, who would notice and who would take action?
XDR & Security – Hip or Happening?
In the podcast series Hip or Happening?, we explore whether an IT development is merely attracting attention or already delivering tangible value, accompanied by the Bechtle Beat, the rhythm of innovation. Listen to the episode and hear Jules and Joris share their insights into detection, response and the decisions that help organisations build resilience.
Would you spot an attack on a critical business process and know how to respond before serious damage is done? Use our Cyber Resilience Checklist to identify which security controls have been proven effective, where gaps still exist and what requires further validation. The checklist helps distinguish between actions your IT team can take directly and decisions that require input from management, Finance and business stakeholders, while providing a practical framework for documenting findings, assigning ownership and capturing next steps.