Back to catalog
Static reviewDevelopment

Skill dossier

performing-vulnerability-scanning-with-nessus

Source declaration

Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network infrastructure, servers, and applications. The scanner correlates findings with CVE databases and CVSS scores to produce prioritized remediation guidance. Activates for requests involving vulnerability scanning, Nessus assessment, patch compliance checking, or automated vulnerability detection.

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

Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network infrastructure, servers, and applications. The scanner correlates findings with CVE databases and CVSS scores to produce prioritized remediation guidance. Activates for requests involving vulnerability scanning, Nessus assessment, patch compliance checking, or automated vulnerability detection.

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.

Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network infrastructure, servers, and applications. The scanner correlates findings with CVE databases and CVSS scores to produce prioritized remediation guidance. Activates for requests involving vulnerability scanning, Nessus assessment, patch compliance checking, or automated vulnerability detection. 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/performing-vulnerability-scanning-with-nessus/SKILL.md:L54]
  • Step 1: Scan Configuration [Source statement; provisional, not tested. Evidence: skills/performing-vulnerability-scanning-with-nessus/SKILL.md:L56]
  • Step 2: Scan Execution and Monitoring [Source statement; provisional, not tested. Evidence: skills/performing-vulnerability-scanning-with-nessus/SKILL.md:L66]
  • Step 3: Results Analysis and Validation [Source statement; provisional, not tested. Evidence: skills/performing-vulnerability-scanning-with-nessus/SKILL.md:L76]
  • Step 4: Vulnerability Prioritization [Source statement; provisional, not tested. Evidence: skills/performing-vulnerability-scanning-with-nessus/SKILL.md:L87]
  • Step 5: Report Generation [Source statement; provisional, not tested. Evidence: skills/performing-vulnerability-scanning-with-nessus/SKILL.md:L97]

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/performing-vulnerability-scanning-with-nessus/SKILL.md:L1-L33]

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
31.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-vulnerability-scanning-with-nessus/LICENSEOther11 KB
skills/performing-vulnerability-scanning-with-nessus/references/api-reference.mdReference2.4 KB
skills/performing-vulnerability-scanning-with-nessus/scripts/agent.pyScript7 KB
skills/performing-vulnerability-scanning-with-nessus/SKILL.mdInstruction11 KB

SKILL.md frontmatter

{
  "name": "performing-vulnerability-scanning-with-nessus",
  "description": "Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network infrastructure, servers, and applications. The scanner correlates findings with CVE databases and CVSS scores to produce prioritized remediation guidance. Activates for requests involving vulnerability scanning, Nessus assessment, patch compliance checking, or automated vulnerability detection.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "vulnerability-scanning",
    "Nessus",
    "CVE",
    "patch-management",
    "Tenable"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1003"
  ]
}

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: Scan Configuration

    Source-described action candidate under “Step 1: Scan Configuration”; not verified execution.

  4. 04
    Decision

    Scan type selection: Choose "Advanced Scan" for full control over plugin families, or "Credentialed Patch Audit" for patch compliance. Avoid "Basic Network Scan" for penetration tests as it uses a limited plugin set.

    Source-described decision candidate under “Step 1: Scan Configuration”; not verified execution.

  5. 05
    Action

    Discovery settings: Configure port scanning to scan all 65,535 TCP ports and top 1,000 UDP ports. Set host discovery to use ARP (local), TCP SYN, and ICMP for maximum coverage.

    Source-described action candidate under “Step 1: Scan Configuration”; not verified execution.

  6. 06
    Action

    Authentication: Add Windows credentials (domain account with local admin), SSH credentials (key-based preferred over password), SNMP credentials (v3 with authPriv preferred), and database credentials for database-specific checks.

    Source-described action candidate under “Step 1: Scan Configuration”; not verified execution.

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

    Plugin configuration: Enable all plugin families relevant to the target environment. For penetration testing, ensure "Denial of Service" plugins are disabled unless explicitly authorized. Enable CGI scanning for web servers.

    Source-described action candidate under “Step 1: Scan Configuration”; not verified execution.

  2. 08
    Action

    Performance settings: Set maximum concurrent hosts per scanner (default 30, reduce for sensitive networks), maximum concurrent checks per host (4-5 for production, higher for test environments), and network timeout values appropriate for the target network.

    Source-described action candidate under “Step 1: Scan Configuration”; not verified execution.

  3. 09
    Action

    Step 2: Scan Execution and Monitoring

    Source-described action candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  4. 10
    Action

    Start the scan during the authorized testing window

    Source-described action candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  5. 11
    Action

    Monitor scan progress through the Nessus web interface, checking for hosts timing out, authentication failures, or plugins causing errors

    Source-described action candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  6. 12
    Action

    Watch for credential failures indicated by "Authentication Failure" results; these mean the authenticated scan fell back to unauthenticated mode, producing incomplete results

    Source-described action candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  7. 13
    Decision

    If specific hosts are crashing or becoming unresponsive, pause the scan, exclude those hosts, and report the issue to the client

    Source-described decision candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  8. 14
    Input

    For large networks (1,000+ hosts), consider splitting scans into smaller subnets to manage load and allow restartability

    Source-described input candidate under “Step 2: Scan Execution and Monitoring”; not verified execution.

  9. 15
    Action

    Step 3: Results Analysis and Validation

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  10. 16
    Action

    Analyze scan results to separate true positives from false positives:

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  11. 17
    Action

    Sort by severity: Start with Critical and High findings; these represent the most exploitable and impactful vulnerabilities

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  12. 18
    Action

    Validate authentication: Verify that plugin 19506 (Nessus Scan Information) shows "Credentialed checks: yes" for each host. Unauthenticated results miss local vulnerabilities.

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  13. 19
    Action

    Eliminate informational noise: Filter out informational findings unless they reveal useful information for manual testing (service banners, SSL certificate details, open ports)

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  14. 20
    Decision

    Cross-reference CVEs: For each Critical/High finding, verify the CVE in the National Vulnerability Database. Check if the vulnerability has a public exploit (Exploit-DB, Metasploit module).

    Source-described decision candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  15. 21
    Action

    False positive identification: Common false positives include version-based detection where backported patches make the software appear vulnerable (common in RHEL/CentOS). Check `rpm -q --changelog <package>` on the target to verify.

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  16. 22
    Action

    Group by remediation: Organize findings by the action needed to fix them (e.g., "Apply Windows KB5034441" affects 47 hosts) rather than listing each instance individually

    Source-described action candidate under “Step 3: Results Analysis and Validation”; not verified execution.

  17. 23
    Action

    Step 4: Vulnerability Prioritization

    Source-described action candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  18. 24
    Action

    CVSS score: Use the CVSS v3.1 base score as the starting point. Scores 9.0-10.0 are Critical, 7.0-8.9 High, 4.0-6.9 Medium, 0.1-3.9 Low.

    Source-described action candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  19. 25
    Action

    Exploit availability: Increase priority for vulnerabilities with publicly available exploit code, especially Metasploit modules or weaponized PoCs

    Source-described action candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  20. 26
    Action

    Network exposure: A critical vulnerability on an internet-facing system is higher priority than the same vulnerability on an isolated internal server

    Source-described action candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  21. 27
    Action

    Asset criticality: Consider the business value of the affected system. Domain controllers, databases with PII, and payment processing systems warrant higher priority.

    Source-described action candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  22. 28
    Decision

    Compensating controls: Reduce priority if the vulnerability is mitigated by network segmentation, WAF rules, or EDR protections (document the compensating control)

    Source-described decision candidate under “Step 4: Vulnerability Prioritization”; not verified execution.

  23. 29
    Output

    Step 5: Report Generation

    Source-described output candidate under “Step 5: Report Generation”; not verified execution.

  24. 30
    Output

    Generate a comprehensive vulnerability scan report:

    Source-described output candidate under “Step 5: Report Generation”; not verified execution.

  25. 31
    Output

    Export the Nessus report in both executive (PDF) and detailed (CSV/HTML) formats

    Source-described output candidate under “Step 5: Report Generation”; not verified execution.

  26. 32
    Output

    Create a custom report that includes only validated findings with false positives removed

    Source-described output candidate under “Step 5: Report Generation”; not verified execution.

  27. 33
    Action

    Include a remediation priority matrix mapping each vulnerability to its recommended fix, affected hosts, and timeline

    Source-described action candidate under “Step 5: Report Generation”; not verified execution.

  28. 34
    Action

    Add context from manual validation (e.g., "This finding was confirmed exploitable during the penetration test")

    Source-described action candidate under “Step 5: Report Generation”; not verified execution.

  29. 35
    Action

    Include scan metadata: date/time, scanner version, plugin set date, scan policy used, authentication success rate

    Source-described action candidate under “Step 5: Report Generation”; not verified execution.

  30. 36
    Action

    Key Concepts

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

  31. 37
    Action

    Tools & Systems

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

  32. 38
    Action

    Common Scenarios

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

  33. 39
    Action

    Configure authenticated scan with domain service account for Windows and SSH key for Linux hosts

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  34. 40
    Action

    Use the PCI-DSS scan policy template with all relevant plugin families enabled

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  35. 41
    Action

    Scan all 200 CDE hosts during the Saturday maintenance window (02:00-06:00)

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  36. 42
    Action

    Identify 847 findings: 12 Critical, 34 High, 189 Medium, 612 Low/Informational

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  37. 43
    Action

    Validate Critical findings: 3 are false positives (backported patches on RHEL), 9 are confirmed vulnerabilities

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  38. 44
    Action

    Group remaining findings by remediation action: 6 require Windows patches, 2 require Apache upgrades, 1 requires TLS configuration hardening

    Source-described action candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  39. 45
    Output

    Generate PCI-compliant report showing no Critical or High vulnerabilities remain unaddressed (after remediation and rescan)

    Source-described output candidate under “Scenario: Quarterly PCI-DSS Vulnerability Scan for a Retail Company”; not verified execution.

  40. 46
    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

13 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 useObserved
Medium

Network access is mentioned

6 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 6 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

4 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 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.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

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 1 location(s) in the collected text; 1 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/performing-vulnerability-scanning-with-nessus/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/performing-vulnerability-scanning-with-nessus/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/performing-vulnerability-scanning-with-nessus
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.