Question 700
At fictional Westmarch Digital, a software-security team is conducting a planned system modernization within the approved release and rollback constraints. The case observation is: A billing webhook handler accepts any correctly signed event even if the event ID has been processed repeatedly. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Authenticated messages can still be replayed; state transitions need idempotency and time bounds. Repeated valid webhook deliveries produce one durable business transition and an auditable duplicate outcome.
Incorrect Answers
This response concerns api gateway authentication mismatch. Here, a billing webhook handler accepts any correctly signed event even if the event ID has been processed repeatedly. The confirming evidence is: Repeated valid webhook deliveries produce one durable business transition and an auditable duplicate outcome.
Mutual tls identity mapping concerns a different operational mechanism. Authenticated messages can still be replayed; state transitions need idempotency and time bounds.
Focusing on cross-origin policy misconfiguration would leave this problem unresolved: A billing webhook handler accepts any correctly signed event even if the event ID has been processed repeatedly.