agentleFS
Sign inStart free
noahfranklinnoahfranklin/gideon/skills/network-pentest/SKILL.md

network-pentest

Skill2 starsChanged 47 days agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    SNMP: default/community strings → device config leakage.

    line 28
  2. Distinctive:

    Check for common misconfigs: default creds, anonymous access, weak protocols, missing patches, exposed management interfaces.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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).
  • Check for common misconfigs: default creds, anonymous access, weak protocols, missing patches, exposed management interfaces.

4. Network-level attacks (internal, in-scope)

  • Name-resolution poisoning & relay (LLMNR/NBT-NS/mDNS → credential capture; SMB relay where signing is off).
  • IPv6 misconfiguration abuse.
  • Credential access & reuse across hosts (spraying with lockout awareness).
  • Pivoting/tunneling to reach segmented networks (document the path).
  • Detection signal for defenders: these generate distinctive traffic — verify the SOC sees them.

5. Remediation themes

SMB signing enforced, disable LLMNR/NBT-NS, patch management, remove default/weak creds, segment and restrict management interfaces, strong protocols only, network monitoring/alerting for poisoning and lateral movement.

6. Tooling

nmap/masscan, netexec (cme successor), responder (capture), impacket suite, enum4linux-ng, snmpwalk, hydra (respect lockout), nuclei. Follow the RoE-approved set.

7. Reporting & handoff

Route AD to active-directory-pentest, cloud to cloud-pentest, network gear to network-device-pentest, priv-esc to privilege-escalation, and post-access work to post-exploitation. Checklist: references/network-checklist.md.

<sub>© 2026 noahfranklin · Part of the Gideon security suite · MIT License · Original work.</sub>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free