ʞɔıɹʇɐԀ 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…
ʞɔıɹʇɐԀ 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
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
|-----------|
| SITE'S |
| BROKEN, |
| POST |
| ASCII |
| ART |
|-----------|
(\__/) ||
(•ㅅ•) ||
/ づ
ʞɔıɹʇɐԀ 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
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Sure enough!
I am releasing splunk queries/jupyter notebook that allows you to take kerberos ticket requests and track them back to the client binary AND the user that MADE the request.
Gist: gist.github.com/jsecurity101…
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Ransom Cartel's configuration pretty much has the same format as REvil.
I have uploaded the full configuration + decoded ransom note here github.com/cdong1012/IDAPyth…
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
hey all, can you help spread the word on What2Log.com?
I'm hopeful that this is a useful resource for the community, but I'm not seeing much love for this IMO great project. I'm working on getting the word out... but I'll need your help.
1
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Being in the trenches, it's easy to overlook how impactful our work is. But proactively notifying a victim of an issue - it reenforces just how *cool* our day job is.
Top coverage that catches pre-#ransomware activity is becoming more common. What's a victim to do when notified?
What To Do If You Get the Dreaded #Ransomware ‘Victim Notification’ - article by @Gigs_Security
ransomware.org/blog/what-to-…
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Finally added the rest of the gang to Docker-OSX
macOS VM's on Linux & Windows (WSL2 btw)!
Full house of VM's for security research:
- Monterey
- Big Sur
- Catalina
- Mojave
- High Sierra
github.com/sickcodes/Docker-…
Discord discord.gg/sickchat
Telegram t.me/sickcodeschat
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
*sits in the same spot for 40 hours a week*
*minimal face to face interaction with other humans*
*irrational fear of being fired for 8 hours a day*
*closes laptop each evening to "relax" 4ft away in the same room*
sunday night: why do I have anxiety?
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Check out PingCastle by @mysmartlogon, it abstracts complex information into easily understandable report. #cyber #activedirectory #bestpractices make it your career goal to fix all the issues and you’ll probably be 80% safer against full scale #ransomware pingcastle.com/
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Many organizations see recovery as an opportune time to execute an upgrade or migration. https://nitter.gq/t.co/vEYg8o6r6J MOXFIVE Director of Technical Advisory Services Thomas Aneiro offers 4 questions to consider before making that decision. #incidentresponse #cybersecurity
ʞɔıɹʇɐԀ sɐɯoɥ⊥ retweeted
Is ransomware a symptom or the disease? In our latest blog, @jason_rebholz looks how the ability to monetize attacks is driving the evolution of extortion-based attacks.
https://nitter.gq/t.co/LsWqVEhbWj #ransomware #cybercrime #extortion
































