protocol-surface-triage

Classifies discovered network services into infrastructure roles and weak-boundary hypotheses.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill protocol-surface-triage-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol-surface-triage
Source: https://github.com/dbx0/skills/tree/main/skills/methodology/triage/protocol-surface-triage
Command: npx skills add https://github.com/dbx0/skills --skill protocol-surface-triage-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw port scans and banner grabs produce lists of open services but no insight into what those services mean for an attack surface. This Skill turns discovered ports, banners, certificates, and reverse DNS into an infrastructure role map, weak-boundary hypotheses, and a concrete follow-up validation plan. ## Core Features & Use Cases - Role-Based Clustering: Groups services into identity/directory, remote administration, file/data movement, data stores, and web/app management categories. - Correlation Analysis: Cross-references TLS certificate names, reverse DNS, host naming conventions, and adjacent web interfaces to reveal internal naming and environment drift (dev, test, backup, migration). - Weak-Boundary Hypotheses: Prioritizes exposed management planes, duplicated trust planes on one host, legacy nodes, and data services lacking segmentation. - Use Case: During an external assessment, a scan reveals LDAP, RDP, an SMB share, and an admin portal across several hosts. Use this Skill to map each service to its operating role, flag a backup server with looser controls, and produce a shortlist of management planes for manual review. ## Quick Start Triage these discovered services and banners into infrastructure roles and weak-boundary hypotheses with a follow-up validation plan.

Frequently Asked Questions about protocol-surface-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage open ports and services after a network scan?

Cluster each discovered service by operating role: identity/directory, remote administration, file and data movement, data stores, and web/app management. Then correlate banners, TLS certificate names, and reverse DNS to build an infrastructure role map and prioritize weak-boundary hypotheses.

What should I look for in service banners and TLS certificates during recon?

Look for product family identification, internal naming leaked through certificate subjects, host naming conventions suggesting dev/test/backup environments, and whether the same hostname exposes both user and operator planes. These clues connect network services to organizational trust boundaries.

How do I identify weak network boundaries from exposed services?

Prioritize hypotheses like management interfaces exposed beyond their intended audience, duplicated trust planes on one host, backup or migration nodes with looser controls, and data services lacking the segmentation of the main application.

Does this methodology cover telecom or mobile carrier network services?

Yes, it recognizes telecom core surfaces such as 3GPP GBA/BSF, SIP/IMS, Diameter, and HSS/AAA through hostnames like *.bsf.* or certificates issued to O=GSM Association. Those cases are handed off to the telecom-surface-triage skill for specialized analysis.

When should I use service-based triage instead of web application testing?

Use it when recon extends beyond HTTP into infrastructure and management services like LDAP, RDP, SMB, databases, or admin portals. It answers what operating role a service implies and which trust boundary sits next to it, rather than testing application-layer vulnerabilities.