performing-authenticated-vulnerability-scan

Perform credentialed vulnerability scans using Nessus, Qualys, or OpenVAS with SSH, WinRM, and SNMP credentials.

954|172|Updated Mar 13, 2026

Search Tags:#ssh #patch management #vulnerability scanning #cve #nessus #authenticated scan #credentialed scan

Ready to run

npx skills add https://github.com/xalgord/xalgorix --skill performing-authenticated-vulnerability-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performing-authenticated-vulnerability-scan
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/vulnerability-management/performing-authenticated-vulnerability-scan
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-authenticated-vulnerability-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unauthenticated vulnerability scans miss 45-60% of vulnerabilities because they can only infer issues from external banners and services. This Skill guides you through credentialed scanning, where valid system credentials allow deep inspection of installed software, patch levels, configurations, and security settings with far fewer false positives.

Core Features & Use Cases

Multi-Platform Credential Setup: Configure SSH keys, sudo elevation, Windows domain accounts, WinRM, SNMPv3, and database credentials for Linux, Windows, network devices, and databases.
Scanner Integration: Step-by-step credential configuration and scan launch via the Nessus API, with vault-based secret storage guidance.
Credential Validation: Verify scan success using Nessus plugins 19506, 21745, 110385, and 117887 to detect silent authentication failures.
Use Case: A security team needs to audit a production subnet. Use this Skill to create least-privilege service accounts, distribute SSH keys, configure Nessus with vaulted credentials, and validate that credentialed checks actually ran on every host.

Quick Start

Set up an authenticated Nessus vulnerability scan against my 192.168.1.0/24 subnet with SSH key credentials for Linux hosts and a domain service account for Windows hosts.

Frequently Asked Questions about performing-authenticated-vulnerability-scan

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

FAQPage Schema

How do I set up an authenticated vulnerability scan with Nessus?▼

Create a dedicated service account, configure SSH key or Windows domain credentials in the scan policy, then launch the scan via the Nessus API with the credentials block. Validate success afterward using plugins 19506, 21745, and 110385.

What is the difference between authenticated and unauthenticated vulnerability scanning?▼

Authenticated scanning logs into target hosts with valid credentials to directly query installed packages, patches, and configurations, detecting 45-60% more vulnerabilities. Unauthenticated scanning only infers issues from external banners, producing more false positives.

What credentials does Nessus need for Windows and Linux scans?▼

Linux targets need SSH key or password authentication with sudo elevation for local checks. Windows targets need a domain or local admin account accessible via SMB, WMI, or WinRM over HTTPS.

Why does my credentialed scan show fewer results than expected?▼

Common causes include failed authentication, missing sudo elevation on Linux, UAC blocking remote checks on Windows, or firewalls blocking SSH/WMI/WinRM ports. Check Nessus plugins 19506 and 110385 to confirm credential success per host.

How should vulnerability scanner credentials be stored securely?▼

Store credentials in a secrets vault such as HashiCorp Vault, CyberArk, or AWS Secrets Manager rather than plaintext scan configurations. Rotate them every 90 days, apply least privilege, and audit all service account login events in a SIEM.