Ros2 security

Skill Leehyunbin0131/claude-ros2-skills/skills/ros2-security

Claude Code skills for ROS 2 Jazzy — establish the unknowns first, verify against the installed system, prove the result ran.

Install

npx -y skills add Leehyunbin0131/claude-ros2-skills --skill ros2-security

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

SROS2: ros2 security CLI, PKI keystore, enclaves, access-control XML, DDS Security.

SKILL.md

1.6 KB, 415 tokens by cl100k_base, as published. Nobody here has run it

ROS 2 Security (SROS2) Instructions (Ubuntu 24.04 LTS & ROS 2 Jazzy)

1. Architecture

SROS2 applies OMG DDS-Security (Fast DDS, Cyclone DDS) for node authentication (X.509 PKI), access control (Governance/Permissions XML), and topic/service encryption (AES-GCM-GMAC 128/256).

2. Documentation Entry Points

Concepts: https://docs.ros.org/en/jazzy/Concepts/Intermediate/About-Security.html
Tutorials (setup + access control): https://docs.ros.org/en/jazzy/Tutorials/Advanced/Security/Introducing-ros2-security.html

Verify ros2 security subcommands and the env vars ROS_SECURITY_ENABLE / ROS_SECURITY_STRATEGY / ROS_SECURITY_KEYSTORE there before use.

3. Key Concepts & Workflows

A. SROS2 CLI Commands

# 1. Create root keystore
ros2 security create_keystore ~/my_keystore

# 2. Create security enclave for node
ros2 security create_enclave ~/my_keystore /talker_listener/talker

# 3. Launch node inside enclave
export ROS_SECURITY_ENABLE=true
export ROS_SECURITY_STRATEGY=Enforce
export ROS_SECURITY_KEYSTORE=~/my_keystore

ros2 run demo_nodes_cpp talker --ros-args --enclave /talker_listener/talker

B. High-Level Access Control Policy (`policy.xml`)

<policy version="0.2.0">
  <enclaves>
    <enclave path="/talker_listener/talker">
      <profiles>
        <profile node="talker" ns="/">
          <topics publish="ALLOW">
            <topic>chatter</topic>
          </topics>
        </profile>
      </profiles>
    </enclave>
  </enclaves>
</policy>

Gives 0 of the 12 instructions most security skills give in 415 tokens

Counted across 648 of the 828 authors here whose files we hold, read 2026-08-06

parameterize all database queriesin 67 of 648, across 49 files
hash passwords using bcrypt scrypt or argon2in 48 of 648, across 35 files
apply rate limiting to authentication endpointsin 48 of 648, across 24 files
Configure security headersin 35 of 648, across 18 files
validate all inputsin 32 of 648, across 24 files
validate all external input at the system boundaryin 29 of 648, across 18 files
run containers as a non-root userin 28 of 648, across 15 files
use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
run dependency audits before every releasein 21 of 648, across 10 files
encode output to prevent cross-site scriptingin 21 of 648, across 10 files
copy dependencies before source codein 20 of 648, across 9 files
store secrets in environment variablesin 20 of 648, across 17 files

Said here and by no other author read

create root keystore
create security enclave for node
set ROS_SECURITY_ENABLE to true
set ROS_SECURITY_KEYSTORE to keystore path
launch node inside enclave
define access control policy xml

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.