Add SECURITY.md with DDS deployment guidance#34
Open
zack-dev-cm wants to merge 1 commit into
Open
Conversation
Expanded the security policy to include detailed reporting guidelines, trust boundaries, safety guidance, and dependency provenance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a SECURITY.md for unitree_sdk2. The repository currently has no security policy, and GitHub issues are disabled for this repo, so this PR is using the available "Suggest a policy" contribution path.
The policy documents responsible reporting expectations, the DDS/RTPS trust boundary, safe command-control deployment guidance, example-use cautions, and dependency/binary provenance expectations.
Context
unitree_sdk2 exposes DDS publish/subscribe and RPC-style APIs that can be used for robot motion, arm, audio, video, configuration, and low-level motor command paths. Deployments should make the trusted-network and DDS Security assumptions explicit so downstream users do not treat examples or CRC checks as production security controls.
Notes
This PR intentionally avoids exploit instructions or packet-level details. It is meant to establish a public security policy and safer deployment baseline.