156 karma · joined November 23, 2020
The activity reported is associated with a customer account within the Microsoft Azure service. Microsoft Azure provides a cloud computing platform in which customers can deploy their own software applications. Customers, not Microsoft, control what applications are deployed on their account.
So why are even we using DKIM at all if bad actors can abuse an open cloud TOS.
Sounds spammy, but this is industry norm from personal experience on Ironport and Exchange. Downside is the spam imitations of this that are likely quite successful at phishing creds from corporate users.
Do you want your transactions to go to a "data analytics service provider" or "fraud prevention services providers" or "identity verification service providers"
A lot of crap can get by with the term "with your consent" AKA just clicking OK to get to the next screen.
You and your team must piecemeal the long term fixes if you want to make any progress towards understanding, scalability and reliability.
Given CPU power of the day PCM should be easier to decode, just the excessive bandwidth (for the time) would be the expensive part to deal with.
There are different kinds of floss and they all feel different, find whatever works for you.
Flossing only hurts the first couple times, then scar tissue builds up and you barely feel it anymore.
#1. Living Asset Inventory (constantly updated automatically)
#2. Intelligence on these Assets (can be mdm, but at least reporting of sysinfo, os update version, security version)
#3. Automatic patching of both security software and os version.
#4. Centralized identity management (Azure AD, other SAML options) with security intelligence builtin.
Slack also had SAML, near feature complete web interface, and an easy to swallow onramp cost in 2017.