Cyberpediaby Brain

Reporting a mistake fast, without fear of blame

Why reporting a mistake or a doubt quickly protects a company, who to tell, and what an employee can expect in return.

On this page
  1. 1In 30 seconds
  2. 2What it is
  3. 3Straight answers
  4. 4What it changes for employees
  5. 5What it changes for management
  6. 6What the text says
  7. 7Where implementation stands
  8. 8Sources
  9. 9Cite this article

In 30 seconds

What the company wants
To know early what is happening, because many incidents are only detected by people[3].
The reflex
Report the dubious click, attachment or message quickly, through the channel the company has set up (help desk, reporting portal or local security contact)[1].
If it is already done
The ANSSI recommends that small and medium-sized businesses not penalise incident reports, except in the case of a deliberate action[4].

What it is

A click on a dubious link, an attachment opened out of habit, a message sent to the wrong recipient: these mistakes happen to everyone. The NCSC, the UK's cyber security agency, points out that even with good training, no one in the organisation can have all the information and experience needed to decide correctly every time[1]. Effective cyber security therefore requires that everyone can ask for help, report a problem, admit a mistake or suggest an idea[1].

People still have to feel able to speak up. The NCSC advocates a culture where investigations aim to learn rather than to blame, without erasing individual responsibility[2]. This article sets out what the NCSC, the ANSSI and NIST say on the subject: these are guides and principles, not a law.

Straight answers

Why report a mistake, even a small one?

According to the NCSC, technical monitoring looks for anomalies, but people can also act as an early warning system and intuitively spot what seems unusual[2]. A simple reporting process can save an organisation a great deal of time and money[2]. The NCSC adds that early detection is decisive in limiting the impact of an incident[3].

Why do people stay silent?

Because they fear punishment or humiliation[1]. The NCSC explains that, without a sense of safety (often called psychological safety), people adopt self-protective behaviours: hiding their mistakes, not challenging other people's poor practices, not putting forward ideas[1]. The NCSC adds that stigmatising mistakes and singling out individuals or teams as culprits makes people more reluctant to report later incidents[3].

Metrics can also push people toward silence. According to the NCSC, if an organisation appears to value the absence of problems being raised, it encourages people to keep quiet. It suggests also measuring how many people reported a phishing attempt, not only how many clicked[2].

Does reporting mean giving up your responsibility?

No. The NCSC writes that "No blame doesn't mean no accountability": the absence of blame does not remove responsibility[2]. An incident report serves to understand the root cause, the actual response and what could be improved. A report that concentrates on the individuals or teams "behind the problem" is, according to the NCSC, a sign of a less mature culture[2].

This is what the NCSC describes as a healthy organisation: people involved in an incident are treated fairly, with no punishment for innocent mistakes[1]. The ANSSI expresses the same idea for small and medium-sized businesses: the response to a report should be non-coercive, the aim being to make users accountable rather than to punish them, except in the case of a deliberate action, so as to avoid under-reporting of incidents[4].

Who should you tell?

The NCSC lists help desks, reporting portals or local security experts as routes for reporting, and asks that they be fast, simple and accessible[1]. The ANSSI recommends that small and medium-sized businesses give every newcomer an IT charter that details the digital practices to follow and the procedure for reporting an incident[4].

What happens after a report?

The NCSC recommends thanking the person who reported and telling them what follow-up was given[1]. Investigations should be carried out openly and fairly, focusing on what went wrong rather than on who is to blame[1]. The lessons learned and the resulting improvements should be shared[1].

What it changes for employees

An employee can report as soon as they have a security question or problem, through the channel their company provides[1]. For a suspicious message, the ANSSI recommends checking its authenticity with the sender through another channel (phone, text message)[4]. If equipment is lost or stolen, the company must be informed[4].

In the case of a confirmed incident on a device, the ANSSI states that the first reflex is to disconnect it from the Internet, for example by unplugging the network cable or turning off WiFi, and not to switch off or modify the affected devices, which will be useful to investigators[4].

If a procedure forces you to work around it to get your job done, saying so is useful: the NCSC notes that such workarounds can reveal a policy or process that needs fixing[2].

In return, the NCSC describes an organisation that says thank you, reports back on what followed, investigates fairly and does not punish an innocent mistake[1]. Recognising contributions and acting where possible encourages further reports[1].

What it changes for managementManagement

Leaders set the tone. According to the NCSC, if senior people ignore the rules or ask for special treatment, they signal to everyone that it is acceptable to bypass them[3]. If they visibly fail to follow security messages, the effectiveness of a campaign is quickly undermined[3].

The NCSC asks organisations to review and improve their reporting mechanisms, and to test them to reduce the friction that leads people to give up and avoid any future contact[1]. It invites them to measure successes too, for example the number of people who reported a phishing attempt[2].

On communication, the NCSC advises against fear: using fear or stressing threats to motivate staff works poorly and can have the opposite effect, leaving employees disengaged. It recommends positive messages about what each person can do to help[3]. It adds that if employees work around rules to get their jobs done, they already know they are breaking them, and more awareness will not help until the causes are fixed[3].

What the text saysOfficial text

None of the documents below is a law. Each is a guide or a set of principles, attributed here to its publisher.

The NCSC defines cyber security culture as the collective understanding of what is normal and valued at work with regard to cyber security[5]. It sets expectations for behaviours and relationships, and influences the ability to collaborate, trust and learn[5]. Its principle 2 asks organisations to build the safety, trust and processes that encourage openness, with four signs of an organisation on the right track: an environment where people feel ready to speak up, fast and accessible reporting routes, investigations to learn rather than to blame, and fair treatment with no punishment for innocent mistakes[1]. The NCSC specifies that you cannot simply "change" a culture: behaviours are encouraged, and culture is the result[2].

The ANSSI, in its guide for very small and small and medium-sized businesses, recommends that small and medium-sized businesses lay the foundations of an IT hygiene culture through regular staff information, with an IT charter that details the procedure for reporting an incident[4]. It asks them to encourage incident reporting through a non-coercive response, with no sanction except in the case of a deliberate action[4].

NIST, in its publication SP 800-50 Rev. 1 of September 2024, describes an awareness, training and education programme that should encourage behaviour change within risk management and lead to the development of a security and privacy culture in the organisation[6].

Where implementation stands

The NCSC's culture principles are at version 1.0, published and reviewed on 4 June 2025[5]. The NCSC states that they describe the desirable states of a healthy culture rather than a prescriptive manual, and that there is no single approach that suits every organisation[5].

The NIST publication appeared in final version on 12 September 2024[6]. It replaces SP 800-50 of 2003 and SP 800-16 of 1998[6]. It is aimed at US federal agencies and at organisations, large or small[6].

The ANSSI guide for very small and small and medium-sized businesses is at version 2.5, dated November 2024[4]. It specifies that some of its recommendations are good practice and that others require a larger investment, for which the organisation can receive support[4].

Sources

  1. NCSC (UK), “Principle 2. Build the safety, trust and processes to encourage openness around security”, 4 June 2025. https://www.ncsc.gov.uk/collection/cyber-security-culture-principles/principle-2 (accessed 14 November 2026)
  2. NCSC (UK), “Developing a positive cyber security culture”, 30 March 2023. https://www.ncsc.gov.uk/collection/board-toolkit/principle-c-people/developing-a-positive-cyber-security-culture (accessed 14 November 2026)
  3. NCSC (UK), “Engagement and training”, 11 May 2021. https://www.ncsc.gov.uk/collection/10-steps/engagement-and-training (accessed 14 November 2026)
  4. ANSSI, “La cybersécurité pour les TPE/PME en 13 questions”. https://messervices.cyber.gouv.fr/documents-guides/20241212_np_anssi_guide_tpe-pme_v2.pdf (accessed 14 November 2026)
  5. NCSC (UK), “Cyber security culture principles”, 4 June 2025. https://www.ncsc.gov.uk/collection/cyber-security-culture-principles (accessed 14 November 2026)
  6. NIST, “SP 800-50 Rev. 1, Building a Cybersecurity and Privacy Learning Program”, 12 September 2024. https://csrc.nist.gov/pubs/sp/800/50/r1/final (accessed 14 November 2026)