• 326 Posts
  • 884 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle


  • You can probably get the URL for a companies SharePoint pretty easily, but you need a login. You are able to get a PAs credentials through a phishing link etc but need the 2fa code.

    You do the IT phishing attack (enter this code for me to fix your laptop being slow…), get them to enter the code and now you have access to a SharePoint instance full of confidential docs etc.

    I’m not saying it’s a great attack vector, but it’s not that different to a standard phishing attack.

    You could attack anything that’s using the single sign on. Attack their build infrastructure and you now have a supply chain attack against all of their customers etc.

    It helps but its not enough to counter the limits of human gullibility.







  • Nighed@sffa.communitytoAsklemmyCan I refuse MS Authenticator?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 days ago

    Bad actor goes to super secret page while working on ‘fixing’ and issue for the user. They then get the 2 digit request code and ask the user to input it to ‘resolve’ the issue.

    Mostly the same as any other 2fa social engineering attack I guess, but the users phone does display what the code is for on the screen which could help… But if your falling for it probably not.




  • Nighed@sffa.communitytoAsklemmyCan I refuse MS Authenticator?
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    4
    ·
    2 days ago

    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?













  • I would split digital privacy from the foss and Linux discussions. They attract the same people, but are fundamentally different topics.

    It also means you could get deeper into the digital privacy topic which is more useful to most people.

    For the digital privacy one, ask for a volunteer (or do you!) ahead of time and get them to do GDPR requests for apple, Google, Microsoft, Meta etc. sanitizer anything they want to hide, but do a demo of what big tech actually knows about them.

    Then go though how to prevent that and have a discussion on the pros and cons of that data collection. (Eg I don’t care about Google data tracking as I find the Google location history really useful)