> For the complete documentation index, see [llms.txt](https://blog.securescape.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.securescape.cc/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure.md).

# Command & Control Infrastructure

### Command & Control

*Description Covered in* [Command & Control Anatomy](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/command-and-control-anatomy.md)

### Command & Control Infrastructure

The Command & Control (C2/C\&C) infrastructure encompasses multiple technologies:

* Team Server (the C2 Itself)
* Redirector (Determines traffic flow)
* Network Protocols (How the agent communicates)
* Cover Server (A decoy server to send defenders or scanners to)

The purpose of the infrastructure is to protect the internal network and the operation from being uncovered. By utilising traffic redirectors, decoy servers, and redirection rules, we can ensure that the security and knowledge about the on-going operations remain hidden from unauthorised view.

#### High Level Graph

<figure><img src="/files/YgZMV0FDjXC5Dqv4a0ga" alt=""><figcaption><p>High Level Overview of a classic  C2 Infrastructure Design</p></figcaption></figure>

### Table of Contents

<details>

<summary><a data-mention href="/pages/kVdJGKvwkaDUTDzTpp7g">/pages/kVdJGKvwkaDUTDzTpp7g</a></summary>

[Command & Control Frameworks](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/command-and-control-anatomy/command-and-control-frameworks.md)

[Mythic Framework](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/command-and-control-anatomy/mythic-framework.md)

</details>

<details>

<summary><a data-mention href="/pages/pBgbbcRO5zGzuCl3lLew">/pages/pBgbbcRO5zGzuCl3lLew</a></summary>

[Nginx](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/traffic-redirection/nginx.md)

[Amazon Web Services](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/traffic-redirection/amazon-web-services.md)

[Microsoft Azure](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/traffic-redirection/microsoft-azure.md)

[Google Cloud Platform](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/traffic-redirection/google-cloud-platform.md)

[Cloudflare Workers](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/traffic-redirection/cloudflare-workers.md)

</details>

<details>

<summary><a data-mention href="/pages/AqPpDrIv2O30PfbuE8Nv">/pages/AqPpDrIv2O30PfbuE8Nv</a></summary>

[Ensuring Resiliency](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/covert-infrastructure/ensuring-resiliency.md)

[Traffic Masking](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/covert-infrastructure/traffic-masking.md)

[Network Rules](/offensive-security/red-team/offensive-development/infrastructure-development-wip/command-and-control-infrastructure/covert-infrastructure/network-rules.md)

</details>