When a company assesses whether its systems and documents are sufficiently secure, authentication is the key concept. Authentication is the process of proving that a user is actually who they claim to be—and in the Nordic region, the modern approach is based on MitID and eID, where identity is verified by a national system rather than simply a self-chosen password. The difference is crucial: a password can be shared or guessed, whereas eID-based verification is linked to a specific, verified identity.
These concepts are often confused, but each serves a distinct purpose. Identification is when the user states who they are. Authentication is the proof that this is correct. Authorization then determines what the verified user is permitted to do. A clear understanding of this chain is the foundation of a robust security design—see the in-depth overview of Secure Identification for Businesses. When these three steps are kept separate, it becomes easier to pinpoint where a potential security vulnerability arises: is the identity verification itself too weak, or are the permissions too broad?
These methods are typically grouped into three factors: something you know (password, PIN), something you have (phone, token, MitID app), and something you are (fingerprint, facial recognition). Single-factor login using only a password is the weakest form, while combining multiple factors provides strong authentication. Two-factor authentication, where a password is combined with a verification code sent to your phone, is now the minimum standard for accessing sensitive systems. The strength of combining factors is that an attacker must compromise multiple independent elements at once, which in practice stops the vast majority of attempts at unauthorized access.
For Nordic companies, MitID is a practical path to strong authentication because the user’s identity is already verified by the national eID. The user does not have to remember yet another set of login credentials, and the company does not need to maintain a vulnerable password database itself. The same login can be used both to grant access and for digital signatures with MitID, so authentication and signing are integrated into a single secure workflow without duplication of effort.
When access is granted to an employee acting on behalf of the company, MitID Erhverv is used. This links authentication to an organizational role, so it can be documented that a specific employee—and not just a private individual—was granted access or approved a document. Read more about the framework in the overview of MitID Business for companies. It also allows the company to grant and revoke access centrally, so that permissions are tied to employment rather than to an individual user.
The level of strong authentication a company needs depends on the risk. Logging into an internal intranet has different requirements than signing a binding agreement with significant financial implications. The eIDAS Regulation defines security levels that help match the method to the need, and you can see the relationship in the overview of eIDAS security levels. The point is not to use the highest level everywhere, but to ensure that the most sensitive actions always require the strongest identity verification.
A robust approach starts by classifying systems and documents by sensitivity and then assigning an appropriate authentication method to each level. Sensitive actions such as signing should always require strong, identity-based authentication, while low-risk access can get by with less. It’s also important to have a clear process for revoking access when an employee changes roles or leaves the company. When authentication is tied to a verified eID, every access event and every signature becomes traceable—which both strengthens security and simplifies the use of digital signatures for businesses across the organization.
Even companies with good intentions often fall into the same traps. A common mistake is relying solely on passwords for systems containing sensitive documents, which makes them vulnerable to phishing and reused passwords. Another is failing to revoke access when employees change roles or leave the company, leaving old accounts as an open security hole. A third is applying the same low security level to everything, which either burdens users with unnecessarily cumbersome logins or leaves the most critical actions unsecured. A fourth pitfall is treating authentication as a one-time task completed during implementation, rather than something that requires ongoing maintenance as roles, systems, and threats change over time. By linking authentication to verified eID and tying the security level to the risk associated with each individual action, the company avoids most of these problems at once.