Question 290
After the team performs “Reassess attack prerequisites using observed credential compromise and actual API accessibility.” for this situation — A high score affects an API endpoint protected by strong authentication but there is evidence of stolen customer tokens. — which finding BEST proves that the response worked?
Explanation
Correct Answer
“The new priority reflects a plausible authenticated attack path and documented customer impact.” is direct acceptance evidence for the response “Reassess attack prerequisites using observed credential compromise and actual API accessibility.”. It resolves the uncertainty introduced by “A high score affects an API endpoint protected by strong authentication but there is evidence of stolen customer tokens.” using an observable test or record.
Incorrect Answers
It would provide evidence about checking deployed build lineage before treating an absent library as a vulnerable component, but would not confirm considering stolen-token evidence despite an API's nominal strong authentication boundary.
The measured result “The response queue records successful exploitation and ownership for rapid containment.” does not match the outcome of “Reassess attack prerequisites using observed credential compromise and actual API accessibility.” for “A high score affects an API endpoint protected by strong authentication but there is evidence of stolen customer tokens.” and instead belongs to the alternate problem “A CVSS 9.8 finding sits on an internal system, but logs show successful exploitation of a CVSS 7.5 issue on an exposed proxy.”.
Even if “Reprioritization cites the observed tactic, affected assets, and verified exposure path.” is correctly observed in “A vendor states a flaw is theoretical, but recent incident telemetry shows the same exploit technique attempted against the environment.”, it would not demonstrate the required “The new priority reflects a plausible authenticated attack path and documented customer impact.” for the present response to “A high score affects an API endpoint protected by strong authentication but there is evidence of stolen customer tokens.”.