Ensure DNS sinkholing is configured on all anti-spyware profiles in use

So wird geprüft

Prüfmethode: Konfigurationsmuster

Muster

(?m)^set (?:shared |vsys \S+ |device-group \S+ |template \S+ config (?:shared |vsys \S+ )?)?profiles spyware (?:"[^"\n]*"|\S+) botnet-domains lists default-paloalto-dns action sinkhole[ \t]*$

So wird behoben

Behebungsmethode: Anleitung oder Infrastruktur-Patch

configure set profiles spyware <profile> botnet-domains lists default-paloalto-dns action sinkhole set profiles spyware <profile> botnet-domains sinkhole ipv4-address sinkhole.paloaltonetworks.com set profiles spyware <profile> botnet-domains sinkhole ipv6-address ::1 commit # CIS guidance: Navigate to Objects > Security Profiles > Anti-Spyware. Within the each anti-spyware profile, under its DNS Policies tab, set the Signature Source List: default-paloalto-dns should have as its Policy Action set to sinkhole If licensed, the DNS Security should have as its Policy Action set to sinkhole Verify the 'Sinkhole IPv4' IP address is correct. This should be set to sinkhole.paloaltnetworks.com, or if an internal host is set then that host IP or FQDN should be in that field Verify the 'Sinkhole IPv6' IP address is correct. This should be set to IPv6 Loopback IP (::1), or if an internal DNS Sinkhole host is set then that host IP or FQDN should be in that field Navigate to Policies > Security Policies For each outbound security Policy, in the Actions tab, set the Anti-Spyware setting to include the Spyware Profile created, either explicitly or as a Group Profile

Diesen Host prüfen

Führen Sie dies auf einem Rechner aus, den Sie prüfen dürfen. Der Scan ist schreibgeschützt.

tmaegis scan --target paloalto