このレポートには指定された言語の翻訳がありません。代わりに正規の英語レポートを表示しています。
バージョン付きセキュリティ評価
レポートID: SA-1FFA7643
7/9/2026, 4:12:18 AM
when-configuring-sandbox-security-use-sandbox-configurator セキュリティ評価 v9
スキルセキュリティ認証レポート
監査モデル: claude 最新の公開済みレポート
- スキル名
- when-configuring-sandbox-security-use-sandbox-configurator
- バージョン
- v9
- メンテナー
- DNYoussef
- カバレッジ
- 4 スキャンされたファイル · 971 解析済み行数
- ポリシーバージョン
- 利用不可
確認済みの検出結果における最高重大度
重大
6 件の確認済みセキュリティ検出結果に対応が必要です。
インストールのコンテキスト
現在のスキルページを確認
このページはレポートの証拠のみを要約しています。正規のインストール勧告は Skill ページで提供されます。
現在のスキルページを開くこのレポートは、マニフェストまたは ZIP をブロックも承認もしません。
The skill has a legitimate defensive purpose, but it includes executable shell workflows that modify host security settings, firewall rules, and privileged system files. Several static findings are false positives because they are deny-list entries or documentation, but sensitive-file tests and privileged configuration commands remain real risks.
レポートの位置
最新の公開済みレポート
「最新」はレポートの順序を指し、アーティファクトの最新性を指すものではありません。
監査アテステーション
証明不可
必要な不変のバインディングは不完全です。
人による検証
未検証
このレポートには人による検証は記録されていません。
カバレッジ
4 スキャンされたファイル · 971 解析済み行数
レビュー対象の項目を 64 件表示
制限事項
このレポートはランタイムまたはサンドボックスでの実行を主張するものではなく、副作用がないことを証明するものでもありません。
証拠チェーン
ソースバインディングからインストール契約まで証拠をたどってください。利用可能な証拠は検証を支援しますが、安全性を保証するものではありません。
ソース
コミットとパスにバインド済み
アーティファクト
コンテンツとツリーのハッシュがバインド済み
監査
完了
確認された機能
「確認」とは、このレポートで裏付けとなる証拠が記録されていることを意味します。「記録なし」は、機能が存在しないことを証明するものではありません。
スクリプトを含む
Skillに含まれるコードを実行する場合があります。
この監査では記録されていません
ネットワークアクセス
外部サービスに接続する場合があります。
5 件の証拠箇所で確認
ファイルシステムへのアクセス
ローカルファイルの読み取りまたは書き込みを行う可能性があります。
25 件の証拠箇所で確認
環境変数
プロセス環境から値を読み取る可能性があります。
この監査では記録されていません
外部コマンド
Skillの外部にあるコマンドまたはプログラムを呼び出す場合があります。
46 件の証拠箇所で確認
機能レビュー項目 (58)
重大
Hidden file in home directory
if ! cat ~/.ssh/id_rsa 2>/dev/null; then
The test attempts to read ~/.ssh/id_rsa and relies on failure for success. Executing this outside a correctly isolated sandbox could expose a private key.
重大
Hidden file access
if ! cat ~/.ssh/id_rsa 2>/dev/null; then
The test attempts to read ~/.ssh/id_rsa and relies on failure for success. Executing this outside a correctly isolated sandbox could expose a private key.
重大
Standard device file access
if ! cat /etc/shadow 2>/dev/null; then
The command attempts to read /etc/shadow as a negative security test. If run with excessive privileges, it could disclose password hash material.
重大
Standard device file access
if ! cat ~/.ssh/id_rsa 2>/dev/null; then
The command attempts to read ~/.ssh/id_rsa as a negative security test. If isolation fails, it could expose an SSH private key.
中
Ruby/shell backtick execution
```yaml
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Ruby/shell backtick execution
```bash
The finding points to a shell code block that creates files, runs commands, or invokes hooks. This is executable operational guidance, so it is a real command-execution risk if followed without review.
中
Shell command substitution
--value "{\"status\": \"complete\", \"threats_identified\": 5, \"controls_defined\": 9, \"timestamp\
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
--value "{\"status\": \"complete\", \"file_boundaries\": true, \"timestamp\": \"$(date -Iseconds)\"}
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
--value "{\"status\": \"complete\", \"network_isolated\": true, \"timestamp\": \"$(date -Iseconds)\"
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
echo "{\"timestamp\": \"$(date -Iseconds)\", \"result\": \"$TEST_RESULT\"}" >> sandbox-security/test
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
--value "{\"status\": \"complete\", \"tests_passed\": true, \"timestamp\": \"$(date -Iseconds)\"}"
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
echo "[$(date -Iseconds)] Resource usage:"
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
--value "{\"status\": \"complete\", \"deployed\": true, \"monitoring\": true, \"timestamp\": \"$(dat
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Shell command substitution
--value "{\"status\": \"success\", \"security_level\": \"high\", \"compliance\": true, \"timestamp\"
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Template literal with command substitution
```bash
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Template literal with command substitution
```bash
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Template literal with command substitution
```bash
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Template literal with command substitution
```bash
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Template literal with command substitution
```bash
The snippet uses shell command substitution inside an executable command. It is mostly timestamp logging, but it still depends on shell evaluation and should remain flagged.
中
Unix shell invocation
#!/bin/bash
The skill creates executable bash scripts for sandbox setup, testing, or monitoring. These scripts can alter host configuration and should be reviewed before execution.
中
Unix shell invocation
#!/bin/bash
The skill creates executable bash scripts for sandbox setup, testing, or monitoring. These scripts can alter host configuration and should be reviewed before execution.
中
Unix shell invocation
#!/bin/bash
The skill creates executable bash scripts for sandbox setup, testing, or monitoring. These scripts can alter host configuration and should be reviewed before execution.
中
Unix shell invocation
#!/bin/bash
The skill creates executable bash scripts for sandbox setup, testing, or monitoring. These scripts can alter host configuration and should be reviewed before execution.
中
Unix shell invocation
#!/bin/bash
The skill creates executable bash scripts for sandbox setup, testing, or monitoring. These scripts can alter host configuration and should be reviewed before execution.
中
Hardcoded URL
if ! curl -s --max-time 5 https://example-malicious.com >/dev/null 2>&1; then
The skill instructs a curl request to example-malicious.com to test blocking. Even as a negative test, it can create outbound traffic if controls fail.
低
Hardcoded URL
if curl -s --max-time 5 https://api.anthropic.com >/dev/null 2>&1; then
The skill instructs curl access to api.anthropic.com as a trusted-domain network test. This is legitimate for validation but still performs outbound network access.
低
Standard device file access
if touch /workspace/test.txt 2>/dev/null; then
The command writes to /workspace to validate allowed access. It is expected behavior, but it still changes the filesystem and should remain visible.
リスク指摘
確認済みのセキュリティ上の懸念事項は、引き続きレビューが必要な項目と分けて表示されます。
確認済みのセキュリティ上の懸念 (6)
RISK-001 重大
SSH directory access
if ! cat ~/.ssh/id_rsa 2>/dev/null; then
The command explicitly tries to read ~/.ssh/id_rsa and treats success as a security issue. This is a real sensitive-file access attempt in the provided test script.
RISK-002 重大
SSH private key file
if ! cat ~/.ssh/id_rsa 2>/dev/null; then
The command explicitly references the default SSH private key path. Running it outside a properly constrained sandbox could disclose private key contents.
RISK-003 重大
System password file access
if ! cat /etc/shadow 2>/dev/null; then
The command explicitly tries to read /etc/shadow and treats success as a security issue. This is a real sensitive system-file access attempt in the test script.
RISK-004 高
Privileged Host Security Configuration Changes
The skill instructs users to write files under /etc/security and /etc/apparmor.d, load an AppArmor profile, modify /etc/hosts, and set iptables default policies. These commands can disrupt the host or network if run outside a disposable environment.
The cited sections directly modify privileged system configuration and firewall state. The intent is defensive, but the operational blast radius is high.
RISK-005 高
Unpinned External Package Execution
The workflow repeatedly invokes npx claude-flow@alpha hooks and memory commands. Using an alpha package through npx can execute remote package code during the workflow and increases supply-chain risk.
The content explicitly uses npx with an alpha package name in executable instructions. This is clear external code execution, even though no malicious intent is proven.
RISK-006 中
Continuous Monitoring Commands May Capture Sensitive Activity
The monitoring script tails audit logs and starts tcpdump on all interfaces. This can collect sensitive file-access and network metadata if enabled without retention limits and access controls.
The script directly starts audit-log and packet monitoring commands. The risk depends on deployment controls, but the collection behavior is explicit.
是正措置
この監査で推奨される修正が記録されています。これらを適用する責任はメンテナーにあります。
- FIX-001重大Security tests attempt to read /etc/shadow and ~/.ssh/id_rsa.Replace live sensitive-file reads with mocked fixture paths or container-only test files that prove deny rules without touching real host secrets.
- FIX-002高Privileged host modification commands are presented as runnable examples.Add explicit warnings to run only in disposable test environments, require manual approval, and provide rollback steps before changing /etc, AppArmor, iptables, or hosts files.
- FIX-003高The workflow executes npx claude-flow@alpha without pinning an immutable version.Pin a reviewed version or remove npx hook calls from the marketplace skill instructions.
- FIX-004中Monitoring commands can collect sensitive audit and packet metadata.Document retention, access control, and scoping requirements before enabling audit-log tailing or tcpdump.
専門家による証拠
不変の対象ID、スキャナーメタデータ、除外された一致項目、およびソースレベルの証拠。
アーティファクト主体
- Marketplace コミット
- 1ffa7643651792ccb4bd3b15d924d2c97edff755
- コンテンツハッシュ
- a160d8209bd2e5fa0af7db92805649b445f711555f3218b9c5c0e5b4fd9c3ae9
- ツリーハッシュ
- 3f7ac7e9ccef245606fee5e9e4e6a40acb7b7f7d7525fb6a09d3ee139053eeef
- Skill パス
- skills/dnyoussef/when-configuring-sandbox-security-use-sandbox-configurator
- 監査ペイロードハッシュ
- ec5ca99ebfe45cb74affb325a38c6648
分析メタデータ
監査モデル: claude
分析状態: 完了
対象範囲は、記録されたファイル、行、メソッド、および証拠に限定されます。ランタイムまたはサンドボックスでの実行は主張していません。
検証とエクスポート
マニフェストとロックファイルは、インストール成果物を暗号学的ハッシュに結び付けます。この完全性に関する主張は、セキュリティ評価とは別のものです。
監査アテステーション: not_attestable