Secret patterns by vendor family
Use these as review hints, not as an exhaustive parser. Keyword matches are case-insensitive unless noted. When in doubt, redact the value and keep the keyword and object name.
Placeholder style: REDACTED_<KIND>_<NN> (for example REDACTED_PSK_01). Reuse the same placeholder if the same object is referenced more than once, but never copy the original value into the map.
All vendors
- PEM or PKCS8 key blocks between
-----BEGIN and -----END where the type contains PRIVATE KEY, RSA PRIVATE KEY, EC PRIVATE KEY, or ENCRYPTED PRIVATE KEY.
- Lines or stanzas containing
password, secret, pre-shared-key, preshared, community, auth-key, privacy, api-key, token, credential, or private-key, unless the remainder is clearly a feature name with no value.
- SNMP community strings and SNMPv3 auth/priv keys.
- Comments (
!, #, /* */) that repeat a password or key.
Cisco ASA or FMC (managed FTD) exports
Common keywords (values go after the keyword; redact the value, keep the command):
enable password, enable secret
passwd, username ... password, username ... secret
aaa-server ... key, ldap-login-password, socks-server ...
snmp-server community, snmp-server user auth/priv values
crypto isakmp key, tunnel-group ... ikev1 pre-shared-key, ikev2 local-authentication pre-shared-key
ospf authentication-key, ospf message-digest-key, key-string under key chains
key under tacacs-server, radius-server
vpnclient and Easy VPN secrets
Hashed passwords in ASA and FMC exports are still sensitive. Redact them.
Palo Alto Networks PAN-OS
phash values on local users
pre-shared-key under IKE gateways
- XML
<private-key>, <preshared-key>, <phash> elements
api-key or key material in exported admin or panorama config
- Authentication profiles that embed bind passwords or RADIUS/TACACS secrets
community under SNMP
PAN-OS set-format and XML exports can both carry these. Search both styles.
Fortinet FortiGate
set password, set passwd, and ENC or SH2 encoded values after password-like keywords
set private-key, set certificate, and set csr blocks that include key material
set psksecret, set ppk-secret, set secret, set passphrase
set auth-password, set auth-pwd (SNMPv3 and admin)
set community under SNMP
- RADIUS/TACACS/LDAP
set secret / set password
set api-user keys and REST API tokens if present
FortiGate ENC strings are not safe to share. Redact them.
Juniper Junos (routers and switches)
$9$, $8$, $1$, and similar secret strings after encrypted-password, secret, or authentication-key. $9$ strings are reversible obfuscation, not hashes. Always redact.
pre-shared-key, preshared-key, authentication-key, md5, key-chain
community under SNMP
radius-server / tacplus-server secrets
load-key-file references and any inline private key text
show configuration | display set and curly-brace format both need a pass.
Cisco IOS / IOS-XE and similar switch or router configs
enable secret, enable password, username ... secret
key-string under key chain
snmp-server community
- BGP, OSPF, EIGRP, and RIP authentication keys
tacacs-server key, radius-server key, aaa host keys
- Wireless or 802.1X secrets if present
Aruba / AOS-CX (when present)
- User passwords and
password lines
- RADIUS/TACACS secrets
- SNMP communities
- Key chains and OSPF/BGP authentication
Optional identity redaction
If the user asked to anonymize addresses or names:
- IPv4 and IPv6 literals, including those inside object definitions and NAT pools.
- Keep replacements consistent so two references to the same address become the same replacement.
- If the file will be converted or validated, keep addresses, or replace them consistently with documentation prefixes (
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, 2001:db8::/32). Do not use named tokens such as INSIDE_NET_01 in those files.
- Named placeholders are for human-readable sharing only.
- Hostnames, serial numbers, and site-specific comments.
Residual-risk hints
Flag these if they remain after the pass:
- Long base64 or hex blobs next to crypto, VPN, or certificate keywords.
- External files the config points at (
key-file, certificate, license) that were not in the bundle.
- Screenshots, packet captures, or log extracts bundled with the config.