Question 300
Original unofficial Palo Alto Networks NetSec-Architect scenario: A SOC dashboard assumes no threat events means the environment is safe, but the HTTP log receiver has been unavailable since midnight. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A SOC dashboard assumes no threat events means the environment is safe, but the HTTP log receiver has been unavailable since midnight. Governing principle: Absence of events is ambiguous without a positive signal that telemetry is flowing. The most defensible design response is: Instrument delivery success, ingestion lag and explicit heartbeat monitoring independently of threat-event counts. Validation: Stopping the receiver generates a transport-health alert even though no security event arrives. Sustained assurance: Test connector failure and recovery in monitoring acceptance exercises
Incorrect Answers
“Capacity-test forwarding endpoints during SOC integration reviews.” concerns the separate design topic: recommend resilient strata logging service integrations and forwarding protocols. It would not fix the described weakness: a SOC dashboard assumes no threat events means the environment is safe, but the HTTP log receiver has been unavailable since midnight. Absence of events is ambiguous without a positive signal that telemetry is flowing.
This alternative is linked to the architecture category: architect panorama high availability and resilient log collection. The actual problem is that a SOC dashboard assumes no threat events means the environment is safe, but the HTTP log receiver has been unavailable since midnight; the controlling distinction is: absence of events is ambiguous without a positive signal that telemetry is flowing.
The proposed design “Recertify data minimization for each product integration.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that a SOC dashboard assumes no threat events means the environment is safe, but the HTTP log receiver has been unavailable since midnight. Absence of events is ambiguous without a positive signal that telemetry is flowing.