Hello ROS 2 Security Working Group,
I’ve developed a lightweight, air-gapped security observability module for
ROS 2 deployments in environments where cloud connectivity is undesirable
(edge robotics, humanitarian infrastructure, privacy-sensitive applications).
Technical Scope:
- Read-only DDS introspection (no publishers/services)
- Localhost-only dashboard (127.0.0.1)
- Docker containerized with non-root execution
- Zero external dependencies
- Real-time system monitoring (CPU, memory, network)
Target Platforms:
- Boston Dynamics Spot (payload compute)
- Humanoid platforms (Digit, Figure 02)
- Edge/lab environments
Current Status:
- Working prototype with backend monitoring
- Docker Compose integration with ROS 2 Humble
- Internal bridge network (air-gapped by default)
Repository: GitHub - coldnsteel/HackerWatchFortress-Sovereign: Sovereign Security Dashboard - No Government Ties
I’m seeking feedback on:
1. SROS 2 alignment best practices
2. Passive DDS monitoring patterns
3. Air-gapped security logging standards
Any guidance would be appreciated.
Best regards,
Monk Bartholomew
Thanks,