Scaniacsod

# 1. Clone the repo
git clone https://github.com/scaniac/scaniac-sod.git
cd scaniac-sod
# 2. Copy example env & edit as needed
cp .env.example .env
nano .env   # <-- set DB passwords, API keys, etc.
# 3. Pull images & start
docker compose pull
docker compose up -d

The UI will be reachable at https://<host>:8443. Default admin credentials are admin / Scaniac2024! – change immediately.

| Area | Recommendation | |------|----------------| | Network Segmentation | Run Scaniac scanners on a dedicated red VLAN; use firewall rules to limit outbound traffic. | | Credential Management | Store privileged credentials in HashiCorp Vault; reference via vault:secret/path. | | Rate Limiting | Adjust Masscan/Nmap rates per subnet to avoid DoS on production services. | | Logging | Forward all scanner logs to central SIEM; keep 90 days retention for audit. | | Patch Management | Automate re‑scan after patch deployment (Playbook: trigger-recheck.yml). | | Change Management | Require change‑request approval before modifying scan schedules. | | Backup | Daily dump of PostgreSQL (pg_dump) and Elasticsearch snapshot. | | Compliance | Use built‑in PCI‑DSS and HIPAA templates for reporting. | scaniacsod


Export – CSV, JSON, or PDF for compliance reporting. The UI will be reachable at https://&lt;host&gt;:8443


Scaniacsod — a compact, memorable name that could suit a tech project, username, indie game, or niche brand. It evokes "scan" and "sod" (ground/soil) with a playful, slightly cryptic tone. Export – CSV, JSON, or PDF for compliance reporting

error: Content is protected !!
Scroll to Top
2
0
Would love your thoughts, please comment.x
()
x