sec-dashboard - Manual Rapido
Guia de referencia rápida para usar las herramientas de hardware y audit. Para detalle completo ver Guía de uso.
Tarjeta de referencia — 35 herramientas
| Categoria | Tools | Input |
|---|---|---|
| Network Recon (9) | Port Scanner, DNS, Subdomain, HTTP Probe, Whois, Ping, Traceroute, SSL, CAA | Dominio/IP |
| Web Security (10) | Headers, Dir Fuzzer, SQLi, XSS, CORS, Tech, CSP, Open Redirect, HTTP Methods, Robots | URL |
| Vulnerability (3) | CVE Search, Hash Lookup, Password Audit | Custom input |
| System (6) | Net Connections, Process Monitor, System Info, PS Audit, WiFi Marauder, M5Stick | None / URL |
| OSINT (5) | ASN, Reverse DNS, CT Logs, Shodan, GeoIP | Dominio/IP |
| Email Security (2) | DNSSEC, Email Security (SPF/DKIM/DMARC) | Dominio |
3 herramientas nuevas — Setup en 1 minuto
1. PS Security Audit (Windows)
# Clonar (una sola vez)
git clone https://github.com/HOSTNAME/Auditing_with_PowerShell.git "$HOME\Auditing_with_PowerShell"
# Usar en dashboard: System -> PS Security Audit -> click (sin input)2. WiFi Marauder Scan (M5StickC)
# Clonar y arrancar viewer
git clone https://github.com/HOSTNAME/wifi-marauder-viewer.git
cd wifi-marauder-viewer
pip install -r requirements.txt
python app.py
# Usar en dashboard: System -> WiFi Marauder Scan -> Run (URL default)3. M5Stick Networks (M5Stick Plus 2)
# Clonar
git clone https://github.com/HOSTNAME/Visualizacion_extendida_M5StickPlus2.git
cd Visualizacion_extendida_M5StickPlus2
pip install -r requirements.txt
# Terminal 1: capturar serial
python src/serial_logger.py -b 115200 -o wifi_scan_evil.log
# Terminal 2: dashboard
python src/app.py
# Usar en dashboard: System -> M5Stick Networks -> Run (URL default)Splunk — Ver reportes
Configurar Splunk en el dashboard
- Dashboard -> Splunk en la barra lateral
- URL:
https://127.0.0.1:8089| User: sammi | Index:sec_dashboard - Save -> Test Connection -> Enable
Configurar props.conf (JSON parsing automatico)
Para que Splunk extraiga campos del JSON automáticamente (sin spath en cada busqueda), crear C:\Program Files\Splunk\etc\apps\search\local\props.conf:
[powershell:audit]
KV_MODE = json
SHOULD_LINEMERGE = false
TRUNCATE = 0
MAX_EVENTS = 10000
[wifi:marauder]
KV_MODE = json
SHOULD_LINEMERGE = false
TRUNCATE = 0
[m5stick:networks]
KV_MODE = json
SHOULD_LINEMERGE = false
TRUNCATE = 0Reiniciar Splunk: & "C:\Program Files\Splunk\bin\splunk.exe" restart
Sin este props.conf, los eventos se ven como JSON crudo sin campos extraidos.
SPL para ver los 3 reportes
-- PS Audit: todos los modulos
index=sec_dashboard sourcetype=powershell:audit
-- PS Audit: solo usuarios
index=sec_dashboard sourcetype=powershell:audit module=02_Usuarios
-- WiFi Marauder: redes detectadas
index=sec_dashboard sourcetype=wifi:marauder
-- M5Stick: redes + clientes
index=sec_dashboard sourcetype=m5stick:networks
-- Las 3 herramientas a la vez
index=sec_dashboard (sourcetype=powershell:audit OR sourcetype=wifi:marauder OR sourcetype=m5stick:networks)
Sourcetypes
| Sourcetype | Procedencia | Que contiene |
|---|---|---|
powershell:audit | PS Security Audit | 1 evento por modulo (10 modulos) |
wifi:marauder | WiFi Marauder Scan | Redes WiFi (BSSID, ESSID, RSSI, canal) |
m5stick:networks | M5Stick Networks | Redes + clientes (SSID, BSSID, n_clients) |
_json | Todas las tools | Metadata del scan (tool, status, elapsed) |
Arrancar todo (cheat sheet)
# sec-dashboard
cd ~/sec-dashboard
python -m uvicorn backend.main:app --host 127.0.0.1 --port 8444
# PS Audit -- no necesita arrancar nada, el dashboard lo invoca
# Solo necesita el repo clonado en $HOME\Auditing_with_PowerShell
# WiFi Marauder viewer (si vas a usar WiFi Marauder Scan)
cd ~/wifi-marauder-viewer
python app.py
# M5Stick Plus 2 viewer (si vas a usar M5Stick Networks)
cd ~/Visualizacion_extendida_M5StickPlus2
python src/serial_logger.py -b 115200 -o wifi_scan_evil.log # terminal 1
python src/app.py # terminal 2Abrir: http://localhost:8444
Troubleshooting rapido
| Problema | Solucion |
|---|---|
| Sidebar muestra “32 tools” | Ctrl+F5 (cache del navegador). El badge se actualiza dinamico desde la API |
| Reportes en JSON crudo en Splunk | Falta props.conf con KV_MODE = json (ver arriba) |
| PS Audit: “Script contained malicious content” | Excluir carpeta en Windows Security + usar run-audit.ps1 (bypass AMSI) |
| PS Audit: “Invoke-SecurityAudit.ps1 not found” | git clone https://github.com/HOSTNAME/Auditing_with_PowerShell.git "$HOME\Auditing_with_PowerShell" |
| PS Audit: timeout 600s | El script tarda 5-7 min. Tarda mas sin admin (modulos limitados) |
| WiFi: “Cannot connect to 5000” | Arrancar el viewer: python app.py |
| Puerto 5000 ocupado | Usar --port 5001 en una de las apps |
| Splunk no recibe eventos | Dashboard -> Splunk -> Test Connection -> Enable |
| Splunk File Integrity Check warning | Borrar .mdmp en C:\Program Files\Splunk\bin\ y reiniciar Splunk |
Notas
- El dashboard debe reiniciarse tras cambios de código: matar el proceso y arrancar de nuevo
- PS Audit solo funciona en Windows (PowerShell)
- WiFi tools son polling (snapshot en el momento del click), no streaming continuo
- Para streaming continuo a Splunk, usar HEC directo de cada viewer (
SPLUNK_HEC_URL+SPLUNK_HEC_TOKENenv vars) - Ver tambien: Project Overview, Guía de uso, Integracion Hardware y Splunk Export, Integracion Auditing with PowerShell