Organization Settings - in the real world

rhbirkelund
Kind of a big deal

Organization Settings - in the real world

For every Meraki customer that I have, the Security Settings under Organizations has its own variations.

rbnielsen_0-1625469919512.png

 

But I am curious as to what ya'll do? 

How do you configure each customers organisational settings and why?

Or in that case, your own company's settings?

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
3 REPLIES 3
CptnCrnch
Kind of a big deal
Kind of a big deal

Even Microsoft itself has gotten to the point that expired passwords decrease security, therefore I'd leave that off.

Used passwords is a two fledged sword, possibly I'd enforce those.

Strong passwords are always a good idea.

Account lockout should be set to prevent users from being brute forced

Idle timeouts are a good things until they're set too low. I'd go with 2-4 hours

Two-factor authentication is a must nowadays

If you have the chance to provide fixed login IP ranges, these are also a good idea.

PhilipDAth
Kind of a big deal
Kind of a big deal

The only option I like to have enabled is forced MFA.

KarstenI
Kind of a big deal
Kind of a big deal

Making sure the customer has MFA enabled is IMO the most important step in onboarding a new customer. I don't want to get the call "my org is gone" because of a compromised account ...

Get notified when there are additional replies to this discussion.