T09 · Insecure Skill Coding Practices
- Location
references/neural-chain-design.md:7- Finding
Classification-Agnostic Cloud Mirroring May Expose Confidential Communications
- Content
View full analysis
Vulnerability Details
File Location:
references/neural-chain-design.md:7-15
Vulnerability Type: Missing classification enforcement before external replication
Risk Level: HighVulnerable Code
text Every communication path must have 3 independent channels. But 3 channels shouldn't mean 3x the complexity. The channels should be layered so that failure at one layer is invisible at the next. Layer 1: Direct (sessions_send) → Fastest, real-time Layer 2: File-based (shared directory) → Async, auditable Layer 3: Cloud (Tencent Docs) → Cross-platform, resilient An agent writes to Layer 1, and the brain ensures Layer 2 and Layer 3 mirror it automatically. Agents read from any available layer.The same document expands the exposure through comprehensive logging and retention at
references/neural-chain-design.md:118-119:text 5. **Log everything** — Every inter-agent message is logged to `company/logs/ops/` 6. **Audit trail** — Any message from 30 days ago should be retrievableThese requirements conflict with the safeguards in
SKILL.md:139-148:text 🔴 绝密 — 仅CEO可见,仅本地处理,禁云模型 🟠 机密 — 部门内部可见,本地+私有云 🟡 内部 — 全公司可见,可用付费云模型 🟢 公开 — 可外发,可用免费模型 密级决定三件事: 1. 存放在哪个目录(本地加密/共享目录/公开目录) 2. 可以用什么模型处理(免费/付费/仅本地) 3. 能不能写入外部渠道(品牌部发文/销售部对外——只能是🟢级信号)Technical Analysis
The neural-chain design requires every communication path to use three channels and states that messages sent through the direct channel are automatically mirrored to both a shared directory and Tencent Docs. It does not require a classification check, destination authorization, redaction, encryption, or an exception for local-only information before replication.
Consequently, the unconditional mirroring rule can override the central information-classification policy. In particular, top-secret information designated for local processing only could be uploaded to a third-party cloud document service. Confide ...[truncated 2213 chars]
- Remediation
View remediation
Remediation Suggestions
- Make classification enforcement mandatory before any message is transmitted, mirrored, logged, or retained.
- Define classification-specific routing:
- Top secret: encrypted local channel and storage only; prohibit shared and cloud replication.
- Confidential: approved department-scoped local or private-cloud destinations only.
- Internal: approved organization-controlled services with authenticated access.
- Public: external replication may be allowed under an explicit destination allowlist.
- Make classification restrictions override redundancy requirements. Redundancy for restricted records must use multiple independently protected local channels rather than an external cloud channel.
- Default to denying replication when a classification label is absent, invalid, or ambiguous.
- Require explicit destination allowlists and verify recipient authorization before each copy is created.
- Encrypt sensitive messages in transit and at rest, with classification-appropriate key management and rotation.
- Log metadata by default—message ID, sender, recipient, classification, timestamp, result, and integrity hash—rather than complete message bodies.
- If message-body logging is necessary, apply redaction, strict role-based access control, encryption, immutable access auditing, and classification-specific retention periods.
- Add deletion propagation so expiration or reclassification removes every authorized replica, including cloud documents and logs where policy permits.
- Add automated tests proving that top-secret and confidential fixtures cannot reach prohibited cloud, shared-folder, model, or logging destinations.
- Reconcile
references/neural-chain-design.mdwith the classification policy inSKILL.mdso no unconditional replication instruction remains.
