Question 530
Which test or documented result best shows that the underlying issue was properly addressed? An internal build runner loads untrusted serialized objects from a developer-submitted artifact with executable type handlers enabled.
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: An internal build runner loads untrusted serialized objects from a developer-submitted artifact with executable type handlers enabled. It demonstrates that the proposed response, use safe data formats and strict allowed-type validation in the import path., produces the measurable result a crafted object cannot execute unintended code during a controlled build. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
The observed “A crafted destination override cannot redirect another user's reset token” validates the separate control “Verify recovery destination ownership through authoritative account records and controlled out-of-band confirmation” under “A password-reset endpoint trusts the caller's requested username and issues reset tokens to an attacker-controlled address”. The present decision calls for the different result “A crafted object cannot execute unintended code during a controlled build” from “Use safe data formats and strict allowed-type validation in the import path”.
“Traversal tests cannot read configuration files outside the approved root” would verify “Canonicalize paths and constrain server file access to an authorized directory after validation” for the situation “A retail service receives requests whose raw path components traverse outside the intended static file directory”. Here the required evidence is “A crafted object cannot execute unintended code during a controlled build” after “Use safe data formats and strict allowed-type validation in the import path”; the alternative observation does not test that control.
Observation “A crafted malformed login produces an ingestion error and cannot be mistaken for an authenticated success.” would be useful for “A developer uses a wildcard parser that converts missing security log fields to zero values, making failed imports look like successful logins”, but it does not prove that the response to “An internal build runner loads untrusted serialized objects from a developer-submitted artifact with executable type handlers enabled” achieved the relevant outcome, a crafted object cannot execute unintended code during a controlled build.