Windows Power Essentials Tips & Tricks
July 26, 2017 2 Comments
If you have been following some of my recent posts you’ll know i have been talking about Office 365 and Exchange Online and how you can tweak the settings to better secure your mail.
One of the steps for that is to setup DKIM. For Office 365 this requires two CNAME records to be published in your public DNS.
The problem i was having when setting up a new client, was knowing what the CNAME should be set to.
April 28, 2017 5 Comments
I have seen a sharp rise in the number of spear phishing attempts my clients are subjected to. I’m sure this trend will continue. Of course our best line of defence when protecting our clients is user education. We can of course try and make things easier for them.
Our most recent example was quite lacklustre by comparison, they hadn’t even bothered to try and find a similar address, just some random Comcast account and setting the ‘From’ name to that of the Executive they were trying to impersonate.
I decided that to counter this we can tag the subject of any such email and then also generate an incident response within Office 365.
March 28, 2017 3 Comments
No doubt everyone reading this is familiar with spoofed email. Where an attacker crafts a message to appear as though it comes from a legitimate sender, in the hopes the recipient will reveal personal information or part with their hard earned cash.
With the rise in so called ‘spear phishing’, being able to effectively block spoofed email is no longer just desireable, it is critical.
Also bear in mind that whilst technologies like Sender ID and DKIM exist, they require both parties of an email to be using them for them to be effective.
You may think any domain you have moved to Office 365 recently is automatically protected by Exchange Online Protection however, like previous versions of Exchange, SenderID checking is disabled by default, as are advanced spam filtering and malware protection. Read more of this post
June 13, 2014 8 Comments
I have just completed a migration from On Premises Exchange 2007, to Exchange Online. Despite what i thought was a pretty well prepared migration, i was gotchad at least four times, the last time actually needed Microsoft Escalation Support, when in actual fact a slight change to documentation and me reading a littler clearer would have solved the four days troubleshooting we did.
SBS Technet Blog The SBS Diva Blog TechNet Forum
Title (Required) 