QUIC is the standard problem across n number of clients who choose Zscaler and similar content inspection tools. You can block it at the policy level but you also need to have it disabled at the browser level. Which sometimes magically turns on again and leads to a flurry of tickets for 'slow internet', 'Google search not working' etcetera.
Hmm, interesting. We also have a policies imposed by the Regulator™ that leads to us inspecting all web traffic. All web traffic goes through a proxy that's configured in the web browser. No proxy, no internet.
Out of curiosity: What's your use case to use ZScaler for this inspection instead?
Why wasn't there a PAM solution in place that logged all the mainframe user level activities and commands? Maybe cyberark or such? Would have help to trace the issues and even control such commands from being run by a novice.
1 is already a solved problem. My employer had originally put a ML based system to find DQ issues (already working) and is looking at pocs to add LLMs in the model mix. Hearsay is that our lakehouse vendor will have their own solution to this question via a acquisition.
2 is interesting, possible to do via LLM but I worry about data privacy and hallucinations making data more believable but not real.
There is a category of sms that won't show up in your inbox. Think of them as messages for your baseband/ system. But they will result in delivery messages. They used to be quite well used in the Nokia era.
This is a company that bills it's sales team to clients indirectly. Wonder if they've automated/ ai-fied some of their mundane corporate functions and back office activities leading to this point.
I highly doubt they've replaced internal functions with AI. They're probably just firing a bunch of people, and telling anyone left that they'll have to pick up the slack and to be thankful for still having a job.
The number needs to be recreated at the original provider (assuming no one else has picked it up), activated, ported multiple times (if you have ported earlier) and then brought to the current final provider.
Source - lost a 20+ year old number during a port activity the same way. Fortunately the provider was a client, and got a circle head involved to recover the number in the way it is mentioned above. Took a week.
