/faraday

Plugin List

Francisco Amato edited this page Oct 5, 2016 · 45 revisions

The main purpose of Faraday is to re-use the available tools in the community to take advantage of them in a multiuser way.

There are three kinds of plugins available for Faraday; console, report and API

Console

Plugins that intercept commands, fired directly when a command is detected in the console. These are transparent to you and no additional action on your part is needed.

Report

Plugins that import file reports. You have to copy the report to $HOME/.faraday/report/[workspacename] (replacing [workspacename] with the actual name of your Workspace) and Faraday will automatically detect, process and add it to the HostTree.

If Faraday is not capable to detect the plugin needed to process the report, you can manually choose which plugin will be used by adding _faraday_pluginName to the file name before the extension.

For example, if the Burp report named burp_1456983368.xml is not being recognized, try renaming it to Burp_1456983368_faraday_Burp.xml. Now copy it to the Workspace directory and Faraday should now run the plugin and import all vulnerabilities.

Keep in mind that this functionality is case sensitive. The names of the available plugins are:

  • Acunetix
  • Arachni
  • Burp
  • Core Impact
  • Maltego
  • Metasploit
  • Nessus
  • Netsparker
  • Nexpose
  • NexposeFull
  • Nikto
  • Nmap
  • Openvas
  • Qualysguard
  • Retina
  • W3af
  • X1
  • Zap

API

Plugin connectors or online (BeEF, Metasploit, Burp), these connect to external APIs or databases, or talk directly to Faraday's RPC API.

List

If you think your favourite tool is missing code your own plugin or ask us to do it!