Manufacturing
Could a route from the office network reach the plant floor?
Questions worth testing in a plant environment.
Which vendor and integrator connections can reach production networks?
Persistent remote access is common, and it often outlives the project that needed it.
Where does enterprise identity cross into plant systems?
Shared accounts, domain trusts, and jump hosts can turn an office compromise into plant access.
How far could one phished laptop get toward the IT/OT boundary?
We test from realistic footholds and stop at the boundary your team has agreed is safe.
What can be tested without putting production at risk?
Windows, exclusions, and observation-only areas are agreed with operations before any testing starts.
Testing that respects uptime.
Production comes first. These are agreed in writing before testing begins.
- Testing windows and exclusions agreed with operations
- Observation-only methods where active testing is not safe
- Named contacts and a stop procedure for every window
- OT and wireless work scoped only where safety constraints are agreed
An example route from vendor access toward production.
An illustrative example, not a customer finding. It shows how a path is recorded from first model to retest.
Path record: illustrative example
Not customer data. No live values.
Example route
- Entry pointVendor remote access accountPossible, not a finding
- HopShared engineering workstation loginPossible, not a finding
- HopDomain trust into the plant networkPossible, not a finding
- ObjectiveProduction supervisory systemsPossible, not a finding
Modeled · Ethos
A possible route from vendor access to supervisory systems is identified from known context. Not yet a finding.
- Modeled: possible, not a finding
- Confirmed by an operator, with evidence
- Where your team broke the route
A retest shows whether this specific route still works. It is not a guarantee that no other route exists.
Start with the boundary. Keep watching it.
Scope and cadence follow from the outcome you need. Some questions are answered by a bounded penetration test of the connections you are most concerned about. Where vendors, systems, and accounts keep changing, Ethos keeps the same record current so Hoplite operators can return to the paths that matter. We recommend the fit once we understand what you need to prove.
- Scope and rules agreed with your teams
- Confirmed paths with evidence
- Modeled paths kept apart from findings
- Retest under agreed terms
Tell us where your plant and office networks meet.
We will talk through vendor access, plant connectivity, and the testing limits your operations team needs, then suggest a scope.