Guides

Synchronizing Data

Synchronize data between redteamer instances. The rt sync command lets operators share runs, outputs, and metadata across machines, networks, or physical media.

Overview

redteamer’s Data Sync feature enables distributed collaboration and continuity. When operators share a sync path, redteamer exchanges only the differences between local and remote data.

This allows the outputs of one operator’s runs to become the inputs of another, across devices, networks, or even offline transfers.

rt sync <path>

How It Works

rt sync performs a bidirectional differential sync between the local redteamer data store and the specified path.

Only changed data is transferred
Sync is content-addressed and de-duplicated
Works over any shared or portable storage
Preserves full audit integrity and traceability
Operates without central servers or network requirements

redteamer maintains a compact index to detect and merge changes efficiently, even for large artifacts and binary data.

Usage

rt sync <path>

Examples

# Sync over a mounted SMB share
rt sync /mnt/redteam-share

# Sync to a USB drive
rt sync /media/usb/redteamer-sync

# Sync over a local SFTP mount
rt sync /mnt/sftp/redteam

# Sync with a cloud-backed fuse mount
rt sync /mnt/s3/redteamer-data

The path can be any mounted or accessible storage location, such as:

Local directories (/media/usb, /mnt/nfs)
Network mounts (SMB, NFS, WebDAV)
Cloud FUSE mounts (S3FS, Rclone)
Portable drives or removable storage

Data Model

Syncing exchanges the contents of redteamer’s local data store:

Component	Description
`runs/`	Execution logs, metadata, and traces
`outputs/`	Collected files and generated artifacts
`modules/`	Cached module manifests
`state/`	Internal sync metadata and hash index

The sync path stores content-addressed objects rather than raw copies. Identical files or run artifacts are stored once and referenced by hash, allowing safe, space-efficient sharing among multiple operators.

Behavior

Action	Result
New local runs	Uploaded to the sync path
New remote runs	Downloaded locally
Modified metadata	Merged bidirectionally
Conflicts	Resolved automatically using timestamp precedence
Deletions	Tracked via soft delete markers
Duplicate content	Automatically deduplicated in storage

Security and Isolation

Sync does not require active network connectivity unless the path itself depends on it
All data is stored in plain directories for transparency and offline inspection
De-duplication ensures that repeated syncs or multiple contributors do not inflate storage
Operators can safely move physical media between isolated networks and merge data later

This design supports high-assurance workflows, including air-gapped or multi-environment operations.

Example Workflow

Operator A performs reconnaissance on an isolated laptop.
```
rt run recon/scan
rt sync /media/usb/redsync
```
Operator B connects the same USB on another system.
```
rt sync /media/usb/redsync
```
The new run and outputs from Operator A now appear in Operator B’s audit history. B can reference them as inputs or review them directly.

The sync path can be reused indefinitely. Only changed or new data is transferred, and shared artifacts are stored once.

Notes

rt sync is idempotent and can be run safely multiple times
Interrupted syncs can be resumed by rerunning the command
To view detailed progress, use --verbose
Sync is fast even on large datasets due to hashing and differential detection

Example

rt sync /mnt/redteamer-share --verbose

Output:

Scanning local data...
Comparing against /mnt/redteamer-share...
↑ 3 runs uploaded
↓ 2 runs downloaded
✔ Sync complete