mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-09-02 14:40:51 +03:00
Mahipal
2fb6a9faff
Each rewritten description now states both what the skill does (concrete capability, named tools/artifacts) and an explicit when-to-use trigger, improving agent discovery/activation. Grounded in each skill's own body; changes confined to the `description` field only (bodies and all other frontmatter untouched). Produced by a gated audit->rewrite->recheck loop (548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded). Schema: 817/817 pass. Framework-ID gate: 0 defects.
71 lines
2.4 KiB
Markdown
71 lines
2.4 KiB
Markdown
---
|
|
name: performing-red-team-with-covenant
|
|
description: Conducts red team operations using the Covenant C2 framework for authorized
|
|
adversary simulation, covering listener setup, grunt deployment, task execution,
|
|
and lateral movement tracking. Use when standing up or operating a Covenant command-and-control
|
|
server for an authorized red team engagement.
|
|
domain: cybersecurity
|
|
subdomain: red-team
|
|
tags:
|
|
- red-team
|
|
- c2
|
|
- covenant
|
|
- adversary-simulation
|
|
- penetration-testing
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- ID.RA-01
|
|
- GV.OV-02
|
|
- DE.AE-07
|
|
mitre_attack:
|
|
- T1595
|
|
- T1190
|
|
- T1059
|
|
- T1078
|
|
- T1021
|
|
---
|
|
# Performing Red Team Operations with Covenant C2
|
|
|
|
## Overview
|
|
|
|
Covenant is a collaborative .NET C2 framework for red teamers that provides a Swagger-documented REST API for managing listeners, launchers, grunts (agents), and tasks. This skill covers automating Covenant operations through its API for authorized red team engagements: creating HTTP/HTTPS listeners, generating binary and PowerShell launchers, deploying grunts, executing tasks on compromised hosts, and tracking lateral movement.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When conducting security assessments that involve performing red team with covenant
|
|
- When following incident response procedures for related security events
|
|
- When performing scheduled security testing or auditing activities
|
|
- When validating security controls through hands-on testing
|
|
|
|
## Prerequisites
|
|
|
|
- Covenant C2 server deployed (Docker or .NET 6)
|
|
- Python 3.9+ with `requests` library
|
|
- Covenant API token (obtained via /api/users/login)
|
|
- Written authorization for red team engagement
|
|
- Isolated lab or authorized target environment
|
|
|
|
## Steps
|
|
|
|
### Step 1: Authenticate to Covenant API
|
|
Obtain a JWT token by posting credentials to /api/users/login endpoint.
|
|
|
|
### Step 2: Create Listener
|
|
Configure an HTTP or HTTPS listener with callback URLs and bind address.
|
|
|
|
### Step 3: Generate Launcher
|
|
Create a binary, PowerShell, or MSBuild launcher tied to the listener for grunt deployment.
|
|
|
|
### Step 4: Deploy and Manage Grunts
|
|
Monitor grunt callbacks, execute tasks, and collect output from compromised hosts.
|
|
|
|
### Step 5: Document Operations
|
|
Generate an operations report documenting all actions, timestamps, and findings.
|
|
|
|
## Expected Output
|
|
|
|
JSON report with listener configuration, active grunts, executed tasks, and task output for engagement documentation.
|