Skip to content
DigitalAftermath edited this page Jun 9, 2018 · 5 revisions

Below is a custom Sparta config file that can be utilized to streamline/simplify the enumeration process.

How do I install the config file?

Simple, go navigate to /usr/share/Sparta and edit the contents of sparta.conf to the supplied configuration file. In the event you manage to mess this simple task up, delete the sparta.conf file, rerun Sparta, and a new sparta.conf file will be generated.

How do I use Sparta?

I'm not reinventing the wheel, so read the fucking manual.

Why should I use Sparta?

A few reasons:

  • Sparta provides an enumeration framework that can save valuable time via a point, click, shoot strategy instead of CLI bashing.
  • Sparta uses a phased approach to port scanning, allowing for the rapid identificaiton of common ports while scanning all 65,535 ports.
  • Sparta can be customized for your particular needs and does not require in-depth scripting/programming knowledge.

What is the suggested workflow?

The workflow is straight forward:

launch sparta -> save file -> add hosts -> enumerate specific services

In the workflow provided, you will see that nmap is used to conduct parallel scanning. This is done for a few reasons:

  1. Sparta uses a phased approach to scanning.
  2. Nmap can be utilized to conduct a more granular approach to scanning (if needed).
  3. Nmap is used to double check the results of Sparta to ensure everything is true.

Sparta allows for the importing of nmap scans, so if you want to skip Sparta scanning hosts, just conduct the scanning via Zenmap/Nmap and import the results.

Make sure you save Sparta results to a folder structure that makes sense for you. I really like utilizing once instance of Sparta to scan one host, so at any given time I will have multiple tabs of Sparta open just to keep things "isolated". All of this is up to how you like to manage your workspace, there is no "correct" way.

Sparta .conf Script

Download the sparta.conf script here.

Clone this wiki locally