Industrial manufacturing · Nine plants, seven cities
Enterprise security uplift
How a multi-site industrial company scoped a security programme across its network, devices, user access and sites.
Secure · Cybersecurity
Security architecture and zero trust design for Indian enterprises that want security built into the network, identity and cloud, not added after the audit. NetScale reviews where trust is assumed today, then designs defence-in-depth and zero trust controls, with risk assessments and compliance preparation. Each phase is fixed-scope and signed off separately.
Security Architecture and Zero Trust
Security architecture is the design of how controls fit together across the network, identity, endpoints and cloud.
Defence in depth layers those controls, so no single control has to hold on its own. Zero trust is a design in which no user, device or network location is trusted by default. Each request is checked before access is granted.
Compliance preparation means the controls are designed with the evidence an auditor asks for. Each recurring gap is closed with a working control and the evidence to show it.
The full DPDP programme, from data mapping to breach response, sits under DPDP readiness.
The governance system that keeps policies followed sits under Governance, risk and compliance frameworks.
The enterprise risk register, vendors included, sits under Enterprise risk management (ERM).
Security was added to close audit gaps. The gaps keep returning. Who owns fixing them before the next audit?
Our answer: Compliance preparation
Anything on the office network is treated as safe. What could a stolen laptop reach?
Our answer: Zero trust architecture
Remote access was opened for a project. Who closed it?
Our answer: Risk assessments and architecture review
Controls were bought one product at a time. Who designed how they fit together?
Our answer: Defence-in-depth design
Defence-in-depth architecture, zero trust design, risk assessments and compliance preparation, including DPDP readiness.
Layered controls across the perimeter, network segments, endpoints, identity and cloud, designed together so no single control has to hold on its own.
Access checked against identity, device and policy on every request and limited to what each role needs, built in phases from the highest exposure first.
Flat network segments, shared admin accounts, open remote access and missing logs found, ranked by risk and written up with the fix for each.
Controls designed with the evidence an auditor asks for, mapped to ISO 27001 and the DPDP Rules, and handed over as yours.
The security safeguards the DPDP Rules name, designed into the architecture: access control, encryption or masking, and monitoring and logging.
One request path, person to application, drawn three times.
You can stop at any phase boundary. The assessment is free, and each phase is priced in writing before it starts.How we engage
The DPDP Rules name reasonable security safeguards for personal data, including encryption or masking, access control, and monitoring and logging. The architecture builds them in. Legal interpretation stays with your counsel.
Source: Digital Personal Data Protection Rules, 2025 (external site)
The Directions of April 2022 require logs kept for a rolling 180 days within India, with clocks synchronised to NIC or NPL. The design sends them to a central store that meets both.
Estate size: sites, users, applications and cloud tenancies in scope.
Segmentation and identity today: whether the network is flat, and whether single sign-on and multi-factor login exist.
Existing controls that fit the design, and how many need replacing.
Compliance targets the design must evidence, such as DPDP or ISO 27001.
The most relevant engagement, with its numbers. Client names and the full write-up are shared in conversation.
Industrial manufacturing · Nine plants, seven cities
How a multi-site industrial company scoped a security programme across its network, devices, user access and sites.
Cloud platform and identityOur own information security and privacy management systems, run under both standards.
Certifications and technologyIt means access is decided request by request, not by where a device sits on the network. Each sign-in is checked against the user’s identity, the device’s state and a written policy. Access is then limited to what the role needs. We build it in phases, starting where the review finds the most exposure.
With segmentation and privileged access, because on a flat network one compromised device can reach everything. The review maps which systems can reach which, and which accounts hold admin rights. The first phase separates critical systems and puts admin access behind approval and logging. Later phases extend the same checks to every user.
No. Zero trust is a way of deciding access, and the firewalls you run are usually part of it. The review keeps what fits the design; you are not asked to replace everything. Where a gap needs a new control, it is priced in writing as its own fixed-scope phase before you commit.
An architecture review looks at how the controls are built; an ISO 27001 programme looks at how security is managed. The review finds where the network, identity and cloud assume trust, and designs the fix. ISO 27001 sets the policies, risk process and evidence around those controls. The review’s findings feed the programme’s risk register.
How the network, identity, endpoints and cloud trust each other, and where a compromise could spread. It covers segmentation, admin and vendor access, remote access, logging and the controls an auditor will ask about. The findings are written down and ranked by risk. The review is free, and the findings are yours either way.
It costs nothing and commits you to nothing. You get a written list of where your IT environment is exposed, and your team can act on it with or without us.