Cisco Secure Firewall Audit Skill

Common failure modes

• Source report has recommendations but no evidence lines
• Device versions are missing, so lifecycle severity must be capped
• Rules engine misses findings because the customer's wording differs from expected keywords
• Placeholder or template text is misread as active evidence

Purpose

This skill converts Cisco Secure Firewall health-check input files into branded HTML, Markdown, and JSON reports.

Input types

• .docx
• .md
• .txt
• .log
• .cfg
• .conf

Workflow

1. Read the source file from input/reports/.
2. Extract plain text and structural content.
3. Use references/grep-patterns.md to locate evidence.
4. Use references/audit-checklist.md to evaluate findings.
5. Use references/reference-values.md for target values and severity.
6. Use references/report-templates.md to build the output structure.
7. Generate:
   • HTML report
   • Markdown report
   • JSON findings file

Report rules

• Preserve exact evidence excerpts where possible.
• Do not include credentials or sensitive values.
• Keep output professional and customer-friendly.
• Show positive findings separately.
• Include methodology and disclaimer in every report.
• If evidence is incomplete, mark the item as unclear rather than guessing.

Output locations

• output/html/
• output/markdown/
• output/json/
• output/extracted/