AGENT SKILL

config-audit

Security-audit an existing network device configuration — router, switch, firewall, wireless controller — for weak credentials, insecure management access, missing hardening, and best-practice violations. Use whenever the user pastes a device config or points at a .cfg file, whether or not they ask you to review/audit/harden/check it — a bare paste ("here's r1's config", "can you look at this?") is itself the trigger, not just an explicit audit verb. Not for writing a new config (use generate-config) and not for diagnosing an active outage (use troubleshoot).

License 许可
MIT
最近更新
2026-11-02
Stars
★ 0
Forks
0

01 前言 Front Matter

name
config-audit
description
Security-audit an existing network device configuration — router, switch, firewall, wireless controller — for weak credentials, insecure management access, missing hardening, and best-practice violations. Use whenever the user pastes a device config or points at a .cfg file, whether or not they ask you to review/audit/harden/check it — a bare paste ("here's r1's config", "can you look at this?") is itself the trigger, not just an explicit audit verb. Not for writing a new config (use generate-config) and not for diagnosing an active outage (use troubleshoot).
when_to_use
Trigger phrases: "here's r1's config", "can you look at this?", "is this config secure?", "harden this", "check this running-config", a pasted show running-config or a .cfg file, SNMP community strings or telnet enabled, a pre-change or compliance config review.
allowed-tools
mcp__plugin_damira_damira__analyze_config, mcp__plugin_damira_damira__damira_search_vendor_docs

03 SKILL.md 正文

Configuration Security Audit

Audit network device configurations for security vulnerabilities and best practice violations.

Workflow

Step 1: Get the Config

Two methods:

  • File reference: User references a file (e.g., @configs/router.cfg). Read the file contents.
  • Paste: User pastes config text directly.

If auditing a directory, read each .cfg or .conf file and audit them individually.

Step 2: Run Security Audit

Call the analyze_config MCP tool with:

  • config_text: the full configuration text
  • check_type: "all" (covers both security and best practices)

If the MCP tool isn't available, run the same local check (<plugin root> is two levels above this skill's base directory; the config never leaves the machine):

python3 "<plugin root>/scripts/audit_config.py" configs/router.cfg --check-type all

IMPORTANT: You MUST call the analyze_config MCP tool (or the script above). Do NOT just review the config visually — the tool catches specific patterns (type 7 passwords, SNMP communities, HTTP management, missing NTP) with severity ratings.

Step 3: Present Findings

Format findings by severity:

CRITICAL / HIGH:

  • List each finding with line number, issue, and remediation command

MEDIUM:

  • List each finding with recommendation

LOW / INFORMATIONAL:

  • List in a table

Step 4: Remediation

For each finding, provide:

  • The exact CLI command to fix it (vendor-specific)
  • Call damira_search_vendor_docs if you need platform-specific remediation syntax

Step 5: Generate Report (Optional)

If multiple configs were audited, offer:

"Want me to save the audit report to documents/?"

Save as documents/config-audit-{date}.md with:

  • Summary table (device, findings count by severity)
  • Detailed findings per device
  • Remediation commands

04 同仓库更多 Skills

ciscoittech
ciscoittech/damira-plugins

upgrade-plan

Ask Damira to assess a version-to-version upgrade of a network platform and produce the MOP and change control. Use when the user names a product and a target release — "IOS-XE 17.6.5 to 17.9.5", "CUCM 12.5 SU7 to 15", "PAN-OS 10.2 to 11.1" — or asks what breaks, what the risk is, or how long a maintenance window needs to be. Covers CUCM, IOS-XE, IOS-XR, NX-OS, PAN-OS, FortiOS, Junos, ISE, ASA, WLC/Catalyst 9800. Not for platform-to-platform migration (CUCM to Webex Calling, on-prem to cloud) and not for diagnosing a fault after an upgrade — use troubleshoot for that.

★ 0
ciscoittech
ciscoittech/damira-plugins

troubleshoot

Ask Damira to diagnose an active, in-progress network fault. Use when the user reports something broken right now — an outage, a flapping interface, a BGP or OSPF adjacency down, dropped or blackholed traffic, failed calls, users unable to connect — or pastes show/log output for analysis. Also fires on direct questions like "why is BGP down" or "why is OSPF stuck in EXSTART". Returns vendor-specific diagnosis with exact CLI commands. Do NOT use for "how does X work" protocol questions, for reviewing a config that is not currently broken (use config-audit), or for planning an upgrade (use upgrade-plan).

★ 0
ciscoittech
ciscoittech/damira-plugins

source-of-truth-change

Turn intended state in the engineer's source of truth (NetBox or Nautobot) into a validated change, then hand it to the automation they already run — an Ansible Automation Platform job in check mode, a pyATS/Genie before-and-after diff, or a Terraform plan. Use when the user asks to make a change "from NetBox" or "from Nautobot", to push what the source of truth says, to bring devices in line with intended state, or to run a validated playbook through AAP or pyATS. Damira never applies the change; the engineer does. For a playbook with no source of truth use generate-playbook, for Terraform alone use generate-terraform, and for an active outage use troubleshoot.

★ 0
ciscoittech
ciscoittech/damira-plugins

lab-test-change

Test a network change in a throwaway ContainerLab lab before it goes near production — deploy the lab, apply the playbook or script, run show-command or pyATS/Genie checks, report pass/fail, and always destroy the lab. Use when the user says "test this in a lab first", "prove this change before the window", "dry-run this playbook against a lab", or wants evidence a change works before a CAB. Needs docker and containerlab on the engineer's machine; without them it validates only and says so. To only build a lab, use generate-lab; to write the change, use generate-playbook, generate-automation or generate-terraform.

★ 0
ciscoittech
ciscoittech/damira-plugins

generate-workbook

Build an Excel workbook (.xlsx) for a network procedure — a migration, platform migration, security audit, change control, or incident-response workbook — grounded in Damira evidence, with an HTML preview. Use when the user asks for a spreadsheet, workbook, tracker, or Excel version of a migration plan, cutover, audit findings, change record, or incident timeline. For a version-to-version upgrade, use upgrade-plan (it offers the workbook itself). Not for diagnosing an active fault — use troubleshoot.

★ 0
ciscoittech
ciscoittech/damira-plugins

generate-tests

Write network tests — pyATS/Genie learn, change, learn, diff jobs that prove a change did what it should and nothing else, and pytest tests for automation scripts — then validate them locally. Use when the user asks for pyATS, Genie, AEtest, a testbed file, pre/post change verification, state snapshots, or unit tests for a Nornir/Netmiko script. For the change itself use generate-playbook, generate-automation or generate-terraform.

★ 0