Macula Mesh Use Build Macula for… Docs Contact

Macula · sectors · All Macula for… pages

Macula for Operational Technology

Macula lets your operators read and command an industrial controller from wherever they are, through a small gateway next to the controller. The gateway only makes outbound connections, so no port on the site accepts a connection from the internet, and every command carries the identity of the operator who sent it. A port forward on the site's router, by contrast, leaves the controller reachable from the internet, and a vendor's remote-access box lets in whoever has the vendor's shared login. We are looking for partners to build it with.

Without Macula: a port forward or a vendor box, and one shared password

Cold rooms, pump stations, building controls and production lines all need service from a distance. Without Macula, the usual setup is a port forward on the site's router or a vendor's remote-access box, protected by one account that everybody shares.

open to scanners

A forwarded port is open to every scanner on the internet

Internet-wide scanners find a forwarded port just as the service engineer does. Anyone who finds it reaches the controller's login page.

no record of who

A shared account makes the controller's log useless

When the whole team, the installer and the vendor use the same account, the controller's log cannot say which person changed a set point. A vendor's remote-access box lets in whoever has the vendor's shared login, and its log cannot say which person that was either.

unpatched for years

Protection inside the controller waits for firmware updates that rarely come

Controllers often run for many years on the firmware they shipped with. The protection therefore has to sit in front of the controller, on the network, not inside it.

With Macula: a gateway that dials out, and a realm whose admin admits what may reach it

The Macula Mesh is a network of stations. Stations link up to form the mesh, keep its phonebook (a Kademlia DHT: which node offers what, and where to reach it), and relay calls, encrypted end to end, between the parties a realm admits. There is one mesh and many Macula Realms. Each realm is an identity space on the mesh with its own key: its operator admits anything that can be given an identity, such as people, organisations, services, machines and devices, gives each a certificate signed with that key, and can revoke it. Anyone can run a station, as many as they like; the more stations, the stronger the mesh. Macula runs a number of seed stations and a community realm; a company or sector body can run its own realm under a Macula licence. The gateway at the machine then decides, command by command, which of them may send it. The operator's client and the site's gateway only make outbound connections; neither accepts an incoming one. Stations link to each other, so a client at one site reaches a gateway that dialled a different station.

The operator's client and the site's gateway each make an outbound connection to a station, and the linked stations carry the call between them. A command for the machine travels back over the gateway's own outbound connection. No device on the site accepts an incoming connection.

What Macula promises

no inbound port

No port listens on the site

The gateway connects out to the mesh. A scan from the internet finds nothing to talk to, and you can retire the port forward and the vendor box.

one command, one permission

Each command names who may send it

Reading a temperature, changing a set point and starting a defrost are separate capabilities. Writes go only to the operator identities you list. Anyone else is refused before the command runs.

end-to-end encryption

The relay station cannot read the commands

Calls are encrypted to the gateway's own key. The station in the middle forwards them without reading them, and a call sent in the clear is refused.

no replays

A captured command cannot be sent again

Every command carries its own id and a timestamp. The gateway refuses a command it has already seen, and one that arrives too late.

per-operator audit

The audit names the real operator

The gateway records who sent each command, which machine it touched and what happened. The controller only ever sees the gateway.

no firmware change

Works with the controller you have

The gateway talks to the controller's existing interface on the plant network, with its own strong account. The old shared password never crosses the mesh.

See it run

Every promise above can be checked in an open-source lab that runs on a single laptop. Each lab starts a simulated controller with the common weaknesses, an exposed port and a default admin account. You run the attack first, then the fix. The labs live in macula-demos; here are two of them.

Lab · one site

freezers-on-mesh: close the port forward, keep remote service

A cold room's controller sits behind a port forward with a default admin account. First you play the attacker, then you put the gateway in front.

What you will do

  1. Scan the exposed site, read the freezers without a password and take control with the shared admin account.
  2. Switch the dashboard to the mesh. The same freezers appear, served by the gateway.
  3. Close the port forward. Scan again and find nothing, while the dashboard keeps working.
  4. Send a command as a stranger, then replay an old one.
operator write: okstranger: unauthorizedreplay: command_replayed

Lab · two sites

warehouses-on-mesh: one operator, two sites, no open ports

The same company opens a second warehouse. A quality manager at site A watches and commands the freezers at site B. Each site has its own gateway and its own station, and the two stations are linked.

What you will do

  1. Pick site B on the dashboard at site A and read its four freezers through the linked stations.
  2. Change a set point at site B. The gateway's audit names you; the controller sees only the gateway.
  3. Capture the traffic the station relays and search it for the freezer data. It is not there.
  4. Check both sites for listening ports. Neither gateway nor controller has one that the outside can reach.
cross-site call: sealedclear call: sealed_requiredstranger: unauthorized

Where it fits

Any site where a controller is reached from outside the plant network. The gateway is the only part that talks the controller's protocol. The labs use a controller with a web interface; another kind of machine needs its own adapter, and the mesh side stays the same.

Cold rooms and refrigerationPump and lift stationsBuilding climate and HVACMachine builders' remote serviceGreenhouses and barnsBatteries and heat pumps

Build it with us

Partners bring the machines, the controllers and the sites; we bring the station software, seed stations and the gateway, and each company gets a realm of its own under a Macula licence. We are looking for partners in three roles.

pilot a site

Operators of sites with machines

You run cold rooms, pump stations, buildings or barns that someone reaches from outside. Put a gateway in front of one site with us and retire its port forward.

bring a controller

Machine builders and integrators

Your controllers use their own protocols. The mesh side stays the same for every machine; together we build the adapter for yours, so your service teams reach it without an open port.

research and audit

Security and research partners

A lab, a university group or an auditor who wants to attack the setup, measure it, and publish what they find.

Try a lab on your laptop

You need Docker with Compose. One script builds the station, the gateway and the dashboard, waits for them to start, and leaves the lab ready.

# the one-site lab git clone https://github.com/macula-demos/freezers-on-mesh cd freezers-on-mesh ./scripts/mesh-demo.sh # then open http://localhost:4000

The two-site lab starts the same way from warehouses-on-mesh. Each repository has a demo script to follow and a page that says exactly what the lab proves.