this post was submitted on 30 May 2024
134 points (100.0% liked)

Asklemmy

1462 readers
89 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

So my company decided to migrate office suite and email etc to Microsoft365. Whatever. But for 2FA login they decided to disable the option to choose "any authenticator" and force Microsoft Authenticator on the (private) phones of both employees and volunteers. Is there any valid reason why they would do this, like it's demonstrably safer? Or is this a battle I can pick to shield myself a little from MS?

top 50 comments
sorted by: hot top controversial new old
[–] xavier666@lemm.ee 32 points 9 months ago (1 children)

Not a good solution but a decent one. Create a work profile on your phone, using Shelter (Fdroid, open source), and put all your work apps on that. Your data and processes are isolated and you can turn off all your work apps with a single tap. It's like a secondary virtual phone.

[–] jaschen@lemm.ee 4 points 9 months ago (3 children)

Wow thanks friend! Does the 2FA work in this silo?

[–] Max_P@lemmy.max-p.me 9 points 9 months ago (1 children)

Just like anywhere else. All it does is sandbox work apps from personal apps so they don't talk to eachother (not even screenshots!)

[–] jaschen@lemm.ee 3 points 9 months ago

This is awesome!

load more comments (2 replies)
[–] DmMacniel@feddit.de 27 points 9 months ago (1 children)

Demand hardware tokens for authentication.

[–] xavier666@lemm.ee 3 points 9 months ago (1 children)

Do hardware tokens support Linux nowadays?

load more comments (1 replies)
[–] Nighed@sffa.community 20 points 9 months ago (2 children)

The ms authenticator works in 'reverse' in that you type the code on the screen into the phone. I assume this is preferable to corporate as you can't be social engineered into giving out a 2fa token. It also has a "no this wasn't me" button to allow you to (I assume) notify IT if you are getting requests that are not you.

I don't believe that the authenticator app gives them access to anything on your phone? (Happy to learn here) And I think android lets you make some kind of business partition if you feel the need to?

[–] Max_P@lemmy.max-p.me 9 points 9 months ago (1 children)

And the authenticator is configurable and they can enforce some device security like not rooted, bootloader locked, storage encryption is on through the Intune work profile. If you work on a bank, you don't want the 2FA to even live on a device where the user gives root access to random apps that could extract the keys (although at this point come on you can probably afford Yubikeys).

As a user, not a fan, but as an IT department it makes complete sense.

load more comments (1 replies)
[–] englislanguage@lemmy.sdf.org 2 points 9 months ago

If it is just TOTP, you can use any other TOTP app, such as Aegis or FreeOTP+.

And no, Microsoft cannot be trusted on not doing anything bad. The app is full of trackers and has an excessive list of permissions it "requires".

For comparison, Aegis and FreeOTP+ work without trackers and way less permissions.

Microsoft has a long track record of leaks. Just naming the 2 most prominent:

  1. Microsoft Edge leaks every single URL to Microsoft servers (source)
  2. There are lots of reports that Microsoft had their general key stolen and not even notify it for months. It is unclear who had acces to that key. This is putting anyone at risk who uses any Microsoft product. (See for example here)
[–] neidu2@feddit.nl 19 points 9 months ago* (last edited 9 months ago) (3 children)

Can you claim that you don't have a smartphone? Then they'd either have to provide an alternative authentication method, or provide you with a phone.

I've been part of the Microsoft Bad crowd for well over 25 years now, but there are a few things that I will concede that MS has done well. Authenticator is one of them. I haven't looked much into the privacy aspect of it, though.

[–] LodeMike@lemmy.today 9 points 9 months ago

Don't do that. Just say they will provide you with an authenticator paid for by them.

[–] BobGnarley@lemm.ee 9 points 9 months ago

If it has Microsoft's name on it, the privacy implications are horrendous. Guaranteed.

load more comments (1 replies)
[–] Dirk@lemmy.ml 14 points 9 months ago

If they want you to use a specific application they need to provide you with everything that is needed for you to run said application.

[–] ziby0405@lemmy.ml 14 points 9 months ago (1 children)

≥ and force Microsoft Authenticator on the (private) phones of both employees and volunteers.

Refuse to use the service until they provide you with a work appointed phone. Volunteers admitedly have a more difficult time with that but as someone else said you can indeed do text/call options.

[–] smileyhead@discuss.tchncs.de 3 points 9 months ago (2 children)

a work appointed phone

With all the tracking that comes with it.

[–] ShellMonkey@lemmy.socdojo.com 4 points 9 months ago

Not much of a privacy risk if it where used for a dedicated purpose and just left off in a drawer otherwise though. My employers pushed the notion of MS authenticator, but left the options to use regular TOTP available, just had to look a bit to find them. Even if they absolutely forced corp software though, a cheap wifi-only setup device is a viable option.

load more comments (1 replies)
[–] Rikj000@discuss.tchncs.de 13 points 9 months ago (2 children)

You can use Aegis and/or Yubico Authenticator instead, that's what I do.

[–] Nighed@sffa.community 16 points 9 months ago

They said that the option to use other authenticators were disabled by their company

[–] Fleppensteijn@feddit.nl 7 points 9 months ago (1 children)

In my company at least, Aegis works for the first few logins, but it will keep nagging you have to switch to Microsoft's authenticator and you're locked out after a while.

load more comments (1 replies)
[–] masterspace@lemmy.ca 12 points 9 months ago (1 children)

You're wasting your life trying to fight battles you don't even understand.

[–] Cataphract@lemmy.ml 3 points 9 months ago

Is there any valid reason why they would do this, like it’s demonstrably safer? Or is this a battle I can pick to shield myself a little from MS?

Thanks for the input?

[–] federalreverse@feddit.de 10 points 9 months ago (2 children)

Is your company mandating Push Authentication or are you entering 6-digit codes?

If it's the former, MS Authenticator is the only option.

If it's the latter, you can use any TOTP app you like, e.g. Aegis.

[–] RecallMadness@lemmy.nz 4 points 9 months ago

Afaik, Microsoft’s OTP implementation is proprietary and not TOTP.

But also, my understanding is you can select which MFA schemes you can use, and allow SMS, MS MFA, and TOTP.

Source: employer used to allow sms, locked it down, and totp apps can’t parse the MS authenticator QR codes.

load more comments (1 replies)
[–] NostraDavid@programming.dev 9 points 9 months ago (1 children)

Just ask whether they can provide a phone as well.

load more comments (1 replies)
[–] speaker_hat@lemmy.one 6 points 9 months ago (5 children)

In my case they didn't disable the option to use any authenticator for 2FA.

So I just use another one.

I don't see why forcing MS Authenticator will be better than any other authenticator.

The person who forces it is for sure not a security expert.

It will be easier to hackers to hack 2FA when they know what the authenticator app is, versus hundreds of different authenticator clients.

[–] greentreerainfire@kbin.social 3 points 9 months ago

It will be easier to hackers to hack 2FA when they know what the authenticator app is, versus hundreds of different authenticator clients.

Security through obscurity is not security.

Additionally, any method that generates a code locally that needs to match the server will not be secure if you can extract the key used locally. Yes you can argue that more users makes a juicier target, but I’d argue that Microsoft has the resources spend reducing the chance of an exploit and the resources to fix it fairly quickly. Much more so than any brand new team.

The default authentication option for the company I work for is that a code is displayed in the screen of the device I’m logging into AND a push notification is sent to the Authenticator app, the app then prompts me to enter the code from authenticating device. To break that you’d need the username, password, a clone of the phone/device used to authenticate (or the original), and the user’s PIN for that device (MS Authenticator requires this to complete the authentication.)

Yes MS Authentication services do sometimes go down, and yea it can impact my ability to work

I am by no means a MS fanatic, but I’d trust them for mission critical authentication over something like Authy.

load more comments (4 replies)
[–] Honytawk@lemmy.zip 5 points 9 months ago

You can just use FreeOTP

My company has the same policy

[–] Scary_le_Poo 5 points 9 months ago (1 children)

Grab the shelter app from f Droid, add the Play store in shelter, move over to the work side Play store and install the authenticator.

Pause your work apps except for when you need to use the authenticator.

Prosper???

load more comments (1 replies)
[–] wuphysics87@lemmy.ml 5 points 9 months ago

Declare yourself a member of The Church of Emacs and claim your religious rights are being violated.

[–] Appoxo@lemmy.dbzer0.com 4 points 9 months ago

I managed to get around the MS auth app and am using aegis right now.

[–] Tinkerer@lemmy.ca 4 points 9 months ago

I don't really get the rub here, JM all for separating work devices and personal devices but the 2fa apps don't leak any info and the company can't "do" anything to your phone remotely. The apps work in air plane mode. I also want to bet more than half the users that complain about this use the companies free WiFi.

Get a flip phone and say you can't install it, however SMS 2fa is very insecure.

[–] mp3@lemmy.ca 4 points 9 months ago* (last edited 9 months ago)

You have the right not to use your personal hardware for work, and the employer must provide the necessary equipment to accomplish your job.

Ask if you could get a hardware token (ie: Yubikey Security Key) instead of using Microsoft Authenticator to fulfill the security requirements. It's low cost and doesn't require a subscription unlike a cellphone plan.

[–] nexussapphire@lemm.ee 4 points 9 months ago

Get a used /cheap phone or tablet, only turn it on or enable wifi when you need the app. Don't use it for anything else. I think that covers all the bases.

[–] MetalMartin@lemmy.myserv.one 4 points 9 months ago

I won't allow any MS stuff on any of my devices.

[–] Nomecks@lemmy.ca 4 points 9 months ago

If your company is enforcing geographic location as a security qualifier then MS Authenticator can poll your device. Also you can use push authentication with the MS suite.

[–] sunbeam60@lemmy.one 3 points 9 months ago (6 children)

What is your concern about installing MS Authenticator.

I mean I can understand the principle of being forced to install anything on your phone.

But just stepping into the practical for a second: What do you worry will happen by installing this app to your phone?

[–] Fleppensteijn@feddit.nl 5 points 9 months ago (1 children)

200 MB of wasted personal disk space just so you can log in to a work account

[–] sunbeam60@lemmy.one 4 points 9 months ago (1 children)

Ok, but most workplaces require some form of apps installed for access, shared documents etc.

How many would install Figma, Office, Expensify, Jira, Confluence or a whole other raft of work apps if it wasn’t for work?

I mean, sure, it’s annoying but is MS Authenticator really the hill people want to die on?

[–] Fleppensteijn@feddit.nl 4 points 9 months ago

Yeah but you install that stuff on your work computer. If my job requires me to use an authenticator on a non-work phone, then at least let me use the one I'm already using.

[–] Martin@lemmy.ml 4 points 9 months ago (3 children)

I'm not concerned per se and I definitely applaud the MFA requirement. I mean I hate MS and don't like apps I don't need, and I don't trust them, but as others pointed out this would mostly just be whiny. That's why I asked for reasons why restricting users to MS Authenticator would be preferable. If it's more secure or technically way easier and thus cheaper to maintain then fine, I'll find an acceptable way to comply. If not, then it's them who are whiny and I'd rather make the case to let us use whatever authenticator we already have installed.

[–] sunbeam60@lemmy.one 4 points 9 months ago (1 children)

But MS Authenticator isn’t a normal 6-digit Authenticator; it scans your Face ID (or finger print) and in many cases (like my work) it can be support password less accounts (relying only on something you have and something you are).

And in regard to your point that you don’t want to install apps you don’t need, it sounds like you do in fact need this app.

🤷‍♀️

load more comments (1 replies)
[–] rekabis@lemmy.ca 3 points 9 months ago (3 children)

reasons why restricting users to MS Authenticator would be preferable

As a security professional:

  1. Under most situations, it is equally as good as any other 2FA app.
  2. Within the Microsoft ecosystem, it provides additional security features above and beyond simple 2FA.

If your workplace is leaning heavily on the Microsoft ecosystem, especially their cloud offerings like Azure, then restricting employees to the Microsoft app is a no-brainer, and actually quite reasonable.

For example, if they happen to have a hybrid domain with an on-prem domain controller syncing with Azure (forgive me for using obsolete terms, I’m a greybeard), then they can control all access to all company assets, including 2FA. If an employee leaves the company, they can also disable the Microsoft app at a moment’s notice by disabling the employee’s Microsoft account. Because everything is hooked into Azure, it sends push notifications down to all company assets - like the Microsoft 2FA app - to unhook all of the company’s credentials and prevent employee access after the fact.

You cannot do this with other 2FA apps.

load more comments (3 replies)
load more comments (1 replies)
load more comments (4 replies)
[–] metawish@lemmy.ml 3 points 9 months ago

Lots of great conversation here, I also work somewhere where this is required. If I didn't need my phone for access to chat, I just wouldn't use it for work. Alternatively, my phone has a work profile so I use that for any work related or non-FOSS apps. My IT guy even approved of my methods and said do the minimum and never more with tech.

[–] Martin@lemmy.ml 3 points 9 months ago (1 children)

Thanks people, some good replies here. I could demand a work phone, but that's impractical, dragging around two phones etc. I'd like all my 2FA in Aegis and not have to think and pick the right app first, let alone pick and unlock the right phone. The Shelter option is very nice, didn't know about that. If my company won't budge I'm doing that. When push comes to shove I could even use outlook that way on my phone.

load more comments (1 replies)
[–] HubertManne@kbin.social 2 points 9 months ago

when you get the prompt at my work their is an option that says you don't have your phone on you and it leads to the old way of doing it.

load more comments
view more: next ›