Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Covenant C2?

Covenant is an open-source .NET command and control framework with a browser-based interface, built around in-memory assembly execution on Windows estates.

Illustration for the cybersecurity term Covenant C2
Home / Blog / Cybersecurity Terms / What Is Covenant C2?
17 November 2026

What Is Covenant C2?

What Is Covenant C2?

Covenant is an open-source command and control framework written in .NET, created by Ryan Cobb while at SpecterOps and released in 2019. Where most frameworks of the period were driven from a terminal, Covenant shipped with a browser-based interface running on ASP.NET Core, which made collaborative operations and operator handover considerably easier to manage.

Its implants are called Grunts. They are .NET assemblies, and that single design decision defines everything interesting about the framework, both operationally and from a detection standpoint.

Why .NET Mattered

Around 2018 and 2019, offensive tooling moved decisively towards C#. The reason was practical: the .NET runtime is present on every modern Windows installation, it exposes the Windows API through managed code, and an assembly can be loaded and executed directly from memory with a few lines of reflection, without ever touching disk.

Covenant built on that. A Grunt communicates over HTTP, HTTPS, or SMB named pipes, with the last used for peer-to-peer tasking so that implants on hosts without internet access route through one that has. Tasks are themselves .NET assemblies compiled on the server and executed in memory on the target, which meant that the large existing library of C# offensive tooling, including SharpUp, Seatbelt, Rubeus, and SharpHound, could be run without being written to the file system.

The framework also supports launchers across the expected set of Windows execution paths, and integrates the Donut project to convert .NET assemblies into position-independent shellcode for scenarios where a managed executable is unsuitable.

Where It Sits Now

Covenant’s active development has slowed considerably, and it has been largely displaced in current practice by Mythic, Sliver, and Havoc, which offer stronger evasion features and more active maintenance. It remains worth understanding for three reasons.

First, it is a clean, readable implementation of .NET command and control, which makes it an excellent teaching reference for both operators and detection engineers. Second, the techniques it popularised did not go away; execute-assembly-style in-memory loading is now standard in Cobalt Strike and almost every modern framework. Third, open-source frameworks are attractive to groups that want capability without the attribution or cost of a commercial product, and several intrusion sets have been observed using open-source C2 frameworks in real operations.

Detecting .NET Tradecraft

The good news for defenders is that the Common Language Runtime is extremely talkative if you configure Windows to listen.

Practical Steps for Defenders

Four controls materially reduce the value of this entire technique class. Enable script block logging and AMSI, and forward the results; without them most of the detections above produce nothing. Enforce application allowlisting with Windows Defender Application Control so that arbitrary managed executables cannot launch. Constrain PowerShell with Constrained Language Mode where the business allows. Restrict and monitor outbound traffic so that a Grunt beaconing to an unfamiliar host is visible on the network as well as on the endpoint.

Then test them. Running a known framework in a controlled environment and checking which of your rules fired is the only way to know whether the configuration you deployed actually produces an alert. Mapping the result to MITRE ATT&CK keeps the exercise comparable between frameworks.

At Privia Security, our SOC Maturation Services include testing detection coverage against current command and control tradecraft and writing the rules that close the gaps.

FAQ – Frequently Asked Questions

Is Covenant Still Used in Real Engagements?

Less often than it was. Active development has slowed, and most teams have moved to Mythic, Sliver, or Havoc for better evasion features and ongoing maintenance. Covenant remains useful as a teaching reference and as a detection engineering target, because its .NET tradecraft is the same tradecraft that current frameworks implement in more sophisticated ways.

Why Is In-Memory .NET Loading Significant?

It avoids writing tools to disk, which defeats file-based scanning and removes the artefact a forensic examiner would normally find. An entire library of C# offensive tooling can be executed inside one process that never creates a new file. Detection therefore has to rely on runtime telemetry: assembly load events, AMSI submissions, and the CLR appearing in processes that should not host it.

What Is a Grunt?

Covenant’s implant. It is a .NET assembly that runs on the target and communicates with the team server over HTTP, HTTPS, or an SMB named pipe. Tasks are compiled on the server as .NET assemblies and executed in the Grunt’s memory. Named pipe Grunts allow peer-to-peer tasking, so hosts without internet access are controlled through one that has it.

Which Windows Settings Help Most Against This?

Enable AMSI and PowerShell script block logging and forward the output, since without them the key telemetry does not exist. Add Windows Defender Application Control so arbitrary managed executables cannot run, Constrained Language Mode where feasible, and Sysmon for named pipe and image load events. Then run a framework in a lab and verify which rules actually fire.

Related Terms

You May Be Interested In These

What Is Dependabot?

Cybersecurity Terms

17 November 2026

What Is Dependabot?

Read More
What Is a SOAR Playbook?

Cybersecurity Terms

17 November 2026

What Is a SOAR Playbook?

Read More
What Is the Purdue Model?

Cybersecurity Terms

17 November 2026

What Is the Purdue Model?

Read More