At a SaaS company, support wants proof of what was in a response body, but the security team has only metadata and session data for that exchange. What is missing?
Select an answer to reveal the explanation.
Short Explanation
The weight of a parcel does not show you the letter inside. You still do not have the response body, because metadata and session data do not store that content. The trap is asking for another byte-count export, a higher score, or a new asset tag.
Full Explanation
Metadata describes an object, and session data describes the conversation around it. Neither one is the response body that support asked to see. What is missing is A full capture of the unencrypted response body, or another record of that content. A content record, such as a full packet capture taken while the body was readable, or an equivalent store of that body, is what can prove the bytes support wants. Another export of byte counts for the same sessions the team already holds in storage repeats volume information and still has no body. A higher CVSS score on the finding, still with no response body attached changes a rating and does not add content. A new asset tag placed on the server that generated the response for support changes an inventory label and does not show what the server sent. Exam caveat: do not treat a size, a session byte count, or a severity score as the body of the response. Operational check: ask whether any sensor stored the clear response before you promise support a copy of that body. A rating or a size cannot stand in for the missing content.