T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:313- Finding
Mutable Remote Repository Is Retrieved and Executed Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
``` 2. **Verify artifact integrity** - Publish a SHA-256 checksum for a release archive. - Require users to verify the checksum before running any script. - Prefer cryptographically signed releases or signed Git tags and document signature verification. 3. **Avoid immediate execution after retrieval** - Separate download, verification, configuration, and execution into distinct steps. - Tell users to inspect `start.bat` and relevant application code before execution. - Display the exact expected release version and revision in the Skill documentation. 4. **Vendor reviewed components where practical** - Include the reviewed launcher and required source in the distributed Skill package. - If remote retrieval remains necessary, restrict it to immutable, integrity-verified artifacts. 5. **Constrain runtime privileges** - Run FocusAI as a standard user rather than an administrator. - Restrict filesystem access to its configuration and designated data directory. - Restrict outbound network access to the explicitly configured cloud vision provider. - Bind the local API exclusively to the loopback interface and add authentication if other local processes should not be able to control monitoring. 6. **Protect sensitive data** - Store the API key using an operating-system credential manager instead of plaintext configuration where supported. - Provide screenshot exclusion, redaction, retention, and deletion controls. - Clearly identify the configured cloud endpoint before monitoring starts and require renewed consent when that e ...[truncated 20 chars]
