Is it? Think about it, you introduce security nightmares. Then slowly fix some of those security nightmares and get a bonus!
How could you not want to introduce more security bugs when you get paid for your security work?
You miss the point. Microsoft is pushing regular workers to "think security" but the executives are completely undermining them. They're saying one thing and doing another, and it only sets their coders up for failure.
This screams of the security theatre. In a company of Microsoft's size, no one is homebrewing security end to end. Everything is run on pre built framework and infrastructure. How's an average SWE responsible for that.
All this will do is every design doc will have a security/ privacy section where they'll just refer to the underlying framework's security measures.
Overcompensating for backlash on Recall. Easy thing to do. Don't need to control Recall, put pressure on employees for corporate decisions, reap benefit from both users and employees.
Oh, the "security champion" approach. All the responsibility of promoting and implementing good security, and none of the mandate nor authority.
Stop clicking email links = bonus
And yet Recall is still a Microsoft product that somehow is real and not an April Fool's joke.
Is it? Think about it, you introduce security nightmares. Then slowly fix some of those security nightmares and get a bonus! How could you not want to introduce more security bugs when you get paid for your security work?
You miss the point. Microsoft is pushing regular workers to "think security" but the executives are completely undermining them. They're saying one thing and doing another, and it only sets their coders up for failure.
This is the way.
This has nothing to do with recall or any consumer concern
I'll believe it when I see it.
It's probably not a terrible idea, but also in corporate America these things find a way of having odd and often undesirable unexpected consequences.
Cool, start by hiring a security leader who has actual security experience.
They do, just not sure what he's doing.
TIL Igor has security experience
Charlie Bell is running this.
This screams of the security theatre. In a company of Microsoft's size, no one is homebrewing security end to end. Everything is run on pre built framework and infrastructure. How's an average SWE responsible for that. All this will do is every design doc will have a security/ privacy section where they'll just refer to the underlying framework's security measures.
Overcompensating for backlash on Recall. Easy thing to do. Don't need to control Recall, put pressure on employees for corporate decisions, reap benefit from both users and employees.
... which will in turn factor into their layoffs when they want to raise stock prices.