/siege-master

Intelligence L3 Production low usage

/siege-master

Overview

/siege-master is a production command in the Intelligence category of the Prismatic Platform that executes comprehensive intelligence siege operations with full-spectrum coverage. Unlike targeted intelligence commands such as /investigate or /email-osint that focus on specific data types, /siege-master orchestrates a coordinated multi-vector intelligence collection campaign that simultaneously queries all available data sources, cross-correlates findings in real time, and produces a unified intelligence product that would require dozens of individual queries to assemble manually.

The "siege" metaphor reflects the command's operational philosophy: rather than probing a target through a single vector and hoping for results, it surrounds the target with overlapping collection methodologies that leave no information gap unexplored. DNS records, WHOIS data, certificate transparency logs, web archives, social media footprints, code repositories, breach databases, dark web mentions, and infrastructure fingerprints are all queried in parallel, with findings from each source used to generate new queries for other sources in a recursive enrichment loop.

This command operates under the L3 authority level and is executed by the siege-master-operator agent. It is part of the platform's 216-command slash command registry, built on the AIAD (Autonomous Intelligence Agent Design) standard. The L3 authority requirement ensures that siege operations, which can be resource-intensive and produce large volumes of data, are initiated only by operators with strategic command authority.

The command produces structured intelligence reports in multiple formats, suitable for security assessments, competitive intelligence briefings, due diligence investigations, and attack surface mapping. All operations are conducted through publicly available and authorized data sources, with strict adherence to ethical intelligence collection standards and applicable privacy regulations.

Architecture

The siege master system coordinates multiple intelligence collection agents through a central orchestration layer that manages query scheduling, result correlation, and report generation.

Target Specification
       |
       v
  [Target Decomposition]     -- Extract queryable identifiers
       |
       v
  [Collection Orchestrator]   -- Parallel multi-vector queries
       |                |                |              |
       v                v                v              v
  [DNS/Infra]     [Web/Social]    [Code/Tech]    [Dark/Breach]
       |                |                |              |
       v                v                v              v
  [Cross-Correlation Engine]  -- Link findings across vectors
       |
       v
  [Enrichment Loop]           -- Generate new queries from findings
       |
       v
  [Report Generator]          -- Structured intelligence product
ComponentPurposeImplementation
Target DecompositionBreaks target identifiers into queryable components (domains, IPs, emails, names)PrismaticOsint.TargetDecomposer
Collection OrchestratorManages parallel query execution across all intelligence vectorsPrismaticOsint.SiegeOrchestrator
Cross-Correlation EngineLinks findings from different sources to build unified entity profilesPrismaticOsint.Correlator
Enrichment LoopUses initial findings to generate secondary queries for deeper coveragePrismaticOsint.EnrichmentEngine
Report GeneratorProduces structured reports in multiple formats with confidence scoringPrismaticOsint.ReportGenerator

Usage

Basic Siege Operations

# Full siege on a domain target
/siege-master target:example.com

# Siege on an organization
/siege-master target:"Acme Corporation" type:organization

# Siege on a person
/siege-master target:"John Doe" type:person context:cybersecurity

# Quick siege with reduced depth (faster, less comprehensive)
/siege-master target:example.com --quick

Scoped Operations

# Infrastructure-focused siege
/siege-master target:example.com --vectors infrastructure,dns,certificates

# Social and web presence siege
/siege-master target:"@username" --vectors social,web,code

# Security-focused siege (attack surface mapping)
/siege-master target:example.com --profile security

# Competitive intelligence siege
/siege-master target:"Competitor Corp" --profile competitive

Advanced Operations

# Siege with maximum enrichment depth
/siege-master target:example.com --depth maximum --enrich 3

# Siege with specific output format
/siege-master target:example.com --output json --file siege-report.json

# Siege with progress streaming
/siege-master target:example.com --stream

# Resume an interrupted siege
/siege-master --resume siege-2026-02-15-001

Options & Parameters

ParameterTypeDefaultDescription
targetstringrequiredTarget identifier: domain, email, organization name, person name, IP address
typestringauto-detectTarget type: domain, organization, person, email, ip, username
--vectorsstringallComma-separated collection vectors to use
--profilestringcomprehensivePreset profile: comprehensive, security, competitive, due-diligence, quick
--depthstringstandardCollection depth: shallow, standard, deep, maximum
--enrichinteger2Number of enrichment loop iterations (0-5)
--outputstringmarkdownOutput format: markdown, json, html, pdf
--filestringauto-generatedOutput file path
--streamflagfalseStream results as they are collected
--quickflagfalseQuick mode: reduced depth, no enrichment loops
--resumestring-Resume a previously interrupted siege by ID
--timeoutduration10mMaximum execution time per vector
contextstring-Additional context to guide collection focus

Execution Flow

  1. Target Decomposition -- Parse the target specification and extract all queryable identifiers. A domain target yields: domain name, potential subdomains, associated email patterns, organization name, registrant information. A person target yields: name variations, potential email addresses, social media username patterns.

  2. Vector Selection -- Based on the target type and selected profile, determine which collection vectors to activate. The comprehensive profile activates all available vectors; focused profiles activate subsets.

  3. Parallel Collection -- Launch concurrent queries across all selected vectors. Each vector operates independently with its own timeout and retry logic. Partial results are available as soon as any vector completes.

  4. Cross-Correlation (Round 1) -- As initial results arrive, the correlation engine links findings across vectors. An IP address found in DNS records is linked to infrastructure data; an email found in WHOIS is linked to breach database results.

  5. Enrichment Loop -- Findings from Round 1 generate new queries. A previously unknown subdomain triggers additional DNS and certificate queries. A discovered email address triggers breach and social media lookups. This loop repeats up to --enrich iterations.

  6. Confidence Scoring -- Each finding is assigned a confidence score based on source reliability, corroboration across vectors, and data freshness. Findings confirmed by 3+ independent sources receive high confidence; single-source findings receive low confidence.

  7. Report Generation -- Compile all findings into a structured intelligence report organized by entity, with cross-references, confidence scores, and collection metadata.

Integration Points

ComponentIntegration TypeDescription
/investigateCollection VectorLeverages the investigation engine for deep-dive queries
/email-osintCollection VectorEmail-specific intelligence gathering
/google-hackingCollection VectorAdvanced search engine intelligence
/web-crawlerCollection VectorAutomated web content extraction
Prismatic PerimeterAttack SurfaceFeeds findings into EASM asset inventory
TelemetryObservabilityCollection progress and performance metrics
Quality GatesValidationReport quality validation before delivery

Best Practices

Target Specification Precision: Provide the most specific target identifier available. target:example.com produces more focused results than target:"Example Company". When investigating organizations, start with the primary domain and let enrichment discover related assets.

Profile Selection: Use focused profiles (security, competitive) rather than comprehensive when you know what you need. Comprehensive sieges are resource-intensive and produce large reports that may contain more information than is actionable for a specific use case.

Enrichment Depth: The default enrichment depth of 2 provides good coverage without excessive runtime. Increase to 3-5 only when investigating complex organizations with many subsidiaries or when mapping large infrastructure footprints.

Result Verification: Always verify critical findings through independent channels before acting on them. The confidence scoring helps prioritize which findings need manual verification, but automated intelligence collection can produce false positives, especially in cross-correlation.

Ethical Considerations: Only conduct siege operations against targets where you have authorization or legitimate purpose. The command operates through publicly available data sources, but the aggregation of public information can still raise privacy concerns.

Error Handling

Error ConditionResponseRecovery
Target not resolvableAttempt alternative interpretations, report if none succeedRefine target specification with type and context
Vector timeoutMark vector as incomplete, continue with available resultsUse --resume to retry timed-out vectors
Rate limiting on data sourceBack off and retry, mark findings as potentially incompleteWait and retry, or exclude the rate-limited source
Enrichment loop explosionCap at maximum iteration count, warn about breadthReduce --enrich depth or scope with --vectors
Report generation failureSave raw findings for manual report assemblyExport raw data with --output json
Network connectivity lossSave progress, enable resumeUse --resume with the siege ID

Advanced Usage

Continuous Monitoring Siege

# Set up recurring siege for ongoing monitoring
/siege-master target:example.com --profile security --schedule weekly

# Compare current siege with previous results
/siege-master target:example.com --diff siege-2026-02-08-001

# Generate delta report (changes since last siege)
/siege-master target:example.com --delta --since 2026-02-01

Multi-Target Campaigns

# Siege multiple targets in a coordinated campaign
/siege-master --campaign targets.txt --profile security

# targets.txt format:
# example.com domain
# 192.168.1.0/24 network
# "Acme Corp" organization

Integration with Perimeter

# Feed siege results directly into Perimeter asset inventory
/siege-master target:example.com --profile security --feed-perimeter

# Generate Perimeter-compatible asset manifest
/siege-master target:example.com --output perimeter-manifest

Doctrine Compliance

All commands operate under the NO MERCY, NO DOUBTS doctrine:

  • NO MERCY: Intelligence siege operations execute against all selected vectors without skipping difficult or slow sources. Every vector must complete or explicitly time out. Partial results are clearly marked as incomplete so that consumers know where coverage gaps exist.
  • NO DOUBTS: All findings include confidence scores, source attribution, and collection timestamps. The NABLA Infinity axioms of Signal Plurality and Provenance Mandatory are enforced -- no finding is reported without source attribution, and high-confidence assessments require corroboration from multiple independent sources.
  • /investigate - Launch comprehensive OSINT investigation across 121+ sources
  • /email-osint - Email-based OSINT gathering with breach correlation and social profiling
  • /google-hacking - Google dorking and advanced search intelligence extraction
  • /web-crawler - Automated web crawling and structured data extraction
  • /ghost-recon - Stealth reconnaissance and passive intelligence collection
  • /delta-force - Precision tactical intelligence operations

Connect & Contribute

Created by Tomáš Korcak (korczis) | Open Source under GHL