faebudo

Use the recommemded parameters: https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-argon2-04#page-11

Also consider WebauthN/Passkeys. They are much less ressource intensive on the server but useless to an attacker when the database is leaked and as such don't rely on slowing down the crypto operations.

"The company currently exports Model 3 vehicles from Shanghai to the EU, while it produces the Model Y in Berlin."

It's right there in the article if anyone would care to read it.

Your first step will be learning to dry it and keep it dry. I can recommend a scale that can resolve to at least 0.1g so you can measure the weight loss while drying. This will help in seeing when it's sufficiently dry (put it in dryer and weigh it every hour) and if it took moisture again.

There are so many VPN providers selling your data, being operated by the feds, operated by cybercriminals etc. it really doesn't matter just as said in 8.

We better should've stayed at 640kB.

They will after

Room-scale DnD dungeons anyone?

It looks like there are multiple layers printed without feeding filament, which causes these frays to build up. Could it be that the filament clogs after this layer? Or do you see that filament still properly feeds later? This could happen for example due to heat creep and the filament getting too warm/soft in the extruder to properly feed or you trying to feed too fast.

Yes I know. We do simulations but we only measure who reports them and provide training how to report them (In the mail itself). No shaming for user who click them and no additional training on how to look at details.

It makes no sense training the user in looking at for example the links if all the big vendors use suspicious links anyway. For example the phishers use OneNote shares to phish, but those are hosted on Microsoft which by itself is legitimate. The only way a user really is able to recognize a phish is if it is unsolicited (report the mail as spam) or if it looks legit but asks for credentials (report it, we use SSO everywhere possible and you should never be asked for credentials for one of our platforms). We cannot do this for all vendors however and the users are encouraged and trained on using Passkeys or Autofill by the company provided password manager so that they get suspicious when no autofill is possible, then they can report the mail.

It's not always possible to recognize phishing from the get go and security is better suited to investigate than rando from the logistics department.

Yes but the only relevant metric is how many reported it. Doesn't matter if they delete, read, click or enter data. We're only interested in the information that a phish got through our security controls (=we failed our users), so we can investigate (and clean up if needed) the impacted mailboxes and accounts.

The layoffs are finally paying off..

However I can see when any IPv6 begins with 2a02:12xx:: then it's Swisscom (biggest swiss ISP). But I can't remember any of their hundreds of IPv4 prefixes.