docker-compose-scanners's Introduction

docker-compose-scanners

To start all siwecos scanners on your local machine, install Docker and docker-compose, clone this repo and run docker-compose up inside the repo's directory.

This repo is still under heavy development and at the moment not ready for use in production environments.

Usage

Start the SIWECOS base components via

docker-compose up

This command will start the SIWECOS Core-API, all scanners and a callback server. All components get a port mapping to the host system so one can either start a complete scan by sending a scan start request to the Core-API or a single scan by sending this request to one of the scanners.

The following components are included at the moment:

Name	Port-Mapping
Callback Server	3000
SIWECOS Core-API	8000
INI-S Scanner	8090
HSHS-DOMXSS Scanner	8091
INFOLEAK Scanner	8093
PORT Scanner	8094
TLS Scanner	8095
VERSION Scanner	8096

Quickstart

You can do a quick-scan for a bunch of domains with the running as follows:

Fill the domainList.txt with one domain per line
Run the scan-domains.sh script

The scan-domain.sh script allows different start parameters. You can either run ALL tests by using the [SIWECOS Core-API] or run a specific scanner by its name: DOMXSS, HEADER, INFOLEAK, PORT, TLS, IMAP_TLS, IMAPS_TLS, POP3_TLS, POP3S_TLS, SMTP_TLS, SMTPS_TLS or VERSION

The Results will be saved in the data/scans.json file. You can either open this file directly or check http://localhost:3000/scans.

docker-compose-scanners's People

Watchers

docker-compose-scanners's Issues

staging & production gleich aufbauen

Reminder:

Im develop.yml soll ebenfalls mariadb und redis genutzt werden, sodass die gleichen Technologien in beiden Umgebungen verwendet werden.

Redis Konfiguration

Um eine Redis-Instanz als Cache und Queue-List nutzen zu können, müssen die jeweiligen Scanner ein eindeutiges Prefix nutzen:

domainList.txt - Scan funktioniert nicht

beim Aufruf von ./scan-domains.sh ALL gibt es lediglich die Meldung

{"url":["validation.required"],"callbackurls":["validation.required"],"dangerLevel":["validation.required"]}

Fehler beim Starten

ALL/CORE funktioniert nicht. Vielleicht weil
INFOLEAK nicht startet

$ ./scan-domains.sh INFOLEAK
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /api/v2/start was not found on this server.</p>
<hr>
<address>Apache/2.4.25 (Debian) Server at localhost Port 8093</address>
</body></html>

TLS nicht startet

$ ./scan-domains.sh TLS
<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title><style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> Not Found</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat/8.5.40</h3></body></html>

Recommend Projects