ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated.
This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses.
The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines".
The 2024 version is 800-63-4.
Here: pages.nist.gov/800-63-4/
The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org.
The previous update was in2020.
The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead:
1. After a breach/compromise
2. User request
2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords.
This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this.
Most frameworks, however, have moved away from arbitrary password resets and complexity rules.
**We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them.
Using complexity rules gets you the user psychology of:
Password1
Password2
and so on
Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies.
I'm so excited for the new changes!
Ok I'm off my soapbox.
Share the love! Thank you!
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Free training 🚨
Microsoft Office Offensive Tradecraft for Red Teamers
outflank.nl/free-training-co…
"We found a BlackCat ransom note but its encrypted by the Cuba ransomware"
Things your client doesn't want to hear on an update call.
1
1
337
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Today's thread is about something I'm rather experienced with...
How to Get Fired With Both Grace and Aplomb
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
If you really want people to click on your phishing link, make it a small „unsubscribe“ button at the end of an subtly annoying newsletter
Getting very excited to go to @RVAsec in a couple of weeks!!
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
|-----------|
| SITE'S |
| BROKEN, |
| POST |
| ASCII |
| ART |
|-----------|
(\__/) ||
(•ㅅ•) ||
/ づ
This is the greatest auto-reply I've ever received in my life. #WorkLifeBalance
34
Me: suffers from imposter syndrome
Also me: continuously works in a role that can be called as an expert witness
1
39
Hey @tastebudspod, show suggestion.. ballpark snacks. Cracker jacks vs peanuts vs cotton candy vs whatev, think it’s a good premise
28
Can @OpenAI's ChatGPT be used as a force multiplier for #cybersecurity teams? I think so! Check out some examples I created in my newest blog post https://nitter.gq/t.co/BwIVgD81MH
40
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Super useful feature! If you're working on Windows and don't have PowerToys installed yet, you're missing out!
Replying to @SwiftOnSecurity
PowerToys now has a Text Extractor tool: aka.ms/powertoys
That means that if someone sends you a screenshot of an error asking for help and you have PowerToys installed, you can just press WIN + Shift + T to extract the text of the error and avoid typing it out manually
Watching a training video and the narrator keeps saying "maulware" (malware) and I think my brain is breaking
1
While I greatly like the AAD/M365 platform as a whole, the 24 hour SLA for _literally any action_ is maddening.
1
Literal response from @MicrosoftHelps even though the initial add was yesterday. Thanks for nothing
"We have run some system diagnostics which indicate that there can be some latency in adding / provisioning guest users which may take upto 24 hours to resolve."
This week I jokingly said "I am but a humble shepherd of wayward clients" and one of my coworkers made this...
Its the best part of my week..
humbleshepardofwaywardclient…
1















