T09 · Insecure Skill Coding Practices
- Location
decision-memory.md:11- Finding
Confidential investment records are stored in plaintext workspace files
- Content
View full analysis
Vulnerability Details
File Location:
decision-memory.md, lines 11–14 and 124–126
Vulnerability Type: Plaintext storage of confidential decision and portfolio data
Risk Level: MediumVulnerable Snippet
The following is an English rendering of the complete relevant Markdown segment:
markdown ## Storage Scheme - Format: **JSONL** (one Object per line: Decision / Monitoring / Outcome / Learning), directly queryable by code and readable by the LLM for Recall - Path: `decision_memory.jsonl` (workspace root) + `outcome_memory.jsonl` (Outcome/Learning, associated by decision_id) - Phase 1: zero external dependencies; linear scanning is sufficient ## Privacy Boundary - Decision / Outcome / Learning Memory contains confidential fund data, is stored locally, is not externally shared, and is not used for third-party training - Exporting or sharing requires manual approval from the IC secretaryRelated persistence instructions also appear in
SKILL.md, lines 187–190, and the sensitive record structures are defined indecision-object.md, lines 158–207.Technical Analysis
The Skill directs the agent to persist investment decisions, evidence, valuation ranges, internal IC resolutions, portfolio financial results, and institutional learning records in JSONL files located at the workspace root.
Although the documentation states that these records are confidential and must not be externally shared, it does not define or enforce:
- Owner-only filesystem permissions.
- Encryption at rest.
- Per-fund or per-user workspace isolation.
- Retention and secure-deletion policies.
- Exclusion from generic workspace synchronization, backup, indexing, or presentation tools.
- Integrity protection against unauthorized modification.
- Access controls for other agents or tools operating in the same workspace.
The
Outcome ObjectandLearning Objectmay contain actual revenue, customers, gross margin, valuation, failed assumptions, misleading evide ...[truncated 1738 chars]- Remediation
View remediation
Remediation Suggestions
- Move decision memory into a dedicated, access-controlled storage directory rather than the workspace root.
- Create files with owner-only permissions, such as mode
0600, and directories with mode0700. - Encrypt sensitive records at rest using a managed key or operating-system credential store; do not store the encryption key beside the data.
- Separate records by fund, tenant, and authorized user to prevent cross-context access.
- Define an explicit retention schedule and secure-deletion procedure for expired projects and outcomes.
- Exclude the memory directory from generic file-delivery, synchronization, search-indexing, source-control, and backup mechanisms unless explicitly approved.
- Add integrity protection, such as authenticated encryption or signed records, to detect unauthorized changes.
- Minimize stored data by replacing unnecessary names and free-form confidential text with identifiers or redacted summaries.
- Enforce authorization checks before Recall, export, or sharing rather than relying only on a written approval rule.
- Record access and export events in a separate tamper-resistant audit log.
