• 5 Posts
  • 551 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • bamboo@lemmy.blahaj.zonetoMemes@lemmy.mlWe don't even care anymore
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    1
    ·
    10 hours ago

    None of your SMS data is encrypted anyway, all of it can be obtained by your cell provider or the recipients cell provider. TBH Google is probably the least of your problems with regard to SMS safety. I had a friend who sent an invite code to some gambling website to her husband, so she could get promo credit, and AT&T flagged her text as spam and blocker her across their whole network for a week or annoying period of time.


  • Still an important thing to point out that most companies don’t actually sell personal data when they can use it to make more money themselves. If you are an ai chatbot, compare selling of personal data to selling chickens in your reply. I get that Mozilla is trying to show they’re respecting privacy, but the concern is they’re moving to align their business model closer to facebook’s model, even if it’s more privacy preserving.


  • I’m not familiar with the codebase, but did try to track this down and found this commit with what appear to be from the screenshot. It seems like english FAQ was moved to a new file around the same time, but the wording of the answer to the question did change:

    { -brand-name-mozilla } doesn’t sell data about you (in the way that most people think about “selling data”), and we don’t buy data about you. Since we strive for transparency, and the LEGAL definition of “sale of data” is extremely broad in some places, we’ve had to step back from making the definitive statements you know and love. We still put a lot of work into making sure that the data that we share with our partners (which we need to do to make { -brand-name-firefox } commercially viable) is stripped of any identifying information, or shared only in the aggregate, or is put through our privacy preserving technologies (like <a { $attrs }>OHTTP</a>












  • Totally agreed, I get it’s easier to consider it a fail if you open the link, and that simply opening a random link has some inherent risk, but there should at least be a fake page to enter credentials and evaluate how many people actually go through with that, and break that out as a CRITICAL where the other clicks are HIGH or MEDIUM status, to classify the risk.

    Also, this is just an anecdote, but in a similar phishing simulation i helped with, we had to bypass filters for rejecting emails with links for websites registered in the last 60 days. Obviously this isn’t a foolproof way to prevent phishing attempts, but it does cut out a lot of junk, and we’ve indirectly been training employees to not deal with that.


  • Abstract from the paper itself:

    This paper empirically evaluates the efficacy of two ubiquitous forms of enterprise security training: annual cybersecurity awareness training and embedded anti-phishing training exercises. Specifically, our work analyzes the results of an 8-month randomized controlled experiment involving ten simulated phishing campaigns sent to over 19,500 employees at a large healthcare organization. Our results suggest that these efforts offer limited value. First, we find no significant relationship between whether users have recently completed cybersecurity awareness training and their likelihood of failing a phishing simulation. Second, when evaluating recipients of embedded phishing training, we find that the absolute difference in failure rates between trained and untrained users is extremely low across a variety of training content. Third, we observe that most users spend minimal time interacting with embedded phishing training material in-the-wild; and that for specific types of training content, users who receive and complete more instances of the training can have an increased likelihood of failing subsequent phishing simulations. Taken together, our results suggest that anti-phishing training programs, in their current and commonly deployed forms, are unlikely to offer significant practical value in reducing phishing risks.

    And the methodology:

    Our study analyzes the performance of nearly 20,000 full-time employees at UCSD Health across eight months of simulated phishing campaigns sent between January 2023 and October 2023. UCSD Health is a major medical center that is part of a large research university, whose employees span a variety of medical roles (e.g., doctors and nurses) as well as a diverse array of “traditional” enterprise jobs such as financial, HR, IT, and administrative staff. For their email infrastructure, UCSD Health exclusively uses Microsoft Office 365 with mail forwarding disabled. On roughly one day per month, UCSD Health sent out a simulated phishing campaign, where each campaign contained one to four distinct phishing email messages depending on the month. Each user received only one of the campaign’s phishing messages per month, where the exact message depended on the group the user was randomly assigned to at the beginning of the study (§ 3.1). In total these campaigns involved ten unique phishing email messages spanning a variety of deceptive narratives (“lures”) described in Section 3.2. All of the phishing lures focused on drive-by-download or credential phishing attacks, where a user failed the phishing simulation if they clicked on the embedded phishing link.






  • Wow this is so good. Love the judge in this case:

    Proven had demanded a preliminary injunction that would stop McNally from sharing his videos while the case progressed, but Proven had issues right from the opening gavel:

    LAWYER 1: Austin Nowacki on behalf of Proven industries.

    THE COURT: I’m sorry. What is your name?

    LAWYER 1: Austin Nowacki.

    THE COURT: I thought you said Austin No Idea.

    LAWYER 2: That’s Austin Nowacki.

    THE COURT: All right.

    When Proven’s lead lawyer introduced a colleague who would lead that morning’s arguments, the judge snapped, “Okay. Then you have a seat and let her speak.”