Dotset Architecture
Dotset is a unified CLI that bundles three independent security tools. This page explains how they work together.Tool Overview
The Three Tools
Hardpoint
Purpose: Pre-flight security scanning Hardpoint scans your developer environment for AI-era threats that traditional security tools miss:| Scanner | What It Finds |
|---|---|
ai | Malicious AI config files, prompt injection |
shell | Backdoors in shell configs |
git | Hidden code in git hooks |
network | Exposed localhost services |
secrets | Hardcoded credentials |
dotset run)
Tollgate
Purpose: Runtime access control Tollgate acts as a proxy between AI agents and MCP servers, controlling what actions the AI can take:Deadfall
Purpose: Compromise detection Deadfall uses cognitive honeypots to detect when AI agents are compromised or behaving unexpectedly:- Trap files contain hidden instructions
- AI reads the file during normal operation
- AI follows instructions to call a verification tool
- Alert triggered when the trap is sprung
Independence Model
Each tool operates independently:- Hardpoint findings don’t automatically create Tollgate policies
- Deadfall alerts don’t automatically block Tollgate calls
- Each tool has its own logs and configuration
Data Flow
With dotset run
Individual Commands
Binary Management
Dotset manages Go binaries in~/.dotset/bin/:
npx.
Installation Flow
Configuration Hierarchy
Defense in Depth
The three tools provide layered security:| Layer | Tool | Threat Model |
|---|---|---|
| Prevent | Hardpoint | Find threats before they execute |
| Control | Tollgate | Limit what AI can do at runtime |
| Detect | Deadfall | Know when something’s wrong |
See Also
- Getting Started — Initial setup
- Orchestration — Workflow details
- Configuration — Full configuration reference