Back to catalog
Static reviewDevelopment

Skill dossier

detecting-port-scanning-with-fail2ban

Source declaration

Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing.

The author's original description, preserved in English. It describes intent, not verified performance.

Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L51]
  • Step 1: Install and Configure Fail2ban [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L53]
  • Step 2: Create Custom Port Scan Detection Filter [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L105]
  • Step 3: Configure Jail for Port Scanning [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L151]
  • Step 4: Configure Advanced Ban Actions [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L199]
  • Step 5: Test and Validate Detection [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L239]
  • Step 6: Monitor and Maintain [Source statement; provisional, not tested. Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L271]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L1-L30]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-port-scanning-with-fail2ban/LICENSEOther11 KB
skills/detecting-port-scanning-with-fail2ban/references/api-reference.mdReference2 KB
skills/detecting-port-scanning-with-fail2ban/scripts/agent.pyScript8.2 KB
skills/detecting-port-scanning-with-fail2ban/SKILL.mdInstruction12.7 KB

SKILL.md frontmatter

{
  "name": "detecting-port-scanning-with-fail2ban",
  "description": "Configures Fail2ban with custom filters and actions to detect port scanning activity, SSH brute force attempts, and network reconnaissance, automatically banning offending IP addresses and alerting security teams to suspicious network probing.\n",
  "domain": "cybersecurity",
  "subdomain": "network-security",
  "tags": [
    "network-security",
    "fail2ban",
    "port-scanning",
    "intrusion-prevention",
    "automated-defense"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.IR-01",
    "DE.CM-01",
    "ID.AM-03",
    "PR.DS-02"
  ],
  "mitre_attack": [
    "T1046",
    "T1040",
    "T1557",
    "T1071",
    "T1595"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Install and Configure Fail2ban

    Source-described action candidate under “Step 1: Install and Configure Fail2ban”; not verified execution.

  4. 04
    Action

    Step 2: Create Custom Port Scan Detection Filter

    Source-described action candidate under “Step 2: Create Custom Port Scan Detection Filter”; not verified execution.

  5. 05
    Action

    Step 3: Configure Jail for Port Scanning

    Source-described action candidate under “Step 3: Configure Jail for Port Scanning”; not verified execution.

  6. 06
    Action

    Step 4: Configure Advanced Ban Actions

    Source-described action candidate under “Step 4: Configure Advanced Ban Actions”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Action

    Step 5: Test and Validate Detection

    Source-described action candidate under “Step 5: Test and Validate Detection”; not verified execution.

  2. 08
    Action

    Step 6: Monitor and Maintain

    Source-described action candidate under “Step 6: Monitor and Maintain”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Install Fail2ban and configure it to monitor Nginx access logs for scanning patterns (404/403 responses to known vulnerability paths)

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  7. 13
    Action

    Create a custom `http-scan` filter matching common scanner signatures and vulnerability probing URIs

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  8. 14
    Action

    Set maxretry to 10 within a 5-minute findtime, with a 1-hour bantime for first offense

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  9. 15
    Action

    Enable the recidive jail to escalate ban duration to 7 days for repeat offenders

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  10. 16
    Action

    Configure webhook notifications to Slack for real-time visibility of banning activity

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  11. 17
    Action

    Add iptables logging rules for SYN packets to closed ports to detect port scanning

    Source-described action candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  12. 18
    Output

    Create a daily report script showing banned IPs, attack patterns, and geographic distribution

    Source-described output candidate under “Scenario: Defending a Public-Facing Web Server Against Automated Scanning”; not verified execution.

  13. 19
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

80 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

4 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

43 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 43 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

33 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 33 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-port-scanning-with-fail2ban/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/detecting-port-scanning-with-fail2ban/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/detecting-port-scanning-with-fail2ban
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.