Local MQTT mTLS security platform
IoT Security Lab
Manage the Hydroficient broker, launch secure and rogue clients, and observe replay, certificate, authentication, and MQTT validation events in real time.
WebSocket offlineBroker stoppedSubscriber retrying
Total messages
0
Accepted messages
0
Rejected messages
0
Active devices
0
Security alerts
0
Latest MQTT Message
No MQTT message received yet. Start a device client to publish telemetry.
--
Connected Devices
| Device | Seq | Flow | Pressure | Seen |
|---|---|---|---|---|
| No validated device telemetry yet. | ||||
Attack Alerts
No attack alerts yet.
MQTT Traffic
Traffic appears as soon as the backend subscriber receives MQTT messages.
Authentication Events
Certificate and broker authentication events will appear here.
Live Security Logs
Backend and process logs will stream here.
System Architecture
A live view of how device telemetry, broker transport, backend security analysis, and dashboard monitoring work together.
TLS/mTLS brokerWildcard subscriberWebSocket stream
IoT Devices
Secure and rogue clients
Python MQTT clients publish sensor telemetry or simulate rogue behavior.
Mosquitto Broker
MQTT message bus
Local Mosquitto broker receives MQTT traffic and enforces TLS or mTLS broker configuration.
FastAPI Security Layer
Subscriber via offline
Backend subscriber consumes wildcard topics, validates HMAC, freshness, sequence counters, and cert events.
Monitoring Analytics
0 events analyzed
Traffic classifier updates devices, metrics, alerts, authentication events, and attack detections.
Frontend Dashboard
Polling fallback active
Next.js dashboard renders live traffic, logs, devices, and presentation-ready system context.
TLS/mTLS Security
Broker certificates, client certificates, and encrypted MQTT transport protect the channel.
WebSocket Updates
FastAPI broadcasts traffic, logs, auth events, and alerts to the Next.js dashboard.
Attack Simulation
Replay, tampering, missing-cert, wrong-CA, and expired-cert scenarios feed the same event pipeline.
Traffic Analysis
Messages are parsed, classified, validated, counted, and mapped to connected device state.