Anyone who installs software they did not write. Every case below is the same
problem. A file you trust gains a capability it never had.
You Look After a Fleet of Machines
One line per machine. No agent, no console, one page for all of it.
You enrol a machine with one line, from Intune, Jamf, a GPO or your image.
Nothing runs as a service and there is nothing to log into. Each machine signs
its own receipt into a folder you already back up, so no cloud password ever
sits on a watched machine. One command turns that folder into a single page.
The page opens off a USB stick and shows every machine that went quiet. It
exports for an audit.
It installs faster than you can read. This reads for you.
Your agent pulls packages on its own, all day. One bad package can read your
keys or run a command on your machine. Vigilance checks each install. It shows
the file that gained a new capability. The agent gets a clear yes or no before it
trusts the code.
It tells you the one line in the update that matters.
A routine update can carry a change nobody reviewed. Vigilance compares the new
version against the old one. It stays quiet on the normal changes and shows the
one file that can now reach the network, run a command, or read a secret.
A gate in your pipeline. One binary, nothing to install.
Every build pulls fresh packages. Vigilance runs in the pipeline as one binary,
with no agent and no service. If a dependency gains a risky capability, the build
stops and tells you which file and which capability.
One command, and it only speaks when a file gained a capability.
No security team, and no time to read a diff on every update. Vigilance stays
silent on normal updates. It speaks up only when a file gains a capability it never
had, so the one alarm you get is worth reading.
A regulated or disconnected shop cannot phone home. The network code is removed
from the Pro binary when it is built, so it cannot reach out even if something
told it to. It still catches the change, because it reads the files on the
machine and not a cloud database.