4 ms·
>How does this article reconcile with the existing disabled by default practice? AFAIK it's usually combined with some sort of social engineering attack to get
by gruez 5y ago
>How does this article reconcile with the existing disabled by default practice?
AFAIK it's usually combined with some sort of social engineering attack to get the user to bypass the warning. eg. "this document is password protected by Adobe Protect™ to view document, click enable macros".
- caminante 5y agoAfter re-reading, it sounds like there's an additional "are you sure" flag if the file came from outside your organization. My point is that macros are already disabled by default. If you're going to get phished or engineered, then adding more "are you sure" prompts is of questionable value, without trying to sound overly cynical about InfoSec. Bottom line: if the "feature" is not explained in a straight-forward way to a tech-savvy crowd like HN, then I have a lot of questions about its efficacy.