When regulatory guidance around security shifts into statutory law, companies tend to rethink their policies in similar ways. Security teams upgrade their technical defences and executive boards want clarity on what compliance means in practice. Yet as the European Union’s Cyber Resilience Act (CRA) moves into enforcement, relying solely on technical controls may leave organisations overlooking important people and process challenges.
On 11 September 2026, the CRA’s mandatory reporting rules became operational. Manufacturers of digital products covered by the Act, including UK companies that export to the EU, must now report actively exploited vulnerabilities and severe incidents affecting the security of those products. An early warning must be submitted within 24 hours of becoming aware of the issue, followed by a more detailed report within 72 hours. The broader cyber security requirements of the CRA will apply from 11 December 2027. Failure to comply carries heavy administrative penalties of up to €15 million or 2.5% of total worldwide annual turnover.
While the 24-hour requirement applies to vulnerabilities and incidents affecting products within the scope of the CRA – not to ordinary employee-driven incidents such as an employee clicking a phishing link – it marks a useful opportunity for security leaders to assess how prepared their organisation is to identify and respond to potential issues.
Many CISOs will view this reporting window as an engineering benchmark, asking whether their incident response strategies and vulnerability scanners can flag a breach and raise an alert in a day. But that’s only part of the equation. Just as important is how quickly an organisation becomes aware that something may be wrong. In practice, that awareness can come from both technical controls and employees raising concerns.
The first warning sign isn’t always a security alert
Technical tools can detect known malware and suspicious activity, but they don’t always identify every issue immediately. Sometimes the first sign of a potential problem is an employee noticing unusual behaviour, an unexpected system change, or something that just doesn’t look right. The challenge is making sure those concerns are recognised, investigated and escalated quickly.
If an employee assumes an anomaly is just a harmless technical glitch or hesitates out of fear of being blamed, days can pass before the security team even hears about it. By the time an automated alert fires, the 24-hour statutory deadline may already have been missed.
This is where the hidden risk lies. Security culture is often treated as an HR initiative, but it has a direct impact on how quickly an organisation identifies and responds to potential incidents.
Training people to spot the risks that matter
If employees play a key role in identifying and escalating potential issues, security awareness training needs to prepare them for the situations they’re most likely to encounter. Yet there’s often a gap between investment and outcomes.
Research from MetaCompliance found that organisations allocate an average of 15% of their security budgets to awareness education, with nearly four in five delivering training at least every two weeks. At the same time, 81% of IT leaders view current security awareness programmes as failing and two-thirds still identify employees as their biggest security risk.
Part of the problem is relevance. Too much training is built around meeting compliance requirements rather than helping people make better security decisions in their day-to-day roles. Employees are often asked to complete the same generic modules year after year, regardless of the risks they actually face.
When three-quarters of IT leaders admit they cannot measure which security interventions are effective for specific job roles, it’s not surprising that many organisations are rethinking their approach. Developers, engineers, support teams and business users all encounter different risks, and their training should reflect that.
A more targeted, role-based approach helps employees recognise the warning signs most relevant to them and understand when something needs to be escalated. That gives security teams a better chance of identifying potential issues early, giving them more time to assess whether they need to act within the CRA’s 24-hour reporting window.
The AI factor
Generative AI is making social engineering attacks much harder to spot. Threat actors can now create convincing emails, messages and content at scale, making it easier to target employees with attacks that feel relevant and legitimate. When malicious communications become more believable, an organisation’s ability to recognise and respond to suspicious activity becomes even more important.
That challenge is already front of mind for security leaders. More than 40% of CISOs say they’re concerned about AI helping cyber criminals scale their attacks. As the volume and sophistication of threats increase, employees are often faced with more situations where they need to make quick judgments about what looks legitimate and what doesn’t.
If an employee clicks a malicious link or notices unusual behaviour in an internal system, what happens next matters just as much as the initial mistake.
While incidents like phishing attacks would not automatically fall under the CRA’s 24-hour reporting requirement, the underlying lesson is the same: organisations need employees to be able to recognise potential security issues and escalate concerns quickly so security teams can investigate the issue, understand the impact and determine whether a reportable product vulnerability or severe incident is involved.
Culture plays a significant role here. In environments where employees worry about blame or repercussions, incidents can go unreported for hours, days or longer. In organisations that promote trust, transparency and shared responsibility, people are far more likely to speak up as soon as something feels wrong.
That earlier visibility gives security teams valuable time to investigate, contain risks and make informed decisions. When regulatory deadlines are measured in hours rather than days, every minute counts.
What boards need: moving beyond completion rates
The CRA doesn’t require organisations to report human-risk metrics directly to their boards, but it does create an opportunity for security leaders to review how human risk is measured and discussed at executive level.
Training completion rates can provide a useful view of participation, but on their own they don’t show how well employees would respond in a real-world situation. Boards increasingly need a broader understanding of security behaviour across the organisation, including whether employees report concerns, how quickly issues are escalated, which teams or roles face higher levels of risk, and whether awareness initiatives are helping to improve risk outcomes over time.
This visibility remains a challenge for many organisations. According to MetaCompliance research, 74% of CISOs say their current human cyber risk reporting produces dashboards but not enough insight to support better decision-making, while 89% cannot confidently link awareness activity to reductions in incidents or near misses.
By combining participation metrics with behavioural insights, organisations can build a more complete picture of their overall security posture and identify where additional support may be needed.
Turning compliance into resilience
The CRA’s 24-hour reporting requirement is prompting organisations to take a closer look at how quickly they can identify, assess and respond to potential security incidents.
Meeting a regulatory deadline is important, but the process of preparing for it can deliver broader benefits. It encourages organisations to examine both their technical controls, but also the people, processes and communication pathways that support effective incident response.
As security leaders prepare for the CRA’s requirements, an important consideration is whether employees know how to recognise potential issues, raise concerns and get information to the right teams quickly. The faster concerns are identified and investigated, the greater the opportunity for security teams to understand what’s happened and respond appropriately.
The 24-hour CRA window applies to a specific set of product vulnerabilities and severe incidents, but the behaviours that support compliance are relevant far more widely.

Building a culture where employees feel confident reporting concerns, understand their responsibilities and know when to escalate potential issues can help strengthen organisational resilience long after any reporting deadline has passed.
By James Mackay, CEO of MetaCompliance.
- Cybersecurity
- People & Culture
- Risk & Resilience





















































