Knock it off, Microsoft. You’re not my buddy, you’re an OS. Your job is to sit down, shut up, and run the programs I choose. That’s it.
If I find a function that’s useful for more than a week, I might make a batch file for it. Until then, you’re spare code.
Or the XCOM games.
SIP providers usually sell numbers in contiguous series for businesses. For example, if your company buys a block of 50 numbers, the SIP provider then allocates XXX-5100 to XXX-5150.
But since you’re keeping this strictly internal, you don’t have to worry about that.
Step 3: unfuck the SIP settings, then email both HR and their supervisor to throw them under the bus. Also covers your ass for step 4.
Step 4: Route the manager’s calls to a disconnected number. When they come knocking about their phone not working, tell them, “No, you should be able to dial out, unless someone changed the SIP trunk settings and didn’t tell me.”
Assuming you already have the IP phones, you need two things. A PBX server (for the VoIP stuff), and a SIP trunk with a block of external phone numbers.
Start with the PBX server software, there’s several free/open-source implementations. Once you’re comfortable with it and have internal calling good to go, then you can spend on the SIP trunk and number blocks.
Having managed an exchange instance for my old job, I can safely say that DKIM and DMARC are just some extra DNS entries for out-of-band verification. They can be boiled down to a pair of checkboxes on a compliance sheet.
I can also say that most of the companies we got emails from didn’t have DKIM, and even fewer had DMARC. Or worse, they had DMARC set to p=ignore. Which is honestly even more infuriating.
Meanwhile, Microsoft’s Exchange platform blatantly ignores DMARC failures for senders and relays on its “Good PTR list”. Bit of a glaringly large hole for spam to pass through.
Sounds more like poor self-checkout design.
All the stores I’ve been to with self-checkout require placing your just scanned item into the bag on a scale. If the weight change doesn’t match what it expects, it locks up and requires a store employee to check and clear it.
Downside is, it has problems with very light items.
748 million? I’ll be surprised if they get more than 748 thousand.
It’s only minor if the data points in this breach are used by themselves.
Once you aggregate this with other data breaches, you could end up with a much bigger capability to target anyone in this breach.