What is zero trust?
Zero trust is a security model based on the principle “never trust, always verify.” No user, device or network segment is automatically considered trustworthy; every access is checked individually based on identity, device state and context, and limited to the minimum necessary.

Zero trust: definition and idea
Classic security follows the castle-and-moat principle: anyone inside the company network is considered trustworthy. That no longer works when employees work from home, data sits in the cloud and service providers need access. Zero trust dispenses with this advance of trust: location within the network alone does not justify permission.
Zero trust is not software you buy but an architectural approach. It is described, among others, in the NIST publication SP 800-207, and Germany’s BSI also takes up the concept. It is implemented step by step and across several technologies.
The core principles
Three ideas underpin the model: every access is explicitly verified, permissions are limited to what is necessary (least privilege), and you assume an attacker may already be in the network (assume breach). This leads to measures that contain damage instead of merely defending the outer perimeter.
Zero trust does not mean distrusting employees. It is about basing decisions on verifiable signals—who is signing in, from which device, with what risk—rather than on the assumption that everything inside your own network is harmless. This makes it harder for attackers to move around, even if an account has been compromised.
- Strong identities with multi-factor authentication as the foundation
- Device checks: access only from up-to-date, managed devices
- Microsegmentation instead of a flat network
- Access to individual applications instead of the whole network (ZTNA)
- Continuous monitoring and automatic response to anomalies
Real-world example: a supplier with service provider access
A machinery supplier with 150 employees gives an external maintenance service access to the company network via VPN. The access is not adjusted for years, and the password is passed on several times. In a worst case, a hijacked service provider account would open up access to design data and ERP alike.
Under a zero trust approach, the service provider gets a personal account with two-factor login, only for the maintenance system, only within the agreed time window and only from a verified device. The session is logged, and unusual access triggers an alert. A stolen password alone no longer suffices for access, and the damage would stay limited to the maintenance system.
Getting started, limits and implementation
Zero trust is a journey, not a switch. Companies start with the biggest risks, usually identities, multi-factor sign-in and device management, for example via Microsoft Entra ID with Conditional Access and Intune. Typical mistakes are equating it with a single product, rules so rigid that they paralyze day-to-day work, and a missing inventory of existing accounts and systems.
Nano Concepts helps with an inventory of accounts, devices and access paths, the introduction of multi-factor sign-in and device management, and the gradual replacement of broad VPN access. The plan is based on your risk and your budget, not on a product catalog. We support this as a project or as ongoing consulting.
Frequently asked questions about Zero trust
No. Zero trust is a concept made up of several building blocks: identity management, multi-factor sign-in, device management, segmentation and monitoring. Vendors advertise zero trust products, but only the interplay and the rules behind it make a zero trust architecture.
It can replace or complement it. Instead of access to the entire network, users get access only to individual applications via zero trust network access (ZTNA). Many companies switch gradually and initially run both approaches in parallel.
Yes, in scaled-down form. Multi-factor sign-in for all accounts, managed devices, graduated permissions and a cloud directory with access rules are feasible even for ten employees and reduce risk considerably, without requiring a large project.
With an inventory: which accounts, devices, applications and access paths exist? Next come the most important levers—multi-factor sign-in, removing unnecessary admin rights and device management. Segmentation and monitoring follow, ordered by the greatest risk.
Matching services

Web Security
Find and fix vulnerabilities – for websites, online stores, customer portals and custom web applications.
Learn more
Technology Consulting
Software selection, architecture, code review and a digitalization roadmap – independent and implementation-oriented.
Learn more
IT Rollouts
Hardware, workstation and branch rollouts plus Windows migration – across Germany with partner teams on site.
Learn moreRelated terms
Relevant for these industries
Related magazine articles

Digital Transformation for SMEs: Roadmap, Data, Change
Digital transformation in mid-sized companies rarely fails because of missing tools but because of unclear goals and isolated solutions. Here is how a target picture, priorities and a data foundation lead to measurable results.
Read more
Outsourcing Field Service: When External IT Technicians Pay Off
Your own technicians at every location? For many companies, that’s not cost-effective. Here’s when external field service teams are the better choice, which billing models exist and what to put in the contract.
Read more
Web Security: OWASP Top 10 and a Pragmatic Checklist for Teams
Most security vulnerabilities follow familiar patterns. With the OWASP Top 10 as a guardrail and a prioritized checklist, you close typical gaps before they become a problem.
Read more