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

DecoysarmedHoneytokensplantedPatchesappliedSecurity meshessynced

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.

01
Decoys and the mazeFake SSH, web, database, RDP and SMB services on their own ports; anyone who gets in lands in an endless, believable file tree.
02
HoneytokensPlanted credentials, API keys, canary links and documents: their use is a critical alert with no false positives.
03
Attacker case filesEvery address profiled — techniques, targets, credentials tried — exportable as STIX 2.1 or a report for an abuse desk.
04
Patching on approvalVulnerable packages checked against OSV with the update that fixes each; one click runs it behind your password.
05
Firewall blockingBlocked addresses refused by VIMS and, on request, dropped by nftables, pf or Windows Firewall.
06
Security meshesShare what you prove with your organisation privately, and with the public mesh only when three independent nodes agree.

How it works

  1. Turn on the decoys and plant a honeytoken
  2. Review detections and attackers as they arrive
  3. 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.