What the BSI expects for devices and access

Written by Milutin Jokić | Nov 14, 2026, 8:49:53 AM

Germany's NIS-2 implementation act has been in force since December 2025. Many small and mid-sized companies tick the topic off quickly because they belong to none of the regulated sectors and are not big enough. Formally that is often true. In practice it still reaches them, through their customers.

This guide shows what the BSI, Germany's Federal Office for Information Security, expects for user accounts, access and company devices, and how to put it into practice, with or without an IT department of your own.

Key points

  • Companies covered by NIS-2 also have to secure their supply chain. They therefore pass requirements on to service providers and suppliers.
  • The BSI's IT-Grundschutz describes quite concretely what is expected for user accounts and access. It comes down to four points. Assign accounts, grant rights as needed, document everything and log changes.
  • Things get critical when an employee joins, changes roles or leaves. That is where forgotten accounts and devices nobody knows about come from.
  • What you need is a fixed process and one place that shows devices, tools and access per employee. A PDF checklist is at the end.

Why this also affects companies outside NIS-2

The act obliges affected companies to manage the security of their supply chain. In its NIS-2 FAQ the BSI points out explicitly that these companies often pass their requirements on to service providers and suppliers by contract. If you work for an energy supplier, a hospital or a larger industrial company, a questionnaire will reach you sooner or later. It asks, in essence, who in your company has access to which systems and how you make sure former employees no longer do.

The BSI therefore suggests that such companies look at the measures in the act now. Two of them touch everyday work in every company, namely access control together with personnel security, and the management of the IT in use.

Then there is the threat situation. According to the BSI's 2025 report on IT security in Germany, around 80 percent of the attacks reported to the police, ransomware for example, were aimed at small and mid-sized companies. The BSI names protecting your own attack surface as the most important lever. An account that keeps running after someone has left is such an attack surface. So is a laptop that appears on no list.

Four points the BSI expects for accounts and access

The BSI's IT-Grundschutz is more concrete than the act. Its module ORP.4 describes how a company should handle user accounts and permissions. Four points matter for everyday work. Each comes with a question you can use to check yourself.

Assign accounts

Every account can be traced to one person. Accounts that have not been used for a long time are deactivated.

Do you know who owns every account in every tool?

Rights as needed

Everyone gets only the access they need for their job. When the job changes, rights that are no longer needed are revoked.

Does anyone still have access from an earlier role?

Document

Accounts and rights are written down and regularly compared with the actual state.

When did you last compare your list with reality?

Log

Handing out and taking back means of access is recorded.

Could you show when access was revoked and by whom?

The third point is the hardest in practice. Most companies have a spreadsheet, but it is rarely up to date. As soon as a team books a new tool on its own, shadow IT appears that is on no list.

The same principle applies to devices. The act requires that the IT in use is managed in an orderly way. That starts with the simple question of which laptops and smartphones exist and who has them right now. Our guide to managing company laptops shows how to set that up.

Joining, changing roles, leaving

In everyday work it comes down to three moments. Each time, who may access what changes.

When someone joins, they get a device, accounts and licenses. If that happens informally, nobody knows three months later exactly what was handed out. A fixed process per role solves this. It defines which tools and which device belong to a position and records what was actually handed out. You will find a template in the onboarding checklist.

When someone changes roles, new access is added while the old access usually stays. That is how long-serving employees collect rights they have not needed for years. The Grundschutz requires that rights no longer needed are revoked. In practice that means going through the person's list once at every change.

When someone leaves, the BSI requires a defined procedure. It includes the return of devices, revoking all access and the question of what happens to data and licenses. What is usually missing is the overview. If you do not know which twenty tools someone had an account in, you can only revoke the five you remember. Why locking the main account is not enough is explained in the guide to deprovisioning, and the individual steps are in the offboarding checklist.

For longer absences, such as parental leave, the Grundschutz also provides for access to be blocked temporarily.

Checklist for devices and access

These ten points show you where you stand. Once a quarter is enough.

  • There is a current list of all devices with the assigned employee
  • There is a list of all tools in use, including those teams booked themselves
  • Every account is assigned to one person, shared accounts are the exception and documented
  • For every role it is defined which access comes with it
  • Accounts without a login for several months are reviewed and deactivated
  • Administrator accounts are protected with multi-factor authentication
  • There is a fixed process each for joining, changing roles and leaving
  • When someone leaves, devices are returned and all access is revoked, both recorded with a date
  • The list of accounts is regularly compared with the actual state
  • You can show a customer on request who had which access and when

The checklist is also available as a PDF. You can fill it in on screen, enter an owner for each point and file it as a record.

Download the checklist (PDF)

How Sovaro handles it

Sovaro brings devices, software and access together in one tool, and you do not have to maintain the overview by hand. The Sovaro agent on the laptops and the browser extension detect which tools are actually in use. The AI knows more than 500 tools and classifies them automatically. That way the tools a team booked on its own show up as well.

You see devices, licenses and access per employee and spot licenses nobody uses anymore. Onboarding and offboarding run as a process with tasks for the people responsible, laptops can be locked or wiped remotely, and every change ends up in an audit log that you can export. The records customers ask for in their questionnaires are created along the way. It does not replace a certification. The IT base costs 6.90 euros per person per month.

Learn more about Sovaro

Frequently asked questions

Does NIS-2 also affect companies that are not directly covered by the act?

Indirectly, yes. Affected companies have to secure their supply chain and therefore often pass requirements on to service providers and suppliers by contract. If you have such customers, you should be able to show how access and devices are managed.

What does the BSI require for user accounts and access?

The IT-Grundschutz expects four things at its core. Every account is assigned to one person, rights are granted only as needed, accounts and rights are documented and regularly compared with the actual state, and handing out and taking back access is recorded.

Do small companies have to implement the IT-Grundschutz?

There is no general obligation. The Grundschutz is a recognized benchmark, though, that customers and auditors use as a reference. For companies with fewer than 50 employees the BSI itself considers it too extensive and offers an easier start with the CyberRisikoCheck.

How do I prove who had which access and when?

With a log that records every grant and every revocation with a date and the person responsible. By hand, that works with a list per employee. A tool that writes these entries automatically during onboarding and offboarding and provides them as an export is easier.

What is the first step?

Taking stock. Write down which devices exist, who uses them, which tools are in use and who has an account there. Only with this overview can you set up fixed processes for joining, changing roles and leaving.