Because it’s Microsoft and they have to compulsively rename things every few years.

They’re also one of the companies trying to destroy the NLRB.

There will 100% be a policy to disable it. Microsoft may shit on their retail users, but there’s no way they’d force it on their enterprise clients. It’s a security and compliance nightmare and they know it.

There’s a reason why every other browser maker has given up and adopted Chromium. It’s not easy to support a browser and rendering engine across half a dozen OSes while keeping it secure, performant and stable.

The biggest loser is Mozilla, who will lose about 80% of their revenue. If they enforce this, Firefox will pretty much be dead.

Google pays them 400 million. You really think they’re going to get anywhere close to that from donations?

I hate dark mode, but it’s because I have a pretty bad astigmatism. Dark mode makes all text look like several mirror images swimming around each other, whereas light mode is fine.

In the US, anything with “heritage” in its name is usually racist. The word became a dog whistle for white supremacists after the civil rights era.

That’s what most exploit-based hacks are. A developer makes a dumb mistake and then someone exploits it to do something they shouldn’t be able to do.

Microsoft has always been like this. They’re a giant company with a bunch of silos that act independently and often undermine what each other are trying to accomplish.

What? There’s lots of reasons to complain about Microsft, but their legacy support is not one of them. Almost every product they make gets 10 years of support + 3 more if you pay for it. In comparison, Postgres only does 5, MySQL is 8, and Mongo is 3.

iPads actually do support multiple users. They just hide the ability to turn it on behind complex IT management tools that your average user would never be able to figure out.

It’s mostly the responsibility of the client to build defense in depth. If is a straight shot from your Solarwinds server to your ADFS server, where the SAML signing keys are stored, that’s your fault, not Solarwinds or Microsoft. Well, I would still blame Solarwinds, because they were encouraging horribly insecure practices, like doing “agentless” monitoring using a highly privileged account.

In this case, yes, not letting a SAML assertion signed by the ADFS server authenticate to Azure reduces defense in depth. But if you’re at the point where your authentication servers have been compromised, you’re already so turbo-fucked that it’s very unlikely a wall like that would stop an attacker for long.

USB devices have a hard coded vendor identifier and product identifier built into them that are issued from a central authority. The ones I saw were easily identifiable as not legitimate mice.

Oof, that was painful to read as someone in cybersecurity. I respect ProPublica, but they have no idea what they’re talking about.

The Solarwinds hack was caused by Solarwinds being absolutely god awful at cybersecurity. The password to their update server was “solarwinds123”, which we know because they accidentally published it in a public Github repo. The company is a complete and utter clown show.

As for Golden SAML, almost nobody in cybersecurity would consider it a vulnerability. It’s just a fundamental part of how asymmetric cryptography works. HTTPS suffers from the same issue. If your private key gets stolen and used to forge signatures, the problem is you not properly protecting it, not the technology requiring you to keep it secret.

A more valid complaint is that Microsoft has been neglecting their on-prem software in favor of Azure. There are tons of security features that they’ve added to Azure that will probably never make their way to ADFS or Exchange.

I’ve been the one identifying the people who use jigglers. Usually it was a manager coming to us to look for a reason to fire a poor employee or a contractor trying to bill a suspiciously large number of hours for the work produced. If it was just poor performance, HR would make us do a PIP and waste 3 months on them. Violating security procedures and falsifying time sheets was an immediate termination. And for the contractors, you need evidence in order to refuse payment.

Btw, if you want to get away with it, don’t use a software or USB one. Get one that interfaces with a regular mouse. Modern cybersecurity software logs every process executed and device connected.

There is no BIOS anymore. It’s all UEFI, which is massively fatter and more complex. Being fat and complex, they have plenty of security vulnerabilities that need to be patched.

Problem with that is that it really only covers the keys sitting on a nightstand situation. You could still get your car stolen while you’re shopping or in a restaurant.

Might as well have a push button instead. Having it work from your pocket without interaction is what makes a fob different and should be a design requirement.

The only thing I can think of is having incredibly tight timing on a challenge/response. With ~10 nanosecond level precision, it’s not physically possible for em waves to travel more a few meters before the time is up.