“Whaling” emerges as cybersecurity threat
cio.com
cio.com
Haha, yes that's true: we still do not have the universal fraud detector and stupidity prevention algorithm. Seriously, this is not a system security problem. If you have high-level employees in the finance dept. of your company that will initiate a wire transfer on the basis of an unsigned, unencrypted email from an un-trusted domain, that is a policy/standards/personnel issue.
i wonder what security policies and practices were followed by one well-known Secretary of State Department of a largest nuclear superpower ...
Government officials commonly have 2 computers and 2 phones, one classified and one unclassified.
Hilary is alleged to have handled a little bit of classified information through her unclassified system, but it's not like she was routinely moving state secrets through civilian email.
This falls under business basics.
Seeing as we use google apps for our email, it would be really nice if google could warn in their interface that this email may have the CFO's address, but it did not come from internal mail...
The way to tell Google apps "don't accept outside forged emails from my domain" is a DMARC policy, combined with the pre-reqs for that. Google apps happily puts forged emails (from your own domain) into your inbox if you don't.
>>DMARC is a message to other entities about what you want them to do in case DKIM/SPF fails
Yes, but it also drives what your hosted Gapps/Gmail instance does with incoming forged email for your own domain.
Google could provide a toggle or functionality to say what to do with failed DKIM and/or SPF more generally, for all domains...but they don't. I can tell you for sure that messages with failures for both regularly land in the inbox within my Google Apps Gmail.
https://serverfault.com/questions/321109/how-to-prevent-remo...