robotics-security

Secure ROS2 communications with DDS encryption and access control.

8|1|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/KJdotIO/innex1-rover --skill robotics-security-kjdotio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: robotics-security
Source: https://github.com/KJdotIO/innex1-rover/tree/main/skills/robotics-security
Command: npx skills add https://github.com/KJdotIO/innex1-rover --skill robotics-security-kjdotio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security hardening and best practices for robotic systems, covering SROS2 DDS security, network segmentation, secrets management, secure boot, and the physical-cyber safety intersection. Use this skill when securing ROS2 communications, configuring DDS encryption and access control, hardening robot onboard computers, managing certificates and credentials, setting up network segmentation for robot fleets, or addressing IEC 62443 for robotics.

Core Features & Use Cases

  • SROS2: DDS security with encryption and access control for ROS2 topics and services
  • Keystore and certificate management: generate per-enclave certificates, governance policies, and permissions
  • Network hardening: VLAN segmentation, firewall rules, unicast discovery, and secure DDS configurations
  • Host and container security: SSH hardening, minimal images, container signing and verification
  • Secrets management and auditing: environment-based secrets, rotation patterns, and security logging

Quick Start

Enable SROS2 Enforce across all ROS2 nodes, generate per-enclave certificates, implement VLAN segmentation, and rotate credentials on a monthly schedule.

Frequently Asked Questions about robotics-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure ROS2 DDS communications with encryption and access control?

To secure ROS2 DDS communications, you must enable SROS2 enforce mode across all nodes and generate per-enclave certificates. This implements encryption and access control for all ROS2 topics and services to protect robotic fleet communications.

What is per-enclave certificate governance in robotic fleet security?

Per-enclave certificate governance is the process of generating isolated security policies and permissions for distinct robotic execution environments. It ensures that individual ROS2 nodes operate under strict access controls defined by centralized governance files.

How do I set up network segmentation and firewall hardening for robot fleets?

Network segmentation for robot fleets is achieved through VLAN configurations, strict firewall rules, and unicast discovery settings. This hardens robotic onboard computers by isolating secure DDS traffic from untrusted network segments.

What is the best way to manage keystore credentials and monthly certificate rotation for ROS2?

The best way to manage keystore credentials is implementing environment-based secrets and automated rotation patterns. You must schedule monthly certificate rotation to maintain SROS2 access control and prevent compromised robotic fleet credentials.

Does this approach address IEC 62443 requirements for robotics and physical-cyber safety?

Yes, this approach addresses IEC 62443 requirements for robotics by implementing DDS security, network segmentation, and secure boot. It intersects physical-cyber safety by hardening onboard computers and configuring audit and monitoring for robotic fleets.

Can I use container signing and SSH hardening alongside minimal images for robot onboard computers?

Yes, you can use container signing and verification alongside SSH hardening to protect robot onboard computers. Deploying minimal images reduces the attack surface while ensuring that only verified containers execute within the robotic fleet.