In this case this officer was searching numerous networks over and over again, that alone should trigger some metrics that raise the question "uh ... why?"
In this case this officer was searching numerous networks over and over again, that alone should trigger some metrics that raise the question "uh ... why?"
If the stakeholder wants a way to bypass this or that, then that's what's going to happen. Neither users nor stakeholders will want to be handcuffed in the name of public accountability. Nobody wants to be handcuffed, really.
I’m sure that’s the case for everyone, but we have permissions and security and auditing for reasons none the less.
https://www.flocksafety.com/blog/how-the-safe-list-solves-pr...
The HOA ones come with “safe list” whitelisting to somehow cause it to dump local reads for some plates? This slightly also seems like a bad idea at least because then you just need to steal a car inside the gated community to defeat its "safe list" and wander around it without its Flocks reading you.
(I mean, once you leave the gated community, you're fair game again, but still: the 'safe list' feature provides bullshit privacy relief to even more ignorant people who are probably more relieved that they think they're suddenly not the ones that will be tracked but only the evil minorities will be.)
Any employee could just search the name of a celebrity who was a card holder and view all their transactions. Not sure if that's still the case, but the only point I want to make here is that when this was brought up internally as a security issue, the top management clearly didn't care and did nothing about it.