CYBERSECURITY-PRACTITIONER practice question 7 of 30
Which security component can detect command-and-control traffic sent from multiple endpoints within a corporate data center?
Full set: 225 questionsA Next-Generation Firewall (NGFW) is specifically designed to detect and block modern, sophisticated threats. It provides application-layer visibility (Layer 7) using technologies like App-ID to identify traffic regardless of the port used. Crucially, its threat prevention capabilities, particularly Anti-Spyware profiles, use signatures to identify and block command-and-control (C2) traffic patterns generated by malware on compromised endpoints. Placed at the data center's egress point, an NGFW has the centralized visibility required to inspect traffic from multiple internal endpoints communicating with external C2 servers.
A. Personal endpoint firewall: This component operates on a single host and lacks the centralized network visibility to detect C2 traffic originating from multiple endpoints across the data center.
B. Port-based firewall: This legacy firewall operates at Layers 3 and 4, making decisions based on IP addresses and ports. It cannot inspect application payloads and is easily bypassed by C2 traffic masquerading on common ports like 80 or 443.
D. Stateless firewall: This is the most basic type of firewall, inspecting packets individually without tracking connection states. It is incapable of understanding the context required to identify sophisticated C2 communication channels. ---
1. Palo Alto Networks Documentation
"What Is a Next-Generation Firewall (NGFW)?". Palo Alto Networks. Accessed 2023.
Reference Detail: The document states
"A next-generation firewall (NGFW) [...] provides visibility into and control over applications
users
and content... NGFWs should include [...] integrated intrusion prevention (IPS)
and application intelligence and control. [...] This allows them to block modern threats such as advanced malware and application-layer attacks." This directly supports the NGFW's ability to inspect content for threats like C2.
2. Palo Alto Networks Documentation
"Anti-Spyware". TechDocs
PAN-OS® Administrator's Guide.
Reference Detail: In the "Anti-Spyware" section
it is explicitly stated that the security profile "identifies compromised hosts on your network when spyware attempts to communicate with its command-and-control (C2) server." This confirms the NGFW's specific mechanism for detecting C2 traffic.
3. Palo Alto Networks
"The Cyber-Attack Lifecycle". White Paper.
Reference Detail: This paper outlines the stages of a cyberattack. Stage 6 is "Command and Control (C2)". The paper details how Palo Alto Networks NGFW features
such as Anti-Spyware and URL Filtering
are used to "Block outbound C2 communication" by identifying malicious patterns and destinations
thus breaking the lifecycle.
4. Palo Alto Networks Cybersecurity Academy
"Cybersecurity Foundation (EDU-110)". Courseware Module 4: The Cyber-Attack Lifecycle.
Reference Detail: This educational module explains that during the Command and Control phase
an attacker establishes a channel for communication. The courseware specifies that a Palo Alto Networks NGFW uses Anti-Spyware profiles to detect and block these malicious outbound connections from compromised hosts within the network.
Keep practicing
Take the free CYBERSECURITY-PRACTITIONER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other CYBERSECURITY-PRACTITIONER practice questions
- Question 1What is an operation of an Attack Surface Management (ASM) platform?
- Question 3How can local systems eliminate vulnerabilities?
- Question 4With regard to cloud-native security in layers, what is the correct order of the four C's…
- Question 5Identify a weakness of a perimeter-based network security strategy to protect an organiza…
- Question 6How does Cortex XSOAR Threat Intelligence Management (TIM) provide relevant threat data t…
- Question 8A doctor receives an email about her upcoming holiday in France. When she clicks the URL …
