Mobile device management

Y'all be wanting a hard accountability from us.

What's up with you and Deontay in Milwaukee? Why are you asking all these questions? What you doing on Monday, Tuesday, Wednesday in MDM, Jody? You going out to brunch real quick? You going to get espresso martini real quick at the Afty's or no? So...

Two weeks too soon to be asking to talk every day, though.

Yeah.

And Matthews was able to run like a crack and go.

So essentially on run game, like he's going to MDM, so he's going to block most dangerous.

And at that standpoint, the safety being at eight yards and the corner being a little bit further back, he becomes a new most dangerous man.

And it was the perfect play call.

This is what I would say is the risk that you're describing is something we're solving.

So when you really double click into this, some people in intelligence agencies and other sort of covert groups, they use what are called MDMs or mobile device management software, network software that attempts to hide the phone.

The problem is for adversaries or criminals.

That's why they look.

Go to Settings, then About Chrome, let the update download, and then restart the browser.

on every managed endpoint, push this from your MDM council rather than waiting for the gradual rollout to reach each machine organically.

And if you're a Chromium based browser, back with those vendors they typically absorb upstream fixes within a couple of days but you want to check today the exposure window here is open and it does not close until the update is installed and the browser is restarted so Something to keep in mind there.

We'll move to our next story here.

And instead we use VMs, but it's the same where VM is even stronger guarantee of isolation.

But it's the same principle is that each dev environment is entirely isolated and And then on the host, we have MDM installed.

And we use Fleet and Sentinel-1, which does scanning of these kind of indicators of compromise and common malware.

But if you don't have one of those tools installed, then maybe the first you'll hear about it is when someone accesses your production environment or you get logged out of all of your sessions of subbing because...

But from the user perspective, it's just a list of chats.

Isn't this where typically a platform team would come into play, right? If you're thinking about the remote compute.

But now if I'm on a desktop, usually the desktop minus basic MDM is completely controlled by the developer themselves, more or less.

Are we basically shifting left now platform all the way down to the laptops?

New configuration profiles also can't be installed.

So if you have an MDM and you have lockdown mode and they want to put a profile or change a profile on your device, no can do.

Wired connections also are blocked.

So if you have a Mac or you want to tether to your device, that's a no-go.

What do they in fact have access to? And what should they have access to via their identity? Are they over-permissioned? Or should we pare down their permissions? Also, is there a policy that needs to be put into place that says, you know, this group of users only has access to this subset of data, right? So audit and restrict what can be accessible.

Third would be to implement MAM and, sorry, MAM is mobile application management.

as well as MDM, if you haven't, I surely hope you have, but MDM is mobile device management.

Those two are pretty low-hanging fruit, right? But it's really good best practices.