ProtoCall legalAuthorisation is required
Use ProtoCall only on systems and networks that you own or have been explicitly authorised to test. Follow the site owner's permit, cybersecurity, change-control and maintenance-window requirements. The operator is responsible for confirming that the planned test is within the authority granted.
Before testing live OT
- Identify the exact host, adapter, endpoint, protocol and permitted test scope.
- Assess whether discovery, session creation, reads, retries or packet capture could affect a legacy or resource-constrained device.
- Start with the smallest bounded test and conservative timing.
- Confirm backups, rollback, communications and an operator stop condition.
- Use an isolated lab or Emulator scenario before testing production where practical.
- Do not expose a simulator or diagnostic listener to an untrusted network.
Inspector boundary
Inspector is designed for read-only diagnostics and evidence. It may still perform discovery, open protocol sessions, send bounded probes, read data and capture traffic. Read-only does not mean traffic-free or risk-free. It must not be used as the sole basis for a safety-critical or production-control decision.
Emulator boundary
Emulator creates test endpoints and controlled behaviours. Depending on the scenario, it may listen on network ports, accept client writes into simulated state and generate responses, delays or faults. Keep it segregated from production unless the production-network owner has explicitly approved the scenario.
Not a safety or control function
ProtoCall does not replace safety validation, functional testing, vendor-approved engineering tools, process alarms, independent verification or competent professional judgement. Stop the test if a target behaves unexpectedly and preserve the evidence for review.