I'm really enjoying the experience on Blue Sky. I can find things that interest me again vs skipping over 99.9% nonsense. If you are also enjoying it over there, you can find me at bsky.app/profile/robwinch.bs…

🔥It’s live! SpringOne content just dropped!🔥 SpringOne is built for application developers and architects. 3 days of Spring sessions presented by the Spring experts. It doesn't get much better than that! Check it out 👉 bit.ly/44452BH #SpringOne at @VMwareExplore

Spring Security 6.4 with Rob Winch x.com/i/broadcasts/1YqKDkBLE…

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!

Attending @SpringOne? RSVP now to "Let's Explore Spring Security 6.4" where #SpringSecurity project lead @rob_winch will teach you about the latest features coming in Spring Security 6.4! event.vmware.com/flow/vmware… Can't make it? Check out the livestream springone.io/schedule

Attending @SpringOne? RSVP now to "Let's Explore Spring Security 6.4" where #SpringSecurity project lead @rob_winch will teach you about the latest features coming in Spring Security 6.4! event.vmware.com/flow/vmware… Can't make it? Check out the livestream springone.io/schedule

Spring Security deity Rob Winch x.com/i/broadcasts/1PlKQbWmo…

So happy to find out that my Spring Start Here has been published in Korean! I've just got today my paper copy!

Missed #springio24 today? 🍃 No worries, we’ve got you covered! The keynote video is now live. Enjoy! 🎉 ▶️ youtu.be/XUz4LKZx83g