Question 720
A technical review is underway: A partner sends a spreadsheet containing an embedded malicious macro and ordinary URL scanning does not detect the file risk. Which risk should be documented as part of this change?
Explanation
Correct Answer
Safe Attachments does not guarantee detection of every novel payload and is not identical to Safe Links. The case concerns detonate suspicious email attachments: A partner sends a spreadsheet containing an embedded malicious macro and ordinary URL scanning does not detect the file risk. Attachment-content threat analysis protects a different mail surface than URL-click inspection. This answers the condition that limits a broader guarantee because it addresses the explicit constraint. Even after the main change, safe Attachments does not guarantee detection of every novel payload and is not identical to Safe Links. Review the concrete evidence before treating the control as complete.
Incorrect Answers
URL reputation and detonation mechanisms address different risks than attachment scanning. The reason this does not settle the present case is the actual condition: Safe Attachments evaluates supported attachments using detonation and threat protection workflows.
Message-specific threat analysis should use authenticated technical fields and protection verdicts. The records needed for this specific case concern: Inspect attachment threat verdicts, delivery action, and Safe Attachments policy scope.
Investigation automation and execution approval are different stages of threat-response governance. The appropriate acceptance check is: A controlled malicious attachment is blocked or quarantined before unsafe consumption.