Which cloud services may be used at work?

At work, only approved cloud services should be used. Shadow IT appears when work bypasses risk management.

· 11 min read · Written by AI · checked by AI

In brief

At work, you may use cloud services that your organisation has approved for that work, that have been assessed as part of risk management, and that come with clear instructions. Shadow IT means work tools or cloud accounts used outside that approved route, for example a personal file-sharing account used to finish a task faster. The Cybersecurity Act, section 9, requires cybersecurity risk management controls for networks and information systems, including acquisition, supply chain security, asset management, access control, cyber hygiene and staff training. The law does not name allowed cloud services, so the practical answer must come from the organisation’s own risk management model and cloud use rules.

An allowed cloud service is known, assessed and instructed

A cloud service is a service used over a network, such as file storage, messaging, collaboration, customer management or an artificial intelligence tool. The important workplace question is not whether the service is well known. The question is whether the organisation knows it is used, has assessed the risks, and has told employees what it may be used for.

The Cybersecurity Act 124/2025, section 9, requires operators to implement proportionate technical, operational or organisational security controls under a cybersecurity risk management model. In daily work, this means that cloud use cannot be a matter of individual preference when the service handles work data, accounts, devices or communication.

An allowed cloud service normally has these practical features:

  • The organisation knows the service is in use.
  • The service has an owner inside the organisation.
  • The intended use is clear, such as internal files, customer communication or project work.
  • The access rights are managed by the organisation.
  • Authentication is defined. Authentication means proving who is signing in, for example with a password and multi-factor authentication.
  • The information that may be stored or shared in the service is defined.
  • The supplier or service provider has been considered as part of supply chain security.
  • Employees have instructions that match real work situations.

A service can be safe for one purpose and unsuitable for another. A team chat may be fine for internal coordination but not for a confidential case file. A file-sharing service may be approved for ordinary project material but not for information that the organisation has classified as restricted. Information classification means sorting information by sensitivity, in the same way that an envelope can be public, internal or confidential.

Cloud rules should therefore be written around use cases. The useful question is: what work may be done in this service, by whom, with what kind of information, and with what access controls? For information classification in daily work, the topic continues in Why is information classified and how does the class guide use?.

Shadow IT appears when the work must be finished but the rule is missing

Shadow IT is not usually created by malice. It often appears when an employee has a real work problem and the approved route is unclear, slow or absent. The employee chooses a familiar cloud service, a personal account, a free trial, a browser extension or a shared folder because the task has to be finished.

Typical causes are simple:

  • The official tool is not known.
  • The official tool does not support the task.
  • The instruction is too general.
  • Access takes too long.
  • External partners use a different tool.
  • Employees do not know what kind of data may be put into which service.
  • Artificial intelligence tools make copying text into a cloud service feel normal.

This creates a management problem. The organisation may not know that the tool exists. It may not know what work data is stored there. It may not know who has access. It may not be able to restore material after an incident. It may not be able to remove access when a role changes.

The Cybersecurity Act, section 9, includes asset management and the identification of functions important for security. Asset management means keeping track of what the organisation uses. In cloud work, the asset is not only a laptop or a server. It can also be a cloud workspace, an integration, an account, an application programming interface key, or a shared folder.

Shadow IT is especially difficult with tools that look harmless. A note-taking service, translation tool or artificial intelligence assistant can still receive work material. If employees use artificial intelligence tools at work, cloud use rules and artificial intelligence rules need to meet. The related question is covered in What may employees enter into an AI tool at work?.

Risk management decides what the cloud may be used for

The Cybersecurity Act, section 9, does not say that every organisation must make the same cloud decisions. It requires controls to be proportionate to the nature and scale of operations, the reasonably foreseeable direct effects of an incident, the risk exposure of networks and information systems, the probability and severity of incidents, costs, and available technical possibilities.

That proportionality matters. A small internal planning tool and a critical service platform do not carry the same risk. A cloud service used for public information and a cloud service used for confidential operational material do not need the same instructions.

The NIS2 Directive, Article 21, also requires appropriate and proportionate technical, operational and organisational measures for risks affecting network and information systems used in operations or service provision. Article 21 lists areas that matter for cloud decisions. These include risk analysis, system security policies, incident handling, business continuity, supply chain security, secure acquisition and maintenance, effectiveness assessment, cyber hygiene, training, cryptography, access control, asset management and authentication.

For cloud services, these legal areas become practical questions:

Risk management area Workplace cloud question
Risk analysis and security policies What may this cloud service be used for?
Acquisition, development and maintenance security How is the service selected, configured and updated?
Supply chain security What is known about the provider and its cybersecurity practices?
Asset management Is the service listed and owned by someone?
Access control Who may use it, and how is access removed?
Authentication Is the sign-in method strong enough for the data and work?
Encryption and secure communication How is information protected when stored or sent?
Incident handling Who reacts if an account, folder or service is compromised?
Business continuity What happens if the service is unavailable?
Cyber hygiene and training Do employees know the safe everyday rules?

Access control means deciding who gets in. A simple example is a project folder that only the project team can open. Authentication means proving the user is the right person. Multi-factor authentication means sign-in needs more than one proof, such as a password and a separate confirmation.

These measures are not only technical settings. They need operating rules and employee understanding. An approved service can still be used unsafely if employees share links too widely, store the wrong information, or accept a fake sign-in page. Phishing and social engineering are therefore part of cloud governance. For that topic, see Phishing and AI-assisted scams: how an employee recognises one.

The service provider is part of supply chain security

A cloud service is also a supplier relationship. The organisation does not only use software. It relies on a provider’s service, resilience and cybersecurity practices.

The Cybersecurity Act, section 9, requires the risk management model and controls to take account of the general quality and resilience of the products and services of immediate suppliers and service providers, the controls included in them, and the cybersecurity practices of immediate suppliers and service providers.

The NIS2 Directive, Article 21, treats supply chain security in the same practical direction. It covers the security aspects of the relationship between the organisation and its direct suppliers or service providers. It also requires attention to supplier-specific vulnerabilities, the general quality of products, and the cybersecurity practices of suppliers and service providers, including secure development procedures.

For cloud decisions, this means that a service provider is not invisible. The organisation needs a way to decide whether the provider is suitable for the intended use. A consumer-grade file store, a trial service and a managed business service may look similar to an employee. For risk management they can be very different.

The following questions help turn supply chain security into a cloud rule:

  • Is this provider approved for the type of work planned?
  • Is the service used under an organisation-managed account or a personal account?
  • Can access be managed centrally?
  • Can access be removed when employment or a role changes?
  • Is there a process for incidents affecting the service?
  • Is the service important enough to need continuity planning?
  • Are employees told what information may not be placed there?

This is why personal cloud accounts are risky in work use. They usually sit outside the organisation’s supplier management, access control, asset management and incident process. Even if the employee acts carefully, the organisation has weaker visibility and weaker control.

Shadow IT is controlled by visibility, rules and training

Shadow IT cannot be solved only by saying no. A ban without workable alternatives often drives the same behaviour further out of sight. The better control model has three parts: visibility, rules and training.

Visibility means the organisation identifies the cloud services used for work. This can include procurement records, identity and access management, device management, network observations, contract reviews and staff feedback. The legal point comes from the Cybersecurity Act, section 9, through asset management, security-relevant functions and risk-based controls.

Rules mean a short and usable cloud use policy. It should say which services are approved, what each service may be used for, which information classes are allowed, how external sharing is handled, and what employees must do if the approved tool does not fit the task. The rule should also cover personal accounts. A practical rule is stronger when it gives a safe alternative.

Training means employees learn the reason behind the rule. If an employee only hears that a tool is forbidden, the next urgent task may still create a workaround. If the employee understands access control, supplier risk, phishing, information classification, remote work and incident reporting, the safer choice becomes easier.

The Cybersecurity Act, section 9, expressly includes personnel security and cybersecurity training in the risk management model. The NIS2 Directive, Article 21, includes basic cyber hygiene practices and cybersecurity training. Cyber hygiene means everyday protective routines, such as using approved tools, checking sign-in pages, protecting devices, reporting suspicious events and avoiding oversharing.

A workable shadow IT programme therefore has at least these actions:

  • Keep an inventory of approved cloud services.
  • Name an owner for each service.
  • Define allowed and prohibited use in plain language.
  • Match cloud services to information classes.
  • Require organisation-managed accounts for work use where control is needed.
  • Use access control and authentication suitable for the risk.
  • Assess direct providers as part of supply chain security.
  • Include cloud use in incident handling and continuity planning.
  • Train employees in cyber hygiene and secure cloud use.
  • Provide a route for requesting a new tool instead of creating a workaround.

Remote work increases the need for these basics because employees often work across home networks, mobile devices and public networks. The related device and remote work questions continue in Remote work security: devices, networks and what to do when ransomware strikes.

Limits: the law does not publish an allowed list of cloud services

The Cybersecurity Act and the NIS2 Directive do not publish a list of cloud services that are allowed at work. They also do not state that one cloud provider is always safe or another is always forbidden. They set requirements for risk management and security controls.

This leaves choices for the organisation. The organisation must decide what is proportionate for its operations, risks and systems. The right decision may differ between a municipality service, an industrial company, an internal support function and a customer-facing system.

The law also does not make training a replacement for technical and organisational controls. Training helps employees recognise safe use, phishing, manipulation and risky workarounds. It does not by itself create an asset inventory, configure access rights, assess a supplier, encrypt data or restore a service after an incident.

Nor does an approved cloud service remove the need for instructions. A service can be approved but still misused. Employees need to know what information may be stored, who may receive links, which account to use, how to report a suspected incident, and where to ask when the approved tool does not solve the work problem.

One statutory detail remains separate from ordinary workplace cloud choices. The NIS2 Directive, Article 21, states that the European Commission adopts implementing acts by 17 October 2024 for technical and methodological requirements for several types of entities, including cloud computing service providers. That concerns requirements for those providers and other listed entities. It does not give an employee a public list of cloud services that may be used in their own workplace.

The practical conclusion is clear. Allowed cloud use is an organisational decision made through risk management. Shadow IT is controlled when approved tools are visible, usable and taught, and when employees have a safe route before they create their own.

Frequently asked questions

Which cloud services may be used at work?

Cloud services that the organisation knows, has assessed and has instructed for the intended use may be used at work. The Cybersecurity Act does not publish a list of allowed services. The allowed list must come from the organisation’s own risk management, access control, supplier assessment and information handling rules.

What does shadow IT mean?

Shadow IT means cloud services, accounts, applications or devices used for work outside the organisation’s approved process. A common example is an employee saving work material in a personal cloud account because it feels faster than the official tool.

Does the Cybersecurity Act ban all unapproved cloud services?

The Cybersecurity Act, section 9, does not use a simple ban list for cloud services. It requires proportionate technical, operational and organisational security controls based on a cybersecurity risk management model. In practice, unapproved cloud use is hard to justify because it bypasses those controls.

Why is an employee’s own cloud account a risk at work?

A personal cloud account is often outside the employer’s asset management, access control, authentication, supplier assessment, backup planning and incident handling. If work material is stored there, the organisation may not know where the material is, who can access it, or how to restore or remove it.

How can shadow IT be brought under control?

Shadow IT is controlled by visibility, clear rules and staff training. The organisation needs to know which services are used, decide what each service may be used for, apply access and authentication rules, assess suppliers, and train employees to recognise when a convenient tool is not an approved work tool.

Sources