← ClaudeAtlas

network-pentestlisted

Use when testing network infrastructure — external or internal — for security weaknesses: host/service discovery, vulnerability identification, common service misconfigurations (SMB, RDP, SSH, SNMP, LDAP, databases), network-level attacks (relay, poisoning), and pivoting. Follows PTES and NIST SP 800-115, mapped to MITRE ATT&CK, with detection and remediation. Authorized engagements only.
noahfranklin/gideon · ★ 2 · AI & Automation · score 70
Install: claude install-skill noahfranklin/gideon
# Network / Infrastructure Penetration Testing Assessment of network hosts and services following **PTES** and **NIST SP 800-115**, with techniques mapped to **MITRE ATT&CK**. Covers external perimeter and internal (assumed-breach) testing. ## 0. Authorization gate - [ ] Written scope: IP ranges/CIDRs, external vs internal, excluded hosts. - [ ] Fragile-system list (SCADA/OT, legacy) explicitly excluded unless cleared. - [ ] Test window, allowed intensity, and emergency contact. - [ ] Data-handling rules for anything accessed. ## 1. Methodology ``` Discovery ─► Service enum ─► Vuln identification ─► Validation/exploitation └─► (internal) credential access ─► lateral movement ─► document & report ``` ## 2. Discovery & enumeration - Host discovery across the scope; TCP/UDP port scans; service + version detection. - Per-service enumeration: - **SMB:** shares, null/guest sessions, signing status, OS info. - **RDP:** exposure, NLA, weak/legacy config. - **SSH:** auth methods, weak algorithms, key exposure. - **SNMP:** default/community strings → device config leakage. - **LDAP/Kerberos:** directory info (hand AD specifics to `active-directory-pentest`). - **Databases (MSSQL/MySQL/Postgres/Mongo/Redis):** exposure, default/weak creds, unauthenticated access. - **Web services:** route to `web-app-pentest` / `api-security-audit`. ## 3. Vulnerability identification - Map services/versions to known CVEs; validate real exploitability (don't ship raw scanner output