Industrial-grade pasarelas de datos que aíslan el tráfico analógico y digital en redes SCADA. Transmisiones cifradas sin interferencias, con latencia por debajo de 5 ms.
Deploy a hardened gateway that isolates analog and digital sensor data, encrypts every M2M frame, and blocks external intrusions before they reach your SCADA panels. Less than 5 ms latency, AES-256 tunnels, and active OT threat detection — all in a single certified appliance.
Common queries about our edge computing gateways, M2M links, and industrial cybersecurity.
How does the EdgeGate 5000 isolate analog and digital data?
The gateway uses dedicated hardware tunnels with AES-256 encryption to separate analog sensor signals from digital control frames. This prevents cross-contamination and blocks external intrusion attempts on the automation network.
What is the typical latency for a LinkSecure M2M transmission?
End-to-end latency stays below 8 ms in point-to-point mode and under 12 ms in mesh topology, even with full encryption enabled. This meets the requirements for real-time SCADA monitoring and control loops.
Can CyberShield SCADA be deployed without interrupting production?
Yes. The firewall supports passive learning mode for the first 48 hours, building a baseline of legitimate traffic. After that, active filtering can be enabled gradually per segment, with zero downtime for critical PLCs and RTUs.
Which industrial protocols are supported by your gateways?
Our devices natively handle Modbus RTU/TCP, OPC-UA, MQTT, Profinet, and EtherNet/IP. Custom protocol parsers can be added via the integrated edge computing module without hardware changes.
Do you offer on-site configuration for B2B deployments?
We provide remote commissioning via secure VPN tunnels and, for large-scale rollouts, on-site engineering support within 48 hours. All configurations are logged and auditable per IEC 62443 guidelines.
Clarifications on edge computing gateways, M2M link encryption, and industrial firewall rules to avoid contractual ambiguity.
Edge computing refers to data processing performed on the EdgeGate 5000 hardware located at the local network boundary, not in a remote cloud. All sensor data is analyzed within the plant LAN before any WAN transmission. Latency guarantees apply only when the gateway is configured with the default firmware and no third-party VPN is inserted between the sensor and the gateway port.
LinkSecure M2M modules operate on license-free ISM bands. While the hardware uses frequency hopping and forward error correction, Sooqok does not guarantee zero packet loss in environments with active jamming devices or co-located high-power transmitters exceeding FCC/ETSI limits. The "cifrado de extremo a extremo" clause applies only when both endpoints are Sooqok-certified units with firmware version 2.1 or later.
The CyberShield SCADA firewall blocks unauthorized traffic based on deep packet inspection rules. The warranty does not cover breaches caused by physical tampering with the appliance, unpatched operating system vulnerabilities on connected HMIs, or misconfiguration of allow-lists by the client's network administrator. Compliance with IEC 62443 is verified only for the firewall itself, not for the entire OT network.
Latency is measured as round-trip time between the sensor input on the EdgeGate 5000 and the SCADA panel output over a wired backhaul. Wireless hops via LinkSecure M2M add up to 12 ms per hop under nominal conditions. Any SLA credit claim must be supported by logs from the integrated performance monitor; third-party ping tools are not accepted as evidence.
AES-256 encryption is applied to data in transit between the gateway and the SCADA head-end. Data at rest on the gateway's local SSD is encrypted with AES-128 by default; upgrading to AES-256 for stored data requires a separate license. Analog sensor signals digitized inside the gateway are encrypted only after the ADC stage — raw analog lines are not encrypted.
The EdgeGate 5000 supports Modbus RTU/TCP, OPC-UA, and MQTT out of the box. Protocols not listed in the official compatibility matrix (e.g., Profibus, CANopen) require a custom firmware build with additional lead time and engineering fees. No retroactive compatibility is assumed — the client must verify protocol support before deployment.
Cookie settings
We use cookies to keep the site reliable, remember basic choices, and understand which pages are useful. You can accept, reject, or review the settings before continuing.