Practical answer: A factory office network and its production systems have different risk and availability requirements. Placing PLCs, HMIs, office laptops and guest Wi-Fi in one flat network can allow routine IT problems to affect manufacturing. Start by identifying business and industrial assets, the necessary communication paths and the people responsible for production uptime.
How to structure the solution
Separate zones based on function and trust, not only on building location. Office users, servers, cameras, vendor access and production controllers may require distinct policies. Document protocol flows before introducing restrictive firewall rules: industrial devices may rely on older communication methods or fixed IP addresses. A controlled conduit through a firewall or gateway is preferable to broad any-to-any connectivity.
Implementation, evidence and ownership
Work jointly with the plant engineering team. During an initial survey, capture diagrams, switch ports, IP ranges, remote maintenance tools, unsupported systems and emergency stop considerations. Change one connection path at a time and prove that production workflows still function. Do not run disruptive scans against industrial controllers without the system owner approving a safe procedure.
Limits, risks and practical decisions
Segmentation is a program rather than a one-day firewall purchase. Define who can request changes, how exceptions expire and what telemetry is reviewed. SMNET can help assess network infrastructure and security components within a scoped project, while equipment manufacturers and plant owners retain authority over machine safety and control logic.
Implementation checklist for managers and IT teams
- Inventory controllers, HMIs and production support PCs
- Document critical cross-zone application flows
- Keep guest and office traffic outside OT zones
- Approve changes with factory engineering owners
- Avoid unapproved active scans on industrial assets
- Maintain a time-limited exception register
Evidence to request before sign-off
For this project, ask for an accountable owner, an asset or configuration baseline and a record of approved decisions. The relevant evidence should show which of the following controls were checked, by whom and on what date. Acceptance should depend on demonstrable operation rather than a product brochure or a verbal assurance.
A useful acceptance meeting has three participants: the Vietnam business owner, the technical implementer and—where required—the regional IT representative. Identify which work is included in ongoing support and which requires a separately approved project. Keep administrative access, documentation and renewal information under customer control. Review the procedure again after a staff change or significant infrastructure change.
Frequently asked questions
Can one firewall protect the entire factory?
A firewall is only one control. Architecture, identities, monitored paths, vendor access and change procedures also matter.
Should we block every connection to OT immediately?
No. Map required production traffic and implement changes in controlled windows with validation and rollback plans.
For a scoped assessment, see SMNET’s Cybersecurity and WatchGuard solutions. For operational assistance and escalation, explore IT Helpdesk and onsite support. Availability, site coverage, SLA and implementation pricing depend on an agreed service scope; no outcome or response time is guaranteed by this article.
Editorial note: This is a practical planning guide, not an audit of a specific customer, legal advice or a guarantee of security. Verify vendor features and regulatory requirements before implementation.



