mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
24f816b6a3
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
63 lines
2.2 KiB
Markdown
63 lines
2.2 KiB
Markdown
---
|
|
name: performing-red-team-with-covenant
|
|
description: Conduct red team operations using the Covenant C2 framework for authorized adversary simulation, including listener
|
|
setup, grunt deployment, task execution, and lateral movement tracking.
|
|
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
|
|
---
|
|
# 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.
|