Information Security & Firewall: coverage in São José - SC

Separating operations from administration

The separation does not have to be radical to be effective. The goal is for administrative traffic never to reach the operational devices directly, and for communication between the two sides to happen only where there is a genuine need — usually a management system that has to read production or shipping data.

That protects precisely what cannot be updated often. Controllers, terminals, and embedded equipment run software that rarely receives a patch, because the window for it does not exist. If the device cannot be fixed, what can reach the device can be reduced.

The devices nobody updates

Cameras, access controllers, network printers, and barcode readers commonly sit in the environment for years without any software maintenance. They are the weakest link and the least remembered one. Keeping them on a network of their own, with restricted reach, is a cheap measure — and it prevents a known vulnerability in a low-cost device from opening a path to the management system.

Third-party access: maintenance, freight carriers, service providers

Industrial environments receive external access all the time: the manufacturer performing remote maintenance on a machine, the freight carrier integrating a system, the contractor reaching one specific device. Each of those accesses tends to be granted in a hurry, when the problem appears, and is rarely reviewed afterwards.

The healthy path is named access, limited to the target equipment, with a defined expiry. The machine vendor needs to reach the machine — not the file server, not the administrative network. And when the contract ends, the access ends with it, without depending on anyone remembering.

Keeping the shipping line running

In a distribution center, a link outage means invoices not issued and trucks parked in the yard. The cost is known and usually high, which changes the conversation about a second link. SD-WAN keeps two links active with automatic failover when one degrades, without depending on manual intervention at an hour when there may be no IT staff around.

It also allows traffic to be treated differently: what is critical and sensitive to interruption follows the most stable path, while bulky, interruption-tolerant traffic uses the other. A large file synchronization stops competing with document issuance.

Head office in the capital, operations here

It is common for administration to sit in Florianópolis and the operation in São José, sometimes with a third unit in Palhoça or Biguaçu. SD-WAN connects those sites under a single policy, administered from one place. Without it, each address accumulates its own configuration, and the most fragile unit ends up defining the exposure of the whole group.

Deployment with the operation running

The work runs in phases, with the new environment brought up in parallel with the existing one and migration in stages, each with a defined and tested rollback point. In an operation that ships daily, cutting everything over at once is not an option — and the real window is usually short, between shifts or on a weekend.

After the cutover, the configuration stays documented and version-controlled. That makes it possible to audit what changed and when, and to rebuild quickly if necessary — relevant in an environment where knowledge tends to be concentrated in very few people.