Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Our help docs have a new home! Looking for the old help center? Visit docs.getthread.com.
Interrogate a client’s Cisco ASA firewall through the Liongard Cisco ASA inspector — software version, interfaces, access lists/NAT, VPN (IPsec/AnyConnect) config, admin access. Use for “what’s their ASA config?”, ACL/exposure review during triage, or version-currency checks.
Liongard
Role: Technician
Outcome: Risk & Compliance, Faster Resolution & Response
When to use: “What access lists / NAT rules are configured at <client>?”, a connectivity or exposure ticket needing the ACL/NAT picture, “what ASA version are they on?”, a VPN (IPsec site-to-site / AnyConnect) troubleshooting read, or “did an ACL or NAT entry change?”.
Run it: on one client — name the client and the ASA question.
Read Cisco ASA firewall config for CLIENT_NAME from the Liongard Cisco ASA inspector. Read-only — ASA changes go through the partner's change process.
1. Resolve the client's environment, then find the Cisco ASA inspector and confirm it ran recently — carry "as of <timestamp>." A client may have multiple ASAs — enumerate them.
2. Read the values from its latest dataprint for the angle you need, verifying every field angle against the live dataprint (schemas vary by inspector version):
- ACLs: access-list entries with action, source/dest, service — flag permit any any.
- NAT: static/inbound NAT with external port to internal host — flag exposure of RDP/3389, SMB/445.
- Version: ASA software version — report verbatim and recommend verifying against current advisories, not memory.
- VPN: IPsec site-to-site peers and AnyConnect config.
- Admins: local admin accounts and access methods (SSH/ASDM).
3. "What changed?" → check what changed on the ASA: ACL adds/edits, NAT changes, version upgrades, admin changes — ordered against the incident window (time-adjacency, not proven cause).
4. Sanity-check surprising zeros (zero ACL entries) — usually a wrong field angle or partial inspection; re-probe broadly. Never paste PSKs, VPN pre-shared keys, or credentials into notes — reference "PSK on file in <doc platform>." Exposure findings are risk inputs, not confirmed breaches — "external RDP NAT present, verify need" phrasing.
5. Output: a compact table, source + data age line, flags (permit-any ACLs, risky inbound NAT, outdated version, unexpected admins). Offer to leave a plain-text note. Degradation: no ASA inspector → documentation → ticket history → "verify on appliance"; also check the generic Cisco network inspector.
Was this page helpful?