Hal Sclater

Microsoft 365 Consultant.

[Hal Sclater @hsclater]

@smtp2go everything is broken today

[Hal Sclater @hsclater]

@colhountech smtp2go. @sendgrid send me multiple emails saying I get a discount if I upgrade, there is no discount available. I guess sendgrid don't want their free customers any more.

[Hal Sclater @hsclater]

It's 2024, we just moved 70TB of files to Azure NetApp, the #1 issue is due to windows file path limitations, an issue that's existed since Windows 95. Why can't @microsoft fix this in file explorer?

[Hal Sclater @hsclater]

@glass__revolver Loooks epic, Elden ring vibes

[Hal Sclater @hsclater]

@WordPress @wp_acf This is absolutely insane. We’ll be moving our clients to a new platform.

[Hal Sclater @hsclater]

@azuread Also all the documentation is out of date e.g. https://t.co/KwTTHqWQQi

[Hal Sclater @hsclater]

The removal of M365 license management in @azuread needs a serious rethink.
- No Reprocessing in the UI
- You can't manage service plans
- You can't see license assignment errors
- In various places in admin you are told to go back to Azure AD.

[BlackRoomSec @blackroomsec]

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: https://t.co/oX8YEJHxXg

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!

[Hal Sclater @hsclater]

@merill @12Knocksinna @DanielatOCN @fabian_bader @inversecos @janbakker_ @NVISO_Labs @rootsecdev This dialog always confuses people because there are so many combinations just with the one tick box and 2 buttons. This doesn’t really change it much.

[Hal Sclater @hsclater]

@maryjofoley What the heck is bizchat!

[Mary Jo Foley @maryjofoley]

Microsoft's virtual M365 Copilot Wave 2 event is coming up at 11 a.m. ET/8 a.m. PT today with @satyanadella and @jared_spataro. Link to watch live:
https://t.co/8WcUCRbFXM

[Hal Sclater @hsclater]

@bt_uk someone left this comms cabinet open on sumner st and now there’s a banana in it. Can you get someone to come and lock it? Been like this for weeks.

[Hal Sclater @hsclater]

@JoanneCKlein With guest accounts it even worse as often guests will have no way of contacting IT of the other company, and they get locked out, shouldn’t really require guests to use MFA.

[Hal Sclater @hsclater]

@JoanneCKlein I must have over 30 work accounts and have to register them all. Do this before wiping the old phone makes it much easier.

[Hal Sclater @hsclater]

Added MFA to an corporate apple id...it completely locked it out, been like this for days. Apple support can't help, yes Apple's MFA sucks.

[Hal Sclater @hsclater]

@12Knocksinna @Office365 If admins are not already using MFA for everyone including themselsves then they shouldn’t be admins

[Hal Sclater @hsclater]

@merill We use Yubico Security Key C NFC, cheap and work well. Up to 25 FIDO2 keys, supports their auth app for key management.

[Jan Bakker @janbakker_]

I would also recommend FIDO2 keys for break-glass emergency axccounts.

However, if you are looking into CBA, do know that most FIDO keys also have PIV slots to store certificates..

https://t.co/tSrgyWPYWW

[Hal Sclater @hsclater]

Test your prompt injection skills! Made it to level 7...https://t.co/pQArixqyPW