Skip to content
Back to skills

Network

ASecurity

Reconstruct Hetzner public/private reachability and environment segmentation for cross-layer security analysis.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
devopsawsdatabasesecurity

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add jpolec/hetzner-cloud-audit-skills --skill network --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Network?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Network
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jpolec-network/badge)](https://www.skillsdirectory.com/skills/jpolec-network)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hetzner-network-audit
description: Reconstruct Hetzner public/private reachability and environment segmentation for cross-layer security analysis.
---

# Hetzner Network Audit

Required inputs: cloud inventory plus any authorized host firewall, socket, container publication, and service bind evidence. No packet scanning or remote connection attempts are allowed by default.

Workflow: map interfaces, subnets, routes, firewall directions/sources/ports, load-balancer listeners, published container ports, host rules, and service bind addresses into directed edges. Run `hetzner-audit network --input snapshot.json --verify`. Prove each reported path from source to target and list unknown hops.

Check public SSH/management/database/cache exposure, missing controls on public hosts, broad lateral movement, and declared environment separation. An open provider rule alone is a candidate; verify attachment and downstream controls. Output an attack path with evidence per hop and one of `confirmed`, `needs_validation`, or `rejected`.

Hetzner Cloud Firewalls do not filter private network traffic (https://docs.hetzner.com/cloud/firewalls/faq/). Every server attached to a private network can reach every port on every other member. Firewall rules whose sources are private CIDRs have no effect on that traffic. Only host firewalls and service authentication restrict lateral movement, so ask for host-firewall evidence before calling a private path blocked.

Edge proxies (Cloudflare, Fastly, Bunny CDN, AWS CloudFront, Gcore, Imperva) are recognized from their published, dated ranges; Akamai and Sucuri cannot be, so ask the owner before calling an allow-list a CDN. Mesh VPN UDP ports (Tailscale 41641, WireGuard/NetBird 51820, ZeroTier 9993) are not exposure. A server with no public ingress, reached through a mesh VPN or a tunnel (Cloudflare Tunnel, ngrok), is the pattern to recommend. The full list is in `docs/coverage.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.