Build out the default command string

[epi052]

Nuclei is a template based scanner. As such, not every template is appropriate to use on every single scan.

Ones that need to be excluded:

• brute-force
• payloads
• workflows

Workflows appear to simply wrap existing templates with add'l logic. We're probably double-tapping if we include them.

Command is probably something like

nuclei -t /tmp/stuff/nuclei-templates/cves -l TARGETS -silent -json

Need to explore -json vs. -json-requests

[epi052]

nuclei -t ~/.local/recon-pipeline/tools/nuclei-templates/panels -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/subdomain-takeover -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/tokens -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/security-misconfiguration -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/default-credentials -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/dns -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/vulnerabilities -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/files -t /home/epi/.local/recon-pipeline/tools/nuclei-templates/generic-detections -t ~/.local/recon-pipeline/tools/nuclei-templates/cves/ -t ~/.local/recon-pipeline/tools/nuclei-templates/technologies/ -l TARGET_LIST -silent -o whatver-output-file -json