What cyber threats face an ordinary organisation?

Ordinary organisations face incidents, vulnerabilities, supply chain and access risks. Staff are the first people who can notice and stop them.

· 10 min read · Written by AI · checked by AI

In brief

Cyber threats are events and weaknesses that can harm the network and information systems an organisation uses for its work. For an ordinary organisation, the practical threat picture is built from information security incidents, vulnerable systems, supplier risks, weak access control, unsafe handling of data, and disruption to continuity. Staff are the first line of defence because these risks first appear in daily work: in messages, logins, devices, cloud services, customer data and office routines. The Cybersecurity Act 124/2025, section 9, and the NIS2 Directive (NIS2), Article 21, both treat cyber hygiene and staff training as part of cybersecurity risk management.

The threat picture of an ordinary organisation comes from everyday work

A cyber threat does not need to start with a dramatic attack. It can start with a routine work task.

An employee receives a message and is asked to sign in. A supervisor approves access to a system. A worker stores a file in a cloud service. A device is used outside the office. A supplier maintains a system that the organisation needs for its own service.

Each of these moments touches a network or information system. NIS2 Article 21 uses that same starting point. It concerns the risks to the security of network and information systems that an organisation uses in its operations or in providing services.

This is why the threat picture is not only a technical map for information technology. It is also a map of ordinary work. If work depends on accounts, devices, data, suppliers and systems, then cyber risk is part of that work.

Cyber hygiene means routine security habits, like washing hands in healthcare or checking a door before leaving an office. At work, it means habits such as checking a login request, protecting a device, using the right channel for files, and reporting an information security incident. The Cybersecurity Act, section 9, names basic information security practices and cybersecurity training as part of the risk management model.

The law highlights concrete threat areas

The Cybersecurity Act, section 9, requires proportionate technical, operational or organisational security controls for managing cybersecurity risks and preventing or minimising harmful effects. A security control is a practical measure that reduces risk. Multi-factor authentication is a security control because it makes a stolen password less useful.

NIS2 Article 21 sets the same structure at European Union level. It requires appropriate and proportionate technical, operational and organisational measures. It also says that the measures must be based on an all-hazards approach. In plain language, the organisation should not look only at one type of attack. It should look at the different ways systems, services and their physical environment can fail or be harmed.

The threat areas in the law can be read as a practical checklist:

Threat area in everyday work What it means in practice Source
Information security incidents Something happens that may affect security or continuity, such as abnormal system behaviour or misuse of access Cybersecurity Act, section 9; NIS2 Article 21
Vulnerabilities A weakness in a system, device or process may be used against the organisation Cybersecurity Act, section 9; NIS2 Article 21
Supply chain risk A direct supplier or service provider may introduce risk through its product, service or cybersecurity practices Cybersecurity Act, section 9; NIS2 Article 21
Access and authentication risk The wrong person may get access, or the right person may be authenticated in a weak way Cybersecurity Act, section 9; NIS2 Article 21
Continuity risk Work may stop if backups, recovery planning or crisis management do not work Cybersecurity Act, section 9; NIS2 Article 21
Data handling risk Data may be moved, stored or shared in a way that does not match its sensitivity Cybersecurity Act, section 9; NIS2 Article 21
Physical and workspace risk Systems, devices or essential resources may be exposed through offices, equipment rooms or other physical environments Cybersecurity Act, section 9; NIS2 Article 21

These are not exotic risks. They are the risks that appear when ordinary work depends on information systems.

Phishing is a simple example. A phishing message tries to make a person reveal credentials, open a harmful file or approve a false request. The legal category behind the situation may be access control, authentication, incident handling or cyber hygiene. For a practical employee view, see Phishing and AI-assisted scams: how an employee recognises one.

Staff are the first line of defence because the threat is first visible in daily work

Staff do not replace technical protection. They make technical protection work in real life.

A filter can reduce suspicious messages. An employee still needs to recognise the message that reaches the inbox. A device management rule can protect a laptop. An employee still needs to notice when the device behaves strangely. An access policy can define who may use a system. A supervisor still needs to avoid giving access just because it is convenient.

The Cybersecurity Act, section 9, names personnel security and cybersecurity training. It also names access management and authentication procedures, incident detection and handling, asset management, and basic information security practices. These are not separate worlds. They meet in daily decisions made by people.

An information security incident is an event that may weaken security or service reliability. In everyday terms, it is the moment when something is not normal and may matter: an unexpected login prompt, files that cannot be opened, a lost device, or a message that asks for urgent payment outside the normal process.

The value of staff training is not that every employee becomes a technical expert. The value is that employees know what to notice, what not to do, and where to report. That turns a weak signal into an early control.

For device, remote work and ransomware scenarios, see Remote work security: devices, networks and what to do when ransomware strikes. For access controls, see Access control, multi-factor authentication and encryption: three measures the law names.

Knowledge alone is not enough if incidents have no operating model

Awareness is useful only when it connects to a way of working.

The Cybersecurity Act, section 9, includes incident detection and handling for restoring and maintaining security and operational reliability. NIS2 Article 21 includes incident handling, business continuity, backups, recovery planning and crisis management.

This means that an organisation needs more than a general instruction to be careful. Staff need to know the practical route from observation to action. If an employee suspects a phishing message, the next step should be clear. If a device is lost, the next step should be clear. If access seems wrong, the next step should be clear.

The operating model also protects the organisation from delay. A person who is unsure may wait. A person who fears blame may stay silent. A person who knows the agreed route can report quickly and without improvising.

Reporting is not only a legal or management task. It starts with observation. The employee who notices the first sign may not know whether the event is serious. The process should still accept the report. Specialists can then decide what the incident means and what must happen next.

For reporting duties after a cybersecurity incident, see What must be reported after a cybersecurity incident, and when?. If the incident may involve personal data, see Personal data breach: the 72 hours start when an employee notices.

For management, staff competence is a security control

Management often sees cybersecurity through budgets, systems and suppliers. The law frames it more broadly.

The Cybersecurity Act, section 9, requires controls to be proportionate to the nature and scale of the operation, the reasonably foreseeable direct effects of an incident, the risk exposure of the network and information systems, the likelihood and severity of incidents, the costs of measures, and available technical possibilities in light of current development.

This matters for staff training. Training is not a communications campaign beside the real controls. It is an organisational control. It supports access management, incident handling, continuity, supplier risk management, data handling and physical security.

NIS2 Article 21 also treats cyber hygiene practices and cybersecurity training as required content in the risk management measures. It separately names personnel security, access control policies and asset management. In plain language, people, rights and assets must be managed together.

A simple example is cloud storage. If employees do not know which cloud services may be used, the organisation may lose control of where files go. If employees understand the rule and the reason behind it, a policy becomes visible in daily work. For more on this topic, see Which cloud services may be used at work?.

Another example is information classification. A classification is a label that tells how carefully information must be handled. A public brochure, an internal plan and sensitive customer data do not need the same handling. For practical guidance, see Why is information classified and how does the class guide use?.

The law does not say or require everything

The legal texts do not say that every organisation faces the same risk level. Both the Cybersecurity Act, section 9, and NIS2 Article 21 are built on proportionality. Measures must match the organisation, the risks and the possible effects of incidents.

The texts also do not make staff solely responsible for cybersecurity. Staff are an important defence line, but the legal model includes technical, operational and organisational controls. That means systems, processes, suppliers, management and training all matter.

The cited parts do not name one mandatory training format. They do not require that every employee becomes an information security specialist. They require cybersecurity training and basic cyber hygiene practices as part of risk management.

The cited parts also do not decide the full scope question for every organisation. NIS2 Article 21 refers to essential and important entities. The Cybersecurity Act, section 9, refers to operators covered by the Act. Scope should be checked before treating a legal duty as applicable. For that question, see Do NIS2 and the Finnish Cybersecurity Act apply to us?.

Finally, compliance is not proven by one technical product or one training event. The law expects maintained controls and an up-to-date risk management model. A supervisory authority may also issue more detailed technical regulations in its sector under the Cybersecurity Act, section 9.

Staff cyber hygiene makes risk management visible

Cybersecurity risk management can look abstract in a policy. Staff cyber hygiene makes it visible in work.

It is visible when an employee checks a sender before opening an attachment. It is visible when a manager grants only the access needed for the task. It is visible when a lost device is reported through the agreed route. It is visible when files are shared through an approved service. It is visible when a visitor cannot see confidential material on a desk or screen.

These actions connect directly to the areas named in the Cybersecurity Act, section 9: personnel security, cybersecurity training, access and authentication, incident handling, basic security practices, asset management, data security, and physical security. They also connect to NIS2 Article 21: incident handling, continuity, supply chain security, vulnerability handling, cyber hygiene, training, encryption, access control and secure communications where needed.

For a decision-maker, the practical question is not whether staff are a weakness or a defence. They are both, depending on how the organisation prepares them. Untrained staff may turn ordinary work into hidden risk. Trained staff make the same work part of detection, prevention and recovery.

That is why the first defence line is not a slogan. It is the point where law, technology and daily behaviour meet.

Frequently asked questions

What cyber threats affect an ordinary municipality or company?

The main threat areas are information security incidents, vulnerable systems, weak access control, supplier risks, loss of continuity, insecure devices, and unsafe handling of data. The Cybersecurity Act, section 9, and the NIS2 Directive, Article 21, frame these as risks to network and information systems.

Why is staff the first line of defence in cybersecurity?

Staff use accounts, devices, cloud services and data every day. They are often the people who first see an unusual sign, such as a suspicious login request, a strange attachment or a service failure. Training turns that observation into the right action.

Is technical protection enough against cyber threats?

No. The NIS2 Directive, Article 21, requires technical, operational and organisational measures. The Cybersecurity Act, section 9, also names personnel security, cybersecurity training, access and authentication procedures, and incident detection and handling.

What does cyber hygiene mean at work?

Cyber hygiene means routine security habits. Examples are checking a message before opening a link, using strong authentication, locking a screen, handling data according to its class, and reporting an information security incident through the agreed channel.

Does the Cybersecurity Act apply to every organisation?

This question must be checked separately. The NIS2 Directive, Article 21, concerns essential and important entities, and the Cybersecurity Act, section 9, sets duties for operators. The same good practices are useful more widely, but the legal duty depends on scope.

Sources