diff --git a/index.html b/index.html index 17dbf2c..b7e2c3d 100644 --- a/index.html +++ b/index.html @@ -6,6 +6,11 @@ + + + + + +
@@ -674,19 +813,24 @@
PENTESTING ยท HACKING ยท REPORTING
-
-
+
@@ -1058,6 +1202,42 @@
+ +
+
+
+
โœ… Readiness
+

Pre-flight & Reporting Guardrails

+

+ Use these quick checks before starting and before handing off any report. + They keep engagements traceable, authorized and consistent. +

+
+ +
+
+

๐Ÿ“ Before You Run Diablo

+

Ensure the environment is safe to touch and every action is approved.

+
    +
  • Authorization and scope are documented.
    • +
  • Network changes are coordinated with owners.
    • +
  • Fallback contacts are ready if services degrade.
    • +
+
+ +
+

๐Ÿ“ค Before You Deliver

+

Ship only what is necessary for remediation and learning.

+
    +
  • Sensitive or out-of-scope data removed.
    • +
  • Risks prioritized with actionable fixes.
    • +
  • Logs archived securely for audit and lessons learned.
    • +
+
+
+
+
+
@@ -1101,6 +1281,55 @@
+ +
+
+
+
๐Ÿงญ Explore
+

Recommended Pages

+

+ Jump into focused guides that extend the main landing page. Each page stays lightweight, + practical, and ready for real engagements. +

+
+ +
+
+

๐Ÿ““ Playbooks

+

Phase-by-phase flows for recon, exploitation, and post-engagement cleanup.

+
    +
  • Recon and enumeration jump starts.
    • +
  • Privilege escalation and pivoting notes.
    • +
  • Containment and cleanup reminders.
    • +
+ Open Playbooks +
+ +
+

๐Ÿงช Lab Setup

+

Reference builds for safe testing spaces and reproducible demos.

+
    +
  • Segmented networks and logging defaults.
    • +
  • Baseline VM / container profiles.
    • +
  • Patch and rollback routines.
    • +
+ Open Lab Setup +
+ +
+

๐Ÿ“ Reporting

+

Templates, tone, and delivery checklists to ship better findings.

+
    +
  • Executive summaries with risk context.
    • +
  • Repro steps with artifacts and commands.
    • +
  • Hand-off and remediation follow-through.
    • +
+ Open Reporting +
+
+
+
+
@@ -1132,6 +1361,11 @@
+ + + diff --git a/lab-setup.html b/lab-setup.html new file mode 100644 index 0000000..8f711e6 --- /dev/null +++ b/lab-setup.html @@ -0,0 +1,255 @@ + + + + + Diablo ยท Lab Setup + + + + + + +
+
+
+
+
+
DIABLO
+
PENTESTING ยท HACKING ยท REPORTING
+
+
+ +
+
+ +
+
+
+
๐Ÿงช Labs
+

Build Repeatable & Safe Diablo Labs

+

+ Lightweight setups for demos, training, and client environments. Keep experiments contained, + monitored, and easy to rebuild. +

+ Return to readiness checklist +
+
+ +
+
+
+
๐Ÿ—๏ธ Baselines
+

Reference Lab Shapes

+

+ Pick a profile and clone it. Each baseline keeps isolation and observability front-and-center. +

+
+ +
+
+

Solo Research

+

Single host, fast rebuilds.

+
    +
  • 1 VM or container snapshot per technique.
    • +
  • Local logging to file + periodic export.
    • +
  • Reset to golden image weekly.
    • +
+
+ +
+

Client Simulation

+

Mini environment for scoped tests.

+
    +
  • AD/DC + app server + defender box.
    • +
  • Segmented networks with clear firewall rules.
    • +
  • Ops runbook for snapshots and restores.
    • +
+
+ +
+

Collab Training

+

Shared practice with rollback.

+
    +
  • Per-user namespaces or VMs.
    • +
  • Centralized logging and SIEM alerts.
    • +
  • Daily cleanup job to revert state.
    • +
+
+
+
+
+ +
+
+
+
๐Ÿ”’ Hardening
+

Safety & OpSec Defaults

+

Keep the lab useful without leaking secrets or leaving debris.

+
+ +
+
+

Access Control

+
    +
  • Unique credentials per operator.
    • +
  • Vault secrets outside of VM snapshots.
    • +
  • MFA for gateways and dashboards.
    • +
+
+ +
+

Observability

+
    +
  • Sysmon/Osquery where possible.
    • +
  • Packet capture ring buffer with retention policy.
    • +
  • Alert on beacon-like traffic leaving the lab.
    • +
+
+ +
+

Recovery

+
    +
  • Documented rollback steps per host.
    • +
  • Immutable backups for clean baselines.
    • +
  • Post-engagement cleanup sign-off.
    • +
+
+
+
+
+ +
+
+
+
โš™๏ธ Tooling
+

Starter Stack

+

Suggested tools for quick bring-up; swap as needed.

+
+
+
+

Networking

+
    +
  • dnsmasq / bind for controlled DNS.
    • +
  • HAProxy / Traefik for routing experiments.
    • +
  • WireGuard for remote teammate access.
    • +
+
+
+

Instrument

+
    +
  • Elastic or Loki stack for logs.
    • +
  • Grafana dashboards for quick trends.
    • +
  • Filebeat/Winlogbeat agents on all hosts.
    • +
+
+
+

Reset

+
    +
  • VM snapshots per scenario.
    • +
  • Container compose files in git with tags.
    • +
  • Nightly cleanup scripts validated weekly.
    • +
+
+
+
+
+
+ + diff --git a/playbooks.html b/playbooks.html new file mode 100644 index 0000000..75793de --- /dev/null +++ b/playbooks.html @@ -0,0 +1,486 @@ + + + + + Diablo ยท Playbooks + + + + + + +
+
+
+
+
+
DIABLO
+
PENTESTING ยท HACKING ยท REPORTING
+
+
+ +
+
+ +
+
+
+
๐Ÿ““ Playbooks
+

Operational Playbooks for Diablo Runs

+

+ Ready-made flows you can adapt on the fly. Each phase highlights quick wins, safety checks, + and reporting hooks so your runs stay auditable. +

+ Return to main usage guide +
+
+ +
+
+
+
๐Ÿ” Recon
+

Discovery & Scoping

+

+ Start lean. Prioritize targets, document approvals, and keep traffic low-noise before + deep enumeration. +

+
+ +
+
+

Network Sweep

+

Map what answers, then decide whether to pivot deeper.

+
    +
  • Define in-scope subnets and assets.
    • +
  • Low-and-slow ping/ARP discovery first.
    • +
  • Pause if rate limits or SOC alerts fire.
    • +
+
+ +
+

Service Fingerprinting

+

Capture banners and TLS quickly so you can sort findings.

+
    +
  • Enumerate open ports and versions.
    • +
  • Tag crown-jewel services (auth, data, control).
    • +
  • Record timing so retries are consistent.
    • +
+
+
+
+
+ +
+
+
+
๐Ÿ› ๏ธ Access & Escalation
+

Exploit with Guardrails

+

+ Move with intent: validate every exploit, snapshot state, and prep your rollback path + before escalating. +

+
+ +
+
+

Initial Access

+

Keep first touch reversible and logged.

+
    +
  • Exploit selection mapped to CVEs and scope.
    • +
  • Artifacts and payloads stored per-target.
    • +
  • Immediate rollback (service restart or restore point).
    • +
+
+ +
+

Privilege Escalation

+

Escalate safely with minimal persistence.

+
    +
  • Log commands and hash artifacts.
    • +
  • Check defenders' telemetry before loud actions.
    • +
  • Restore configs after testing persistence.
    • +
+
+
+
+
+ +
+
+
+
๐Ÿ“ค Reporting Hooks
+

Close the Loop

+

+ Tie every action back to evidence so the final Markdown report is repeatable and concise. +

+
+ +
+
+

Evidence Pack

+
    +
  • Screenshots, command logs, and hashes per finding.
    • +
  • Environment notes (time, host, IP, creds).
    • +
  • Countermeasure ideas listed next to impact.
    • +
+
+ +
+

Cleanup & Handoff

+
    +
  • Stopped shells, removed test users, restored configs.
    • +
  • Documented what was left intentionally (e.g., test accounts).
    • +
  • Shared remediation sequence with owners.
    • +
+
+
+
+
+
+ + diff --git a/reporting.html b/reporting.html new file mode 100644 index 0000000..205e981 --- /dev/null +++ b/reporting.html @@ -0,0 +1,254 @@ + + + + + Diablo ยท Reporting + + + + + + +
+
+
+
+
+
DIABLO
+
PENTESTING ยท HACKING ยท REPORTING
+
+
+ +
+
+ +
+
+
+
๐Ÿ“ Reporting
+

Ship Clear, Actionable Findings

+

+ Use these outlines to keep Diablo reports concise, reproducible, and tailored to your audience. + Pair them with evidence packs so remediation is fast. +

+ Check readiness before delivery +
+
+ +
+
+
+
๐Ÿ“„ Templates
+

Markdown Skeletons

+

Copy, adjust, and keep consistent across engagements.

+
+
+
+

Executive Snapshot

+
    +
  • Context (scope, timeline, owners).
    • +
  • Top 3 risks with business impact.
    • +
  • Remediation ETA and dependencies.
    • +
+
+
+

Technical Finding

+
    +
  • Title + severity + asset identifier.
    • +
  • Repro steps with commands and responses.
    • +
  • Evidence links (hashes, screenshots, pcaps).
    • +
  • Fix guidance + validation steps.
    • +
+
+
+

Changelog

+
    +
  • Runs executed (date/time/host).
    • +
  • Tools and versions used.
    • +
  • Cleanup and rollback actions taken.
    • +
+
+
+
+
+ +
+
+
+
๐ŸŽฏ Delivery
+

Tailor for the Audience

+

Pick a delivery path that meets stakeholders where they are.

+
+ +
+
+

Stakeholder Brief

+

Slides or PDF with visuals.

+
    +
  • One slide per critical issue.
    • +
  • Impact framed in business terms.
    • +
  • Clear next steps and owners.
    • +
+
+ +
+

Engineer Hand-off

+

Repo or wiki entry with diffs.

+
    +
  • Commands, configs, and sample payloads.
    • +
  • Tests to verify the fix (unit/integration).
    • +
  • Rollback steps documented.
    • +
+
+ +
+

Leadership Summary

+

Concise email or memo.

+
    +
  • One paragraph of highlights.
    • +
  • Risk trend (improving/regressing).
    • +
  • Asks: budget, tooling, or policy changes.
    • +
+
+
+
+
+ +
+
+
+
โœ… QA
+

Pre-Delivery Checklist

+

Last pass before you send anything out.

+
+ +
+
+

Content

+
    +
  • Redacted secrets and client-identifying data.
    • +
  • CVSS/impact ratings match evidence.
    • +
  • Findings mapped to scope and ticket IDs.
    • +
+
+ +
+

Format

+
    +
  • Headings and numbering consistent.
    • +
  • Images compressed; hashes recorded.
    • +
  • Accessibility tags on diagrams/charts.
    • +
+
+ +
+

Handoff

+
    +
  • Delivery channel agreed (email, portal, live readout).
    • +
  • Links to evidence packs and lab notes.
    • +
  • Plan for follow-up validation scheduled.
    • +
+
+
+
+
+
+ +