Monarch C2
  • Introduction to Monarch
  • Installation
    • Resources
    • Uninstall Monarch
  • Interface
  • Features
    • External integration
    • Multiplayer
    • Management (server)
    • HTTP customization
  • Architecture
  • Usage
    • Builders
    • Agents
    • Listeners
    • Stage
    • Sessions
    • Players (server)
    • Chat
  • Integration
    • Project configuration
    • Builder
      • Architecture
      • API
      • Build routine
      • Build service
    • C2 server
      • Registering implants
      • Talking to implants
    • Implant development
      • Registration
      • Tasks
      • The TCP handler
Powered by GitBook
On this page
  1. Integration

C2 server

More in-depth information about the C2 server

The C2 server facilitates communication between operators and live implants. As long as it's live, the deployed agents can be controlled.

The server has a specific, well-defined schema that implants or C2 profiles may use to directly communicate with it.

Implants have separate registration and operation endpoints.

Monarch currently only supports beacon-like or session-like implant communication. This means that to have non-registration data accepted by the server, a request must have been sent by an operator in the first place.

Last updated 1 year ago