Confidential files are not for everyone.

Personnel files, development documents, quotes and customer data already deserve protection in normal business operations. Your company does not need to handle government contracts or process classified information for this. Together, we determine which files are encrypted, who needs access on the business side and how deputies can be arranged. The standard solution is aligned with these workflows; an approved edition is added when your specific protection needs require it.

A small business can start with a protected storage area for management and HR. In midsize companies, for example, separate project teams, multiple sites and external collaboration come into play. For enterprise structures, we additionally plan delegated administration, systematic permission changes and clearly assigned key responsibilities. The selection takes into account client versions, existing storage locations, application compatibility and how authorized people continue working even after a device change.

A file share first governs who may access data through a specific access path. File and folder encryption adds to this protection: access to the content additionally depends on the keys required. What matters is which data pathways the chosen solution actually covers. Together, we look at local storage, shared directories, copy operations and exchange with partners. This shows where confidential content is processed and where different or additional protection is needed.

The application perspective remains important here. Authorized people still need to be able to edit files; at that moment, plaintext can exist. Encryption therefore does not automatically prevent data loss through an already authorized or compromised user. Endpoint protection, sensible roles and secure exchange procedures remain part of the overall setup. In the pilot, we examine the intended workflows and document their limits. This gives your team a clear statement of what is protected and what responsibility remains elsewhere.

Choosing a method does not yet resolve the organizational questions. Who is allowed to add new members to a project? What happens when someone leaves? How is data made accessible if an authorized key is not available? These questions are answered before the rollout. An agreed role model prevents broad access rights from arising merely out of convenience. Recovery is given named owners and a documented approval path that matches the protection requirements of your information.

Backup and recovery must also fit together with the key concept. Data can technically exist and still remain unusable if the associated keys are missing. Conversely, a recovery procedure must not bypass the intended access restrictions unnoticed. That is why backup scope, key availability and recovery are tested together. The handover explains these procedures to administrators and business owners. Changes to protection domains or products are then evaluated against the same setup.

u.trust LAN Crypt version 13.0.x from Utimaco IS GmbH is approved under BSI-VSA-10966 up to VS-NfD. The approval, issued on November 15, 2025, is valid until November 15, 2028; the entry is current as of November 15, 2025. We translate the requirements of your file storage into a specific setup and check platform, configuration and operating procedures against the associated documentation. For this version, we do not state an EU or NATO approval: this approval entry names only VS-NfD. Requirements for NATO RESTRICTED are therefore assessed separately and not derived from the national approval.

Even in a military project, product approval, system operation and personnel access are considered separately. Ü3 denotes a security clearance for people, not an encryption level. Required clearances and access authorizations must be clarified before deployment for the specific personnel involved. This does not mean that the worldwide OTOKO® team as a whole is cleared for classified information. For initial discussions, we use an unclassified description; confidential project documents are only exchanged through agreed, permitted channels.

As the exclusive EMEA distributor for u.trust LAN Crypt, OTOKO® combines delivery of the solution with technical implementation at your organization. We handle customer-specific adaptations and modifications, installation and commissioning. First, we determine which systems and workflows are to be connected, which functions are needed and who will administer the solution afterward. This results in an agreed implementation scope, a pilot and a rollout plan. Modifications are documented and assessed against the respective approval: the approval of the original version does not automatically apply to every modified setup.

After commissioning, maintenance and Level 1-3 support remain part of our offering. Level 1 handles structured intake and initial triage, Level 2 the in-depth analysis of configuration and integration, Level 3 the resolution of complex technical root causes and the required coordination with the vendor. Support scope, availability, response times and permitted remote access are agreed to fit the project. In classified environments, we take the permitted access and communication channels into account. Maintenance changes are assessed and tested in a traceable way and put into operation through the agreed approvals.