Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool workflows for automating pentests #42

Open
aronmolnar opened this issue Aug 3, 2023 · 3 comments
Open

Tool workflows for automating pentests #42

aronmolnar opened this issue Aug 3, 2023 · 3 comments

Comments

@aronmolnar
Copy link
Contributor

Pentests often have parts that can easily be automated. Some tools could be automatically triggered, parsed, and added as issue to a report.

#41 would allow us to protocol commands and their outputs.

We could use this feature to implement workflows. A workflow is a definition of commands that should be executed.

---
upload: yes
parallel_execution: yes
commands:
  - sudo nmap -p 80 {target}
  - nuclei -t xyz- -u {target}
  - sslyze -u {target}

The workflow could be executed (reptor cmd --workflow wf.yaml), the tools run and upload their tool outputs to the current report.

(Regarding parallelization, we could also introduce stages that should run in parallel.)

---
upload: yes
parallel_execution: yes
commands:
  portscan:
    - sudo nmap -p 80 {target}
  attacks:
    - nuclei -t xyz- -u {target}
    - sslyze -u {target}

In the future, we could also take tool outputs from previous tools (like sslyze open ssl ports from nmap scan).

@aronmolnar
Copy link
Contributor Author

/cc @MWedl @Patralos

@richardschwabe
Copy link
Contributor

IMHO: I suggest you wait with this until there is more feedback from users and the reptor CLI has been made public.
Of course, the workflows and command integration sound great and would be beneficial. However, they are also introducing a new landscape and slightly changing the core functionality. As in: Reptor is purely for managing sysreptor notes and uploading any notes from projects. At the moment piping might be enough for users. Every line of code needs to be maintained and it might get too much.

@aronmolnar
Copy link
Contributor Author

aronmolnar commented Aug 3, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants