JonathanCisneros.com

Independent project / case study

CIS Mini RMM.

A Windows agent, a narrow gateway, and a control plane built to make endpoint administration more deliberate. Follow the path from first enrollment through a verified update.

Windows serviceASP.NET CorePostgreSQLSigned releases
SYSTEM PATHEndpoint → Edge → Control planeIndependent technical build · Active development

Independent technical project

One agent. A complete control path.

A private endpoint-management project that connects Windows services, APIs, databases, network boundaries, and signed updates into one traceable workflow.

Product engineeringEndpoint operationsSecurity architecture
01/ 04

Enroll

One-time, high-entropy tokens are hashed at rest and expire when redeemed. Devices receive their own ID and secret.

Report

A Windows service phones home with heartbeats and version information through a restricted nginx gateway.

Recover

A separate Auditor watches the Agent and can restart it with retry and backoff behavior.

Update

Maintenance tooling checks signed release artifacts before replacing the installed Agent.

Interface preview

Inside CIS Mini RMM.

Working API Alpha Version 10.9.26 - Private use only

Platform architecture

Follow the signal.

Select a layer to see what it does and how data moves through the system.

01 / ENDPOINT

Start with a known device.

A one-time enrollment token gives each device its own ID and secret. The Agent reports heartbeats and version information, while the separate Auditor watches for recovery and maintenance work.

  • Device identity
  • Outbound reporting
  • Watchdog recovery

Security by design

Trust is a workflow.

Key decisions in the build include single-use enrollment, device identities, a dedicated agent gateway, outbound endpoint communication, and RSA-signed software releases. Self-update has been tested end to end with the new version reported back by the API.

One-time tokenSigned releaseRoute isolationOutbound agent
DESIGNED / IN PROGRESS

Device lifecycle and remote control

The planned lifecycle covers pending, approved, active, suspended, rejected, decommissioned, and archived states. Tokenless bootstrap keeps unknown devices quarantined until approval. The Admin Center preview shows a remote session in development; per-user remote-control authorization and the complete browser workflow remain design work.

Remote terminal execution is currently in the SYSTEM context; interactive-user execution is being examined.

Release engineering

Update the endpoint with evidence.

The release flow is designed to verify both package integrity and publisher authenticity before installation.

01 / BUILDAgent packageCompile and archive
02 / RECORDManifest + hashVersion and metadata
03 / SIGNRSA signaturePublisher verification
04 / STAGERelease catalogueDownload location and notes
05 / VERIFYMaintenance appReject invalid releases

A self-update test replaced an installed Agent and the API subsequently reported the new version.

Keep exploring

See the lab where I keep testing ideas and tools.

Explore the lab ↗