Cmd uses 4 major components: the agent, collector, database, and the Cmd app.
The Cmd web app is the main point of contact with Cmd. It provides an interface for monitoring activity and configuring security rules on Cmd-enabled servers. From the app, users can monitor activity on their servers, configure rules to enforce their organization's policies, create actionable reports, and more.
The agent, collector, and database run in the background to enable Cmd's monitoring, logging, and control capabilities. To enable Cmd on a server, system administrators simply install the Cmd Control or Cmd Audit agent (~5mb in size) on the server. Once an agent is installed, it enforces configured security policies and logs server activity. It sends the activity logs to the collector. The collector runs on either a dedicated on-premise server or in a cloud environment. It compiles all the data logs from your Cmd-enabled servers. The collector sends data to the database, where it is processed for display in the Cmd app.
To learn more or request a demo, visit cmd.com