Cybersecurity
Zero Trust Security: Stop Trusting Your Own Network
Affix Center · · 9 min read

Quick answer: Zero trust security is an approach where no user, device or connection is trusted by default, even inside the office network. Every request is checked for identity, device health and need before access is given, and access is limited to what each role needs. Most firms start with MFA, device checks, least privilege and network segmentation.
Most office networks still work like a building with one guarded gate. Once someone is inside, through a VPN, a shared Wi-Fi password or a phished employee login, they can often reach file servers, ERP, backups and admin panels. That is why one stolen password so often turns into a ransomware attack on the whole company.
Zero trust security closes that gap. It does not mean buying one product or replacing your firewall. It is a way of designing access so that being "inside" no longer means being trusted. This guide explains the idea in plain words, compares it with the traditional model, and gives a step-by-step plan that Indian SMEs, enterprises and government offices can follow without stopping daily work.
What Is Zero Trust Security?
The idea is often summed up as "never trust, always verify". The US National Institute of Standards and Technology describes the approach in its Special Publication 800-207, Zero Trust Architecture, published in 2020. The core points are simple:
- Verify every request: check who the user is, which device they use and whether that device is healthy, every time they access a resource.
- Least privilege: give each person and system only the access their role needs, for as long as they need it.
- Assume breach: design as if an attacker is already inside, so one compromised account cannot reach everything.
- Protect resources, not the perimeter: put controls around each application and data store, not only at the office edge.
- Watch continuously: log access and look for unusual behaviour, because trust can change during a session.
Traditional Network Security vs Zero Trust
The table shows how the two models handle the same everyday situations.
| Situation | Traditional perimeter model | Zero trust security model |
|---|---|---|
| Employee connects from home | VPN gives access to the whole office network | Access only to the specific apps the role needs, after identity and device checks |
| User logs in at the office | Trusted because the device is on the LAN | Checked the same way as a remote login |
| A laptop is infected | Malware can scan and spread across flat networks | Segmentation and app-level access limit how far it can move |
| Vendor needs support access | Shared VPN account, often left active | Time-bound access to named systems, logged and reviewed |
| Password is phished | Attacker logs in like the real user | MFA and device checks block or flag the login |
| Staff member leaves | Accounts removed manually, some forgotten | Central identity removes access to every app at once |
Why the Old Model Keeps Failing
The perimeter model was built for a time when staff, servers and data all sat in one office. Today, work happens on laptops at home, phones on mobile data, cloud apps like Microsoft 365 and Google Workspace, and vendor portals. Each of these is a door the firewall does not see.
- Credential theft: phishing and password reuse give attackers valid logins. Fix: strong MFA and sign-in risk checks.
- Flat networks: every device can talk to every server. Fix: segmentation by role and system.
- Over-privileged accounts: staff keep access from old roles; admins use one account for everything. Fix: least privilege and separate admin accounts.
- Unmanaged devices: personal laptops and phones reach company data. Fix: device checks before access.
- Blind spots: no one reviews who accessed what. Fix: central logging and alerting.
The Building Blocks of Zero Trust
Identity
One central directory for users, with single sign-on to business apps and MFA for every login. Phishing-resistant methods, such as authenticator app number matching or security keys, are stronger than SMS codes. Our guide to multi-factor authentication implementation covers the rollout in detail.
Devices
Know every device that reaches company data. Check that it is managed, encrypted, patched and running endpoint protection before it gets access. See our posts on endpoint security and mobile device management.
Network
Split the network into segments, for example users, servers, CCTV and IoT, guests and management, and allow only the traffic each segment needs. Replace broad VPN access with app-level access where possible. Our network security services guide explains segmentation options.
Applications and data
Control access per application and classify sensitive data so that the strongest checks protect the most important information.
Visibility
Collect sign-in, device and network logs in one place and review alerts. A managed SOC can do this round the clock if you lack an in-house team.
How to Implement Zero Trust Security: Step by Step
This is the fix. You do not need to do everything at once. Each step reduces risk on its own.
- Map users, devices, apps and data: list who works for you, which devices they use, which applications they reach and where sensitive data lives, and rank what would hurt most if it were stolen or locked.
- Centralise identity and turn on MFA: move users to one directory, connect business apps through single sign-on and require MFA for every user, starting with admins, email and remote access.
- Apply least privilege: remove access people no longer need, create separate admin accounts, and review access to finance, HR and server systems every quarter.
- Check device health before access: enrol company laptops and phones in device management, require encryption, updates and endpoint protection, and limit what unmanaged devices can reach.
- Segment the network: separate servers, user devices, CCTV and IoT, guests and management interfaces, and allow only the connections each one needs.
- Replace broad VPN access: give remote staff and vendors access to specific applications instead of the whole network, with time limits for vendor sessions.
- Log, monitor and test: send sign-in and network logs to a central place, set alerts for unusual access, and test the controls with a security assessment at least once a year.
A realistic first 90 days
- Days 1 to 30: asset and access inventory, MFA for admins and email, removal of shared and stale accounts.
- Days 31 to 60: single sign-on for main apps, device enrolment, separate admin accounts.
- Days 61 to 90: first network segments for servers and CCTV, vendor access rules, central logging.
Where to start, by type of organisation
- Small offices (under 50 users): the biggest gains come from MFA on email and cloud apps, removing shared logins, keeping laptops updated and putting guests, CCTV and printers on separate networks. Most of this uses licences you already have.
- Mid-size companies with ERP and branches: add single sign-on, separate admin accounts, device management and a segmented server zone. Review vendor and branch access, since these links are often wide open.
- Enterprises and regulated firms: plan zero trust as a programme with owners for identity, endpoints, network and monitoring, and link it to your audit and risk reporting.
- Government departments and PSUs: focus on admin access to portals and servers, vendor and contractor access, and logging. Many departments rely on outside agencies for development and support, so time-bound, logged access for those agencies is an early win.
Whatever your size, write down who owns each step and how you will measure progress, for example the share of users on MFA, the number of admin accounts and the number of open firewall rules. Simple numbers like these show management that risk is going down.
Common Mistakes When Moving to Zero Trust
- Treating it as one product: a vendor may sell "zero trust", but the result depends on your identity, device and access design. Buy tools to support a plan, not instead of one.
- Starting too big: trying to segment everything in one weekend breaks business apps. Start with the most sensitive systems.
- Forgetting user experience: constant prompts push staff to find workarounds. Use single sign-on and risk-based checks to keep logins smooth.
- Ignoring vendors and service accounts: third-party access and old service accounts are often the weakest link.
- No testing: controls that are never tested give false comfort. Regular VAPT services in Mumbai or elsewhere can show whether segmentation and access rules really hold.
Frequently Asked Questions
Is zero trust security only for large companies?
No. The principles scale down well. A small business can start with MFA, separate admin accounts, device updates and a separate network for guests and CCTV, mostly using tools it already pays for.
Does zero trust mean I can remove my firewall?
No. Firewalls remain useful for segmentation and filtering. Zero trust changes how you decide who gets access, so the firewall becomes one of several controls rather than the only one.
Is zero trust the same as ZTNA?
Zero trust network access (ZTNA) is one technology that applies zero trust to remote access, giving users access to specific apps instead of the whole network. Zero trust as a whole also covers identity, devices, data and monitoring.
How long does it take to implement zero trust?
It is a programme, not a one-time project. Many organisations see strong gains within three months by fixing identity, MFA and admin access, then continue with segmentation and monitoring over the following year.
Does zero trust help with compliance in India?
Controls such as MFA, least privilege, logging and access reviews support the reasonable security safeguards expected under the DPDP Act and the log and incident duties in CERT-In directions. Check your exact obligations with your adviser.
How Affix Center Can Help
Affix Center helps organisations in Mumbai and across India move to zero trust in practical stages. We review your current access, identity and network design, build a phased plan, and help roll out MFA, device management, segmentation and monitoring without disrupting daily work. Our cyber security services in Mumbai cover assessment, design and ongoing support, and our managed IT services team can run the day-to-day controls.
Ready to stop one password from opening your whole network? Talk to our team about a zero trust security plan for your organisation.