# Performing Vulnerability Scanning With Nessus

> agentic-workflows-blueprint.workflow.performing-vulnerability-scanning-with-nessus

- Skill: `devton/performing-vulnerability-scanning-with-nessus` (Agent Skill)
- Install (CLI): `npx skillmds@latest add devton/performing-vulnerability-scanning-with-nessus`
- Raw SKILL.md: https://api.skillmd.com/api/skills/devton/performing-vulnerability-scanning-with-nessus/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: devton (https://skillmd.com/u/devton)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/devton/performing-vulnerability-scanning-with-nessus

---

## agentic-workflows-blueprint.workflow.performing-vulnerability-scanning-with-nessus

### Goal

Execute Nessus-based vulnerability assessments with validated findings, risk-prioritized remediation guidance, and auditable scan evidence.

### Scope

- Applies to: authorized vulnerability scanning engagements using Nessus across hosts, network infrastructure, and services.
- Does not cover: replacing manual penetration testing or unauthorized scanning operations.

### Triggers

- "Run vulnerability scan with Nessus"
- "Perform authenticated patch/compliance assessment"
- "Validate remediation with rescan evidence"
- "Produce prioritized CVE-based remediation plan"

### Inputs

- `authorizedScope`: approved target ranges/assets and scanning window
- `scanPolicy`: Nessus policy and plugin family settings
- `credentialSet` (optional): authenticated scan credentials and constraints
- `riskContext`: asset criticality and exposure profile
- `reportingRequirements`: executive/technical output expectations
- `rescanPlan` (optional): timeline for validation after remediation

### Invariants

- Scanning must only run within explicit written authorization boundaries.
- Credentialed scan integrity must be verified before trusting results.
- Critical/high findings require false-positive triage before escalation.
- Findings must map to concrete remediation actions and owners.
- Scan metadata (plugin date, policy, auth status) must be preserved.

### Procedure

1. **Plan and configure scan**
   - Confirm scope, timing, and risk controls for potentially fragile systems.
   - Configure policy, plugin families, and performance limits.

2. **Run scan and monitor**
   - Execute scan in authorized window.
   - Monitor auth success, host reliability, and plugin stability during execution.

3. **Validate result quality**
   - Confirm authenticated coverage and identify fallback unauthenticated results.
   - Remove obvious noise and investigate likely false positives.

4. **Prioritize findings**
   - Rank by severity, exploitability, exposure, and asset criticality.
   - Group remediation by fix action to accelerate closure.

5. **Publish actionable report**
   - Produce executive and technical outputs with remediation matrix.
   - Include scan metadata and confidence notes.

6. **Rescan and verify**
   - Re-scan remediated assets.
   - Confirm closure and track residual findings.

### Outputs

- Nessus scan result package (raw + curated findings view).
- Prioritized remediation matrix with SLA and ownership.
- False-positive validation notes and confidence rationale.
- Rescan verification report for remediated findings.

### Review gate

- [ ] Scan ran within authorized scope and approved window.
- [ ] Authentication coverage is measured and reported.
- [ ] Critical/high findings are validated and prioritized.
- [ ] Remediation guidance is actionable and ownership-bound.
- [ ] Rescan confirms remediation outcomes where required.

### References

- `../../SKILL.md`
- `../triaging-vulnerabilities-with-ssvc-framework/SKILL.md`
- `../review/SKILL.md`
- [Interactive HTML View](./README.html)