Node defense and agent safety
Defend the computer your agents run on
A security team in the app: decoys and honeytokens that catch intruders, a host watch, attacker case files, vulnerability patching on approval, firewall blocking by your rules, and security meshes that share what you prove — plus app scans and approvals for agents.
Inside VIMS Desktop · macOS · Windows · Linux · ChromeOS · Free
What it does
Security is organised like a real security team. Blue detects (every event tagged with its MITRE ATT&CK technique), green fixes (vulnerable packages and their patches), red maps your attack surface, white sets the rules of engagement and keeps the audit, orange turns what was seen into lessons. A security assistant reads every view and acts only when you approve. By default VIMS watches, deceives and asks; it blocks only what decoys prove hostile, and it never touches an attacker’s systems.
How it works
- Turn on the decoys and plant a honeytoken
- Review detections and attackers as they arrive
- Patch, block, or share a case file — each waits for you
FAQ
Does VIMS attack back?
No. The default rules of engagement are: defend this computer only — deceive, record and block; never touch an attacker’s systems; report them.
What leaves my computer when I share?
Only indicators — an address, its confidence and the techniques seen — and never an address or host that isn’t publicly routable. Private meshes encrypt everything to their own key.
How does the public mesh avoid poisoning?
An address is kept only once at least three independent publishers report it, and publishers are weighed by how often others corroborate them. See it live at security.vims.com.
Are agents still governed?
Yes. App and skill scans, approval levels and the audit log apply to every agent and app.
How does VIMS Security connect to the rest of VIMS?
It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.
Related
Defend the computer your agents run on
Security is organised like a real security team. Blue detects (every event tagged with its MITRE ATT&CK technique), green fixes (vulnerable packages and their patches), red maps your attack surface, white sets the rules of engagement and keeps the audit, orange turns what was seen into lessons. A security assistant reads every view and acts only when you approve. By default VIMS watches, deceives and asks; it blocks only what decoys prove hostile, and it never touches an attacker’s systems.
security