MAH7MANAGE · ALERT · HARDEN

Where an API stops

Ordinary jobs that stop because there is nowhere to put a program.

Agents can drive anything with an API. The gap is everything else: a BIOS screen, a GUI installer, a UAC prompt, an appliance with a web UI and no credentials worth scripting, a vendor box that is locked down, a laptop that will not run an agent. So we go in the other way.

In through the ports a person would use.

The target sees a monitor and a keyboard and cannot tell the difference, so every screen a person can operate becomes operable.
USB HID reports written straight to the gadget device, so chords, hold, ctrl-drag and shift-click all work rather than one key at a time.
The stock firmware on an off-the-shelf KVM is left untouched. Video, EDID and updates stay the vendor's problem.
Nothing is installed on the machine being driven, so there is nothing to package, deploy or maintain on the far end.

The loop

Target machine BIOS, installer, appliance, locked box NOTHING INSTALLED HDMI out eyes and ears USB HID in the hands Agent Machine Interface open board, or a daemon on a KVM you own frames intent Your agent one authenticated JSON API, bearer key

Next

What we doWhat an engagement covers, step by step.What we measureHow quick the loop actually is, measured.Talk to usTell us what you need an agent to operate.