[Autogenerated] We've talked about good architectural principles here about,
you know, doing it centrally managed, uh,
password management, use a creation.
We've talked about having a ticketing system or some sort of
process that you can actually order it.
So But where the organization is usually fail in in in the first part,
requirement IT well,
so if they've got a series off generic users or or
problematic process IEDs or something like that,
right, that those error sometimes difficult to to to deal with right?
Or if they don't have a really good process for managing that,
that users kind of entire lifecycle e mean,
ideally, the idea of having a ticket or some sort of record.
This user account came into the organization at this point in time,
and we granted or this person right, And we gave them,
you know, an 80 user account.
And we gave them this other user account and we gave them these
privileges and and And as they moved through the organization,
they sort of collect things as their job roles dictate.
I see two things that fail right?
One is that,
uh if if somebody moves responsibilities within an
organization right and they get new things,
you know,
they're very good at accumulating the new users or the
new roles or the new privileges.
But organizations error really terrible at sort of letting go of the old ones,
right?
So somebody just accumulates more, more stuff,
you know, over a long tenure, half of which they don't need anymore,
right?
And other thing is that when a when a an individual leaves an organization,
do you have a really clear record of where all those user accounts are?
So you could go deactivate all of them right again.
If you've got, you know, sort of everything in a d or everything in l'd app,
you could go flip the switch on that one place and get 80% of it.
But then if that's an I t person or somebody that's got some
specialized kind of responsibilities and they have this one off
user account in this appliance or there's one off user account
in this in this application, and you don't go deal with that right,
that's about or or, you know,
if they have a bunch of access to third-party utilities
and you're not tracking that right, you know,
for many years at at, uh, you know, my my previous employer,
right where we provided a Zvi services.
And we had other kind of portal access for our clients,
uh, to supply documentation during an assessment or get vulnerability scans.
Right?
Uh, you know, the client organization wouldn't deal with those user accounts.
Is those people left the organization?
You really want your former employees having access to your vulnerability?
Scans?
Really?
But that's that's just I mean, a problem of the way that our entire you know,
software as a service based infrastructure is tending to working organizations.
If you if you don't have a single sign on, you, don't have a wolf in place.
Keeping track of that almost impossible for a big it gets really difficult.
And I think what you have to do is have a fairly regular sort of occurrence of,
you know,
getting all the right people together and scribbling on the white board.
Like Okay, where are their repositories of user accounts?
What are we forgetting and hope?
People are sort of caffeinated enough to spit all the right answers,
but hopefully not a lot of that's gonna be where there's cardholder data,
I hope hopefully hopefully, but I'd say increasingly,
you know, affects the security off