Secator docs
  • GETTING STARTED
    • Introduction
    • Installation
    • CLI Usage
    • Library usage
    • Configuration
    • Examples
      • 5 minutes secator session
  • RUNNER OPTIONS
    • Global options
    • Meta options
    • Input formats
    • Output options
  • IN-DEPTH
    • Philosophy & design
    • Distributed runs with Celery
    • Concepts
      • Output types
      • Proxies
      • Exporters
      • Runners
      • Drivers
      • Profiles
    • Deployment
  • For developers
    • Development setup
    • Writing tasks
      • Integrating an external command
        • Parsing JSON lines
        • Parsing raw standard output
        • Parsing output files
        • Example: integrating ls
        • Example: cat hunters
      • Integrate custom Python code [WIP]
      • Advanced options
    • Writing workflows
    • Writing scans [WIP]
Powered by GitBook
On this page
  • Direct input
  • File input
  • Stdin input

Was this helpful?

  1. RUNNER OPTIONS

Input formats

... or how to pass targets to secator.

secator is built to be flexible in terms of input formats.


Direct input

Inputs can be passed directly as an argument to the command / workflow / scan you wish to run:

secator x httpx example.com # single input
secator x httpx example.com,example2.com,example3.com # multiple comma-separated inputs

File input

Input can also be passed from a file containing one item per line:

secator x httpx urls.txt

Stdin input

Input can also be passed directly from stdin:

cat urls.txt | secator x httpx

You can build basic workflow using UNIX pipes:

secator x subfinder vulnweb.com | secator x nmap | secator x httpx

For more complex workflows, we highly recommend using the YAML-based workflow definitions or the code-based workflow definitions (see Writing workflows).


PreviousMeta optionsNextOutput options

Last updated 7 months ago

Was this helpful?