Question 290
Original unofficial Palo Alto Networks NetSec-Architect scenario: A managed detection provider accepts HTTP event deliveries but retries create apparent duplicate incidents without event identifiers. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A managed detection provider accepts HTTP event deliveries but retries create apparent duplicate incidents without event identifiers. Governing principle: At-least-once transport behavior can repeat deliveries even when the security event is unique. The most defensible design response is: Design idempotent correlation using stable event IDs and the provider’s supported HTTP integration behavior. Validation: One injected event with a simulated retry produces one logical case while preserving delivery evidence. Sustained assurance: Reconcile forwarded counts and duplicated-event rates after connector changes
Incorrect Answers
The suggested “A packet capture shows protected log transport and the SIEM receives an attributed test event.” tests a different architectural concern: recommend resilient strata logging service integrations and forwarding protocols. Here, a managed detection provider accepts HTTP event deliveries but retries create apparent duplicate incidents without event identifiers. At-least-once transport behavior can repeat deliveries even when the security event is unique.
The proposed design “Test users’ approved cloud-group memberships are represented without creating a second directory.” addresses this related architecture topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual security gap is that a managed detection provider accepts HTTP event deliveries but retries create apparent duplicate incidents without event identifiers. At-least-once transport behavior can repeat deliveries even when the security event is unique.
“A valid employee is associated with the correct principal while an offboarded account fails portal access.” concerns the separate design topic: recommend user identification and authentication methods including saml. It would not fix the described weakness: a managed detection provider accepts HTTP event deliveries but retries create apparent duplicate incidents without event identifiers. At-least-once transport behavior can repeat deliveries even when the security event is unique.