advisory-exposure
Check a device inventory against published security advisories - which devices are exposed to critical or high CVEs at their exact running versions, through which vendor advisory, and what to patch first. Use when the user asks "are we exposed to...", "which devices are affected by CVE...", gives an inventory or version list and asks about vulnerabilities, or Security wants an exposure report. Covers Cisco ISE, IOS-XE, NX-OS, ASA, FTD, Palo Alto PAN-OS, FortiOS, Junos, Arista EOS. Not for planning the upgrade itself (use upgrade-plan).
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- advisory-exposure
- description
- Check a device inventory against published security advisories - which devices are exposed to critical or high CVEs at their exact running versions, through which vendor advisory, and what to patch first. Use when the user asks "are we exposed to...", "which devices are affected by CVE...", gives an inventory or version list and asks about vulnerabilities, or Security wants an exposure report. Covers Cisco ISE, IOS-XE, NX-OS, ASA, FTD, Palo Alto PAN-OS, FortiOS, Junos, Arista EOS. Not for planning the upgrade itself (use upgrade-plan).
02 资源文件 1
- 参考文档references/exposure-report.md942 B
03 SKILL.md 正文
Advisory exposure
You judge exposure and patch order. The CVE data comes from NVD by exact version (CPE), saved by code. Never name a CVE, advisory or fixed release from memory: a recalled list misses recent advisories and gets fixed versions wrong, and Security acts on it.
Step 1: Save the inventory
Make documents/<id>/ and save the inventory word for word as inputs/inventory.csv
(a hostname column, platform, version). Group hosts by platform and version: each
distinct pair is one lookup.
Step 2: Look up each platform and version
~/.damira/bin/damira-advisories --products # product keys
~/.damira/bin/damira-advisories ise "3.3 Patch 2" --save documents/<id>/evidence/ise-3.3p2.md
~/.damira/bin/damira-advisories ios_xe 17.9.4 --save documents/<id>/evidence/ios_xe-17.9.4.md
Without an NVD key each lookup takes about 15 s; run them one after another. Exit 2 means
NVD has no record for that product and version: that host goes under "Not covered", not
"none found". If a CVE needs more detail, damira search-vendor-docs "<advisory id>" --save documents/<id>/evidence/<advisory>.md fetches the vendor page.
Step 3: Write the report
Save documents/<id>/exposure.md with the sections in references/exposure-report.md:
summary, exposure by device (every host in the inventory), patch order, not covered.
For each exposed CVE give the show command that tells whether its feature is enabled.
Step 4: Check it
~/.damira/bin/damira-doc-check documents/<id>
It fails on a missing section, a host not covered, or an ID not in evidence/ and not
marked UNVERIFIED. Fix and re-run; a Stop hook runs it too.
Step 5: Present the result
Report the summary, the patch order and what is not covered. Do not publish or send it unless the engineer asks.
04 同仓库更多 Skills
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.
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).
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.
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.
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.
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.