SecureHost Control Suite

The case in short.

The problem

Windows gives you little control over which process can reach which address, or which app can open the camera, microphone, USB or Bluetooth, and no single place to see what happened.

Who it is for

Anyone who wants to control and audit device and network access on their own Windows machine.

My part

Sole author.

How it was done

1. A core library holds the policy engine (allow or deny decisions), the audit engine (JSON logs) and storage encrypted with Windows DPAPI.
2. The service exposes a REST API on localhost, monitors connections and devices, and ships with three default rules: block camera, block microphone, audit unusual outbound connections.
3. A WPF client gives a dashboard, rule editor, connection viewer and audit export, and a CLI covers scripting.
4. I wrote it to be recoverable: a documented one-command system reset undoes every rule.
5. I wrote two kernel drivers (a Windows Filtering Platform network filter and a device filter) but have not installed them, because enforcement needs the Windows Driver Kit and code signing. The user-mode parts work without them.

What came out

The service, GUI, CLI, REST API, network monitoring, device enumeration, audit logging and encrypted policy storage run today. Actual blocking needs the optional drivers.