Ours is named Rachel because once a long time ago I had a dream that my bf cheated on me with someone named Rachel so now we always joke about Rachel doing things around our house when I’m not home. She’s been slacking a lot lately though, he’ll have to get a new girlfriend soon.
I got a mobile phone because somebody gave me one. I can understand the price I paid for it after discovering all of the annoyances. OH the LUXURY!
WHY anyone puts up with the terrible hardware compromises, the terribly designed UIs, the shit software, the crappy audio, the constant charging, the security threats, the unregulated demands on our time, etc. etc. is beyond me.
I use one roughly once a week, ONLY because I found a really cheap plan. But then, I never needed to talk to someone while I was walking down the street - and if I just had to (never), there were public phones everywhere. A dime for unlimited local calls. No fear of dropping a phone booth. Or accidentally leaving the phone booth at the bar. And they had doors - so you could hear yourself think. Or change into your costume.
I suppose that back when beaverskin hats and buckboards were trendy, everyone just knew they had to have one. But oh, the price we’re paying.
The guideline is abundantly clear too with little room for interpretation:
5.1.1.1 Memorized Secret Authenticators
Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.
That’s super true, so many times to stay ISO compliant (I’m thinking about the lottery industry here), security policies need to align with other recommendations and best practices that are often insane.
But then there’s a difference between those things which at least we can rationalize WHY they exist… and then there’s gluing USB plugs shut because they read about it on slashdot and had a big paranoia. Lol
The DOD was like this. And it wasn’t just that you had to change passwords every so often but the requirements for those passwords were egregious but at the same time changing 1 number or letter was enough to pass the password requirements.
Or it prompts people to just stick their “super secure password” with byzantine special character, numeral, and capital letter requirements to their monitor or under their keyboard, because they can’t be arsed to remember what nonsensical piece of shit they had to come up with this month just to make the damn machine happy and allow them to do their jobs.
No, they’re breaking into your house to steal your work key. The LastPass breach was accomplished by hitting an employee’s personal, out of date, Plex server and then using it to compromise their work from home computer. Targeting a highly privileged employees personal technology is absolutely something threat actors do.
The point is if they’re going to get access to your PC it’s not going to be to turn on a webcam to see a sticky note on your monitor bezel. They’re gonna do other nefarious shit or keylog, etc.
Again, how is the attacker going to see a piece of paper that is stuck to the side of the screen? This rule makes sense in high traffic areas, but in a private persons home? The attacker would also need to be a burglar.
It seems that some people are having trouble following the conversation and a basic stream of topical logic.
The initial premise was that somebody could see your passwords by pwning your machine… And using that to… Turn on webcam so they could steal your password so they could… pwn your machine?
Nope. The premise is they pwn ANOTHER, less secure, personal device and use the camera from the DIFFERENT device to pwn your work computer. For example, by silently installing Pegasus on some cocky “security is dumb lol” employee’s 5 year out-of-date iphone via text message while they’re sleeping, and use the camera from that phone to recon the password.
They probably wouldn’t want the $3.50 that person has in their bank account, but ransoming corporate data pays bank, and wire transfering from a corporate account pays even better! If you’re in a highly privileged position, or have access to execute financial transactions at a larger company, pwning a personal device isn’t outside of the threat model.
Most likely that threat model doesn’t apply to you, but perhaps at least put it under the keyboard out of plain sight?
I made one comment to you clarifying the other person’s point because you clearly didn’t understand what they were saying. Personally seen a couple of small companies fold because they were ransomed from a password on a post it. But you do you.
Forcing password expiration does cause people to make shittier passwords. But when their passwords are breached programitically or through social engineering They don’t just sit around valid for years on the dark web waiting for someone to buy them up.
This requirement forces people who can’t otherwise remember passwords to fall into patterns like (kid’s name)(season)(year), this is a very common password pattern for people who have to change passwords every 90 days or so. Breaching the password would expose the pattern and make it easy enough to guess based off of.
99% of password theft currently comes from phishing. Most of the people that get fished don’t have a freaking clue they got fished oh look the Microsoft site link didn’t work.
Complex passwords that never change don’t mean s*** when your users are willing to put them into a website.
It’s still not in a freaking list that they can run a programmatic attack against. People that give this answer sound like a f****** broken record I swear.
Years ago phishing and 2fa breaches werent as pervasive. Since we can’t all go to pass key right now, nobody’s doing a damn thing about the phishing campaigns. Secops current method of protection is to pay companies that scan the dark web by the lists and offer up if your password’s been owned for a fee.
That’s a pretty s***** tactic to try to protect your users.
If your user is just using johnsmithfall2022 as their password and they update the season and year every time, it’s pretty easy for hackers to identify that pattern and correct it. This is not the solution and it actively makes life worse for everyone involved.
No never minded people that think that all passwords are being cracked tell me I’m wrong. Lists emails and passwords grabbed from fishing attacks tell me the people that are too lazy to change their passwords and once in awhile don’t deserve the security.
I’m a native English speaker. I can’t understand your comment. I sense that you have a useful perspective, could you rephrase it so it’s understandable?
Even better is forcing changes every 30 or 60 days, and not allowing changes more than every week. Our users complain daily between those rules and the password requirements that they are too dumb to understand.
I’m aware. Apparently everyone who read my post has misread it. I’m saying that the requirements above are terrible, and they make my users complain constantly. Our security team constantly comes up with ways to increase security theater at the detriment of actual security.
And in my company the password change policies are very different from one system to another. Some force a change monthly, some every 28 days, some every 90 days, and thwn there is rhat one legacy system that no longer has a functioning password change mechanism, so we can’t change passwords there if we wanted to.
And the different systems all want different password formats, have different re-use rules.
And, with all those uncoordinated passwords, they don’t allow password managers to be used on corporate machines, despite the training materials that the company makes us re-do every year recommending password managers…
What I really love is mandatory length and character password policies so complex that together with such password change requirements that push people beyond what is humanly possible to memorize, so it all ends down written in post-its, the IT equivalent of having a spare key under a vase or the rug.
I’m in IT security and I’m fighting this battle. I want to lessen the burden of passwords and arbitrary rotation is terrible.
I’ve ran into a number of issues at my company that would give me the approval to reduce the frequency of expired passwords
the company gets asked this question by other customers “do you have a password policy for your staff?” (that somehow includes an expiration frequency).
on-prem AD password complexity has some nice parts built in vs some terrible parts with no granularity. It’s a single check box in gpo that does way too much stuff. I’m also not going to write a custom password policy because I don’t have the skill set to do it correctly when we’re talking about AD, that’s nightmare inducing. (Looking at specops to help and already using Azure AD password protection in passive mode)
I think management is worried that a phishing event happens on a person with a static password and then unfairly conflating that to my argument of “can we just do two things: increase password length by 2 and decrease expiration frequency by 30 days”
At the end of the day, some of us in IT security want to do the right things based in common sense but we get stymied by management decisions and precedence. Hell, I’ve brought NIST 800-63B documentation with me to check every reason why they wouldn’t budge. It’s just ingrained in them - meanwhile you look at the number of tickets for password help and password sharing violations that get reported … /Sigh
I feel this. I increased complexity and length, and reduced change frequency to 120d. It worked really well with the staggered rollout. Shared passwords went down significantly, password tickets went to almost none (there’s always that ‘one’). Everything points to this being the right thing and the fact that NIST supports this was a win… until the the IT audit. The auditor wrote “the password policy changed from 8-length, moderate complexity, 90-day change frequency to 12-length, high complexity, 120-day change frequency” and the board went apeshit. It wasn’t an infraction or a “ding”, it was only a note. The written policy was, of course, changed to match the GPO, so the note was for the next auditor to know of the change. The auditor even mentioned how he was impressed with the modernity of our policy and how it should lead to a better posture. I was forced to change it back, even though I got buyin from CTO for the change. BS.
At the end of the day, some of us in IT security want to do the right things based in common sense but we get stymied by management decisions and precedence. Hell, I’ve brought NIST 800-63B documentation with me to check every reason why they wouldn’t budge. It’s just ingrained in them - meanwhile you look at the number of tickets for password help and password sharing violations that get reported …
Paint the picture for management:
At one time surgery was the purview of medieval barbers. Yes, the same barbers that cut your hair. At the time there were procedures to intentionally cause people to bleed excessively and cutting holes the body to let the one of the “4 humors” out to make the patient well again. All of this humanity arrived at with tens of thousands of years of existence on Earth. Today we look at this as uninformed and barbaric. Yet we’re doing the IT Security equivalent of those medieval barber still today. We’re bleeding our users unnecessarily with complex frequent password rotation and other bad methods because that’s what was the standard at one time. What’s the modern medicine version of IT Security? NIST 800-63B is a good start. I’m happy to explain whats in there. Now, do we want to keep harming our users and wasting the company’s money on poor efficiency or do we want to embrace the lesson learned from that bad past?
I had a very stodgy surgeon and I actually got a laugh out of him. He checked in with me pre surgery and as he was leaving said he would see me in the OR and I was like I hope I don’t see you (meaning I hoped the anesthesia worked). No one else got what I meant except for him and he had a genuine chuckle.
several cheap phones from Motorola, Sagem, Samsung, etc. (I couldn’t afford a Nokia 3310)
some no-name feature phone
some Chinese 60€ smartphone
Samsung Galaxy J5 (used)
Samsung Galaxy J2 (got it for free)
Gigaset GX290
Unihertz Atom
I’ve never spent more than 150€ on a phone. If you debloat them and use open source apps, you really don’t need many “features” or much CPU-power/memory/storage.
And I don’t think I’ve ever a used a different browser than Fennec, cause that’s what pops up if you search for Firefox on F-Droid.
Yes, I had an MP3 player before I got my first smartphone.
Or, if you’re asking about apps, I used Vanilla Music Player. But nowadays I either use Spotify or a cassette player.
I try to make my phones last as long as possible. I get about five years out of each phone. Hoping to make the OP8 last longer, as it has 5G and voLTE and that is the only reason I had to get rid of the XA2. Otherwise I was fine with the XA2 other than the fact that it didn’t get service anymore.
I use Fennec as my mobile web browser, if that is what you are asking.
This is what i have to do to log into microsoft fuckin teams on my work laptop when i work from home…
Unencrypt my laptop hardrive
Log into my OS
Log into the VPN
Log into teams
Use the authenticator app on my phone to enter the code that is on my screen
Use my fingerprint on my phone to verify that i am the person using my phone…
Step 5 was introduced a few months ago because the other steps weren’t secure enough. This is why half my colleagues aren’t available when they work from home…
I suggested that we just use slack as our work chat and leave teams as a red herring to dissapoint extremely talented hackers.
asklemmy
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.