Use a test profile, synthetic data, and no production credentials. This guide is strategy and evaluation guidance, not managed implementation or support.
Map the trust boundary
List the model provider, agent runtime, UI, gateway, tools, extensions, storage, logs, backups, and every network path.
Start with least privilege
Disable tools and channels you do not need. Use a separate user/profile and synthetic data for the first pilot.
Protect credentials
Keep API keys and session tokens in the supported secret store. Never paste them into prompts, repositories, screenshots, issue reports, or public logs.
Restrict network exposure
Keep local APIs and admin panels private until authentication, authorization, transport, and update procedures are verified.
Review extensions and model terms
Treat skills, plugins, MCP servers, and downloaded models as supply-chain inputs. Check source, permissions, license, and update path.
Test recovery and deletion
Prove you can revoke credentials, remove chat history/files, restore a clean backup, and shut down the agent without exposed services.
Completion checklist
- Trust boundary mapped
- Least privilege enabled
- Secrets externalized
- Network exposure restricted
- Extensions reviewed
- Recovery/deletion tested