OT security protects the controllers, sensors, cameras and building systems that run physical operations. In India it means finding every connected device, separating it from the office network, fixing default passwords and vendor remote access, and watching traffic passively, all without disturbing the process. We assess and implement under written authorisation, inside your change process, with safety and uptime first.
Key takeaways
- OT and IoT need a different playbook: old protocols, devices you cannot patch, and safety before everything.
- We find devices mostly by listening to traffic, not by scanning live controllers.
- Segmentation into zones and conduits, as IEC 62443 describes, does more than any single product.
- CERT-In's 6-hour reporting covers attacks on SCADA, OT systems and IoT devices.
- Power sector entities face the CEA cyber security regulations from 1 April 2027.
A factory line, a telecom site, a substation and an office tower have something in common: a layer of controllers, sensors, cameras and building systems that nobody thinks about until it stops. That layer is operational technology (OT) and the Internet of Things (IoT). OT security in India is now a board question, because these systems are more connected than ever: to the corporate network, to the cloud dashboards, and to the vendors who maintain them from afar.
Mirav Labs assesses and secures these environments for manufacturers, telecom operators, utilities and building owners. We work around your process, not through it. Safety and uptime come first, and every test happens only with your written authorisation and an agreed scope.
Why OT and IoT break the IT security playbook
Most security programmes are built for laptops, servers and cloud accounts. Bring that playbook to a plant floor and it fails in predictable ways.
- Old protocols with no authentication. Many industrial protocols were designed for closed serial networks. Anything that can reach a controller can often send it commands.
- Devices you cannot patch. A programmable logic controller (PLC) may run for twenty years. Updating its firmware can mean a shutdown, a vendor visit and requalification. Some devices have no update path at all.
- Safety and uptime first. In IT, you isolate a suspicious machine. In OT, cutting a link can stop a line, trip a feeder or open a door that should stay shut. Every control has to be judged by what it does to the process.
- Scanning can hurt. An aggressive network scan that a server ignores can hang a fragile controller or a camera.
- Vendors with remote access. Integrators and equipment makers often keep their own remote connections for support. These are frequently the least visible way into the plant.
- Flat networks. Building systems, cameras, controllers and office PCs often share one network, so one infected laptop can reach everything.
So OT and IoT security, also called industrial cybersecurity or ICS security (industrial control systems), is less about buying a product and more about knowing what you have, separating it, and changing how people and vendors reach it.
What Indian rules and global standards expect
You do not need to read every standard to start, but you should know which ones shape the work.
IEC 62443
IEC 62443 is a series of standards, developed jointly by the IEC and the ISA99 committee, on security for industrial automation and control systems over their whole life cycle. It covers both organisational and technical sides. Part 2-1 sets out an asset owner's security programme. Part 3-2 describes how to partition a system into zones (groups of assets with common security needs) and conduits (the communication paths between them). Part 3-3 defines system requirements and four security levels, and Part 4-2 covers requirements for components such as embedded devices. We use its vocabulary because your integrators and equipment vendors increasingly do too.
CERT-In reporting
The CERT-In directions of 28 April 2022 require service providers, intermediaries, data centres, body corporates and government organisations to report listed cyber incidents within 6 hours of noticing them. The list expressly includes attacks on critical infrastructure, SCADA and operational technology systems, and attacks on IoT devices and associated systems. The same directions require logs of ICT systems to be kept for a rolling 180 days within India, clocks to be synchronised to NIC or NPL time servers (or sources traceable to them), and a point of contact to be named for CERT-In. Most plants are not ready to meet a 6-hour clock for an OT incident, because nobody is watching OT traffic in the first place.
Power sector: CEA
The Central Electricity Authority released its guideline on cyber security in the power sector on 7 October 2021. On 31 July 2026 it notified the CEA (Cyber Security in Power Sector) Regulations, 2026, which come into force on 1 April 2027 (a few provisions start on dates the Authority will set separately). They apply to entities that own, operate or manage OT linked to the interconnected power system, and to IT physically or logically connected to that OT. For generating companies, captive plants and energy storage, they apply at 50 MW installed capacity or more. Among much else, entities must test their cyber crisis management plan through exercises and mock drills at least once a year, and vendors must supply validated security patches for the contract period or useful life (whichever is later), a bill of materials including firmware for critical systems, and end-of-life details.
Critical information infrastructure
Under section 70 of the Information Technology Act, critical information infrastructure is a computer resource whose incapacitation or destruction would have a debilitating impact on national security, economy, public health or safety, and the government may declare such a resource a protected system. Section 70A provides for a national nodal agency for its protection, which is the National Critical Information Infrastructure Protection Centre (NCIIPC). If your systems have been declared protected, or may be, our work is designed to fit alongside the obligations that come with it.
How we assess and secure OT without stopping it
We follow five steps. Each one is planned with your operations and safety teams, and nothing touches production control logic except through your own change process.
Every controller, sensor, camera and device
Separate OT and IoT from IT
Passwords, firmware, vendor access
Watch passively, never disturb
Playbooks that keep people safe
1. Inventory
You cannot protect what you cannot see. We build a list of every controller, sensor, camera, gateway and connected device, with its firmware, the protocols it speaks and who talks to it. We do this mostly by listening: a copy of traffic from a mirror port or network tap, plus your drawings, vendor documents and a walk of the site. Active queries happen only where you agree, in a window you choose, using methods the device vendor supports.
2. Segment
Next we draw the zones and conduits. OT and IoT come off the office network. Building systems, cameras, production cells and safety systems each sit in their own zones, and the conduits between them allow only the connections the process needs. Where data has to reach IT or the cloud, it goes through a controlled boundary, not a direct route. Often this is the single change that cuts the most risk.
3. Harden
Then the practical fixes. We change default and shared passwords, switch off unused services, and plan firmware updates with the operator and the vendor rather than pushing them. Vendor remote access gets special attention: one controlled entry point, named accounts, multi-factor login, time-limited sessions that someone on your side approves, and recording of what was done. For devices that cannot be patched, we add compensating controls around them.
4. Monitor
We set up monitoring that watches a copy of the traffic, so detection never adds load or risk to the process. It learns what normal looks like, such as which engineering station programmes which controller, and flags new devices, new connections and unexpected commands. Alerts feed your existing security operations, with enough OT context that an analyst knows what the asset does.
5. Respond
Finally, playbooks written with operations, not just for them. For each likely scenario they say what can be isolated, what must keep running, who decides, and how to fall back to manual operation safely. They also carry the reporting clocks, including CERT-In's 6 hours. We rehearse them as tabletop exercises. For recovery and backups across IT and OT, see our cyber resilience work.
Our rules of engagement
Testing happens only with written authorisation and an agreed scope that names systems, methods and time windows. We prefer passive methods on live systems and run active tests on test benches, spares or during planned shutdowns. We never change production control logic, setpoints or safety systems ourselves; any change goes through your management of change process, approved by the people accountable for the plant.
Building systems: BMS, access control and CCTV
Building management system security gets less attention than the factory floor, but the risks are similar. A BMS controls heating, cooling, lifts and power. Access control decides who enters. CCTV records everyone who does. These systems are often installed and maintained by facility vendors, connected to the internet for remote support, and left with factory passwords.
We apply the same five steps: find every panel, controller, camera and recorder; give them their own zones; close direct internet exposure and unmanaged vendor access; monitor for change; and agree how to respond without locking people in or out.
There is a data protection angle too. CCTV footage, badge records and visitor logs are personal data. Under the DPDP Act, a Data Fiduciary must take reasonable security safeguards to prevent a personal data breach, and Rule 6 lists measures such as access control and logs that let you detect and investigate access. These duties apply from 13 May 2027. For the detail, read DPDP Ready's guide to DPDP security safeguards.
What you get
Every engagement ends with things your engineers and auditors can use, not just a report.
| Deliverable | What it contains | Who uses it |
|---|---|---|
| Asset inventory | Every OT and IoT device with location, firmware, protocols, owner and criticality | Operations, maintenance, security |
| Network and data-flow map | How devices connect today, including vendor and cloud links | Engineering, network team |
| Zones and conduits design | Target segmentation mapped to IEC 62443 concepts, with a phased migration plan | Engineering, integrators |
| Risk register | Findings ranked by safety, operational and data impact, with fixes and compensating controls | Plant head, CISO, board |
| Vendor remote access standard | One controlled route, approvals, logging and contract clauses for suppliers | Procurement, security, vendors |
| Monitoring setup | Passive sensors placed, normal behaviour baselined, alerts routed to your team | Security operations |
| Incident playbooks | OT-specific scenarios, isolation decisions, manual fallback and CERT-In reporting steps | Operations, security, management |
| Hardening plan | Password, firmware and configuration changes sequenced into your maintenance windows | Maintenance, operations |
Where your devices push data to cloud platforms, our API and supply-chain security work covers the gateways, APIs and third-party software in that path. If the data must stay in India, see sovereign cloud and data residency.
How to start
Most engagements begin with one site or one building. In a first conversation we agree the boundary, who in operations and safety must be involved, and what is off limits. We then put the authorisation and scope in writing, start with a passive inventory, and come back with a map and a ranked list of fixes you can schedule into normal maintenance.
If you run a plant, a network or a building portfolio and want to know where you stand, talk to us.
Frequently asked questions
What is the difference between OT security and IT security?
IT security protects data and puts confidentiality first. OT security protects physical processes, so safety and availability come first. OT devices often run for decades, use protocols with no authentication, and cannot be patched or rebooted on demand, so the controls have to work around the process rather than interrupt it.
How do you do an IoT security assessment without disrupting production?
We start passively: we read traffic from a mirror port or tap, so nothing new talks to your controllers. Any active test runs only in an agreed window, on a test bench or spare unit where possible, under written authorisation and your change process. We never alter production control logic ourselves.
What is IEC 62443?
IEC 62443 is a series of standards, developed jointly by the IEC and the ISA99 committee, on security for industrial automation and control systems across their life cycle. It covers asset owner programmes, risk assessment and partitioning a system into zones and conduits, system security levels, and requirements for components and product development.
Do CERT-In's 6-hour reporting rules apply to OT and IoT incidents?
Yes. CERT-In's directions of 28 April 2022 require reportable incidents to be reported within 6 hours of noticing them, and the list includes attacks on critical infrastructure, SCADA and operational technology systems, and attacks on IoT devices. The same directions require logs to be kept for a rolling 180 days within India.
How do I secure a building management system, CCTV and access control?
Put them on their own network segments, change default credentials, update firmware on a planned schedule, and remove direct internet exposure and unmanaged vendor access. Because CCTV footage and access logs are personal data, access to them should be limited and logged too.
Do the CEA cyber security regulations apply to my power plant?
The CEA (Cyber Security in Power Sector) Regulations, 2026 come into force on 1 April 2027 and apply to entities that own, operate or manage OT linked to the interconnected power system, and the IT connected to it. For generating companies, captive plants and energy storage, they apply where installed capacity is 50 MW or more. Check the notification for your case.
Scope it with us
A 30-minute call to understand your systems and what good looks like. We aim to send a written, fixed-scope proposal within three working days.
Related services
This page describes engineering and security services. Where it mentions laws, rules or standards, it is general information, not legal advice.