Every industry with a control network has a line to hold.
Wherever a business network meets the systems that run a process, a few firewall rules decide what can cross. Pick an industry to see where that line usually sits, one crossing that should not be there, and the rules it answers to.
- ManufacturingStop one bad laptop from stopping the line.
- Water and wastewaterKeep the treatment plant off the office network.
- Oil and gasKeep the pipeline running when IT has a bad day.
- Electric powerSee every firewall rule into the Electronic Security Perimeter.
- Pharmaceuticals and life sciencesProtect the batch, not just the network.
- Defense manufacturingShow the shop floor is scoped, not forgotten.
- Ports and maritimeGet terminal segmentation ready before the Coast Guard asks.
- Rail and transitKeep passenger systems away from signaling.
- Warehousing and logisticsKeep the dock moving when the office network goes down.
Pharmaceuticals and life sciences
Pharmaceutical sites run batch control, clean room environment and lab systems that must stay validated. SegAudit shows the rules that let business and building systems reach production, and a change you can plan around a validation window.
What crosses the line in pharmaceuticals and life sciences
Each one is a finding ranked by risk, with the rule that allows it, the hosts that used it when a traffic log is loaded, and the change that closes it.
- Building management in the production zone
The building management system and bioreactor controllers share one zone.
- Lab systems reaching batch control
Lab instruments reach batch execution on any service.
- Vendor access with no end
Equipment vendor rules stay open between visits.
- Validated systems behind broad rules
Validated systems sit behind rules that allow far more than the sessions in the traffic log.
Illustrative examples of what an audit can find. They are not from a customer.
The rules pharmaceuticals and life sciences answers to
SegAudit judges the controls a firewall's evidence can speak to as supported, partial or gap, and shows each one again after the change. It helps you assess segmentation; it does not certify compliance.
| Rule | What it asks of segmentation | Judged from the evidence |
|---|---|---|
| IEC 62443-3-3 | Zones and conduits: network segmentation (SR 5.1), zone boundary protection (SR 5.2) and least functionality. | 9 controls |
| NIST CSF 2.0 | Networks protected from unauthorized logical access (PR.IR-01), asset inventories and log monitoring. | 10 controls |
| ISO/IEC 27001:2022 Annex A | Segregation of networks (A.8.22), networks security (A.8.20) and logging. | 7 controls |
| NIS2 Article 21(2) | Cybersecurity risk-management measures for essential and important entities in the EU. | 6 controls |
Control by control in the frameworks overview. Confirm the versions in force for your audit period.
Who runs the audit
The same audit either way. What differs is who approves the change.
Asset owners
Your own firewall team runs the audit on its own sites, every quarter, and approves each change through its own change process. Priced per site with the Asset Owner edition.
For asset ownersConsultants
You assess a client's sites and deliver the findings and the fix under your firm's letterhead. The client's team approves. Professional or Engagement.
For consultantsSee what crosses the line on your own firewalls.
Export a firewall configuration, add a traffic log if you have one, and read the findings on your own workstation. Nothing leaves it, and SegAudit never connects to your network.
Step-by-step export guides, for customers and trial holders: Palo Alto, FortiGate, Cisco ASA, Cisco FTD, Check Point.