News for hackers. Stuff that matters.
Re:Developing inside a virtual machine by mongol on Wednesday January 01, 2025 @05:23PM (#42569811)
I do something similar but using WSL on Windows. But something I really, really hate is dealing with special certificate handling required to pass the corporate Zscaler proxy. I think it works somewhat transparent on the Windows host, but repeating the setup in every VM is such a pain.
Re:Developing inside a virtual machine by deergomoo on Wednesday January 01, 2025 @06:22PM (#42570143)
Heh, my employer is rolling out Zscaler this year. The limited trial a few months ago was hell for folks using WSL primarily, with Docker images adding an additional layer of pain.

The people in the trial got very little done until it was decided to pause it, and I do not have high hopes for when it’s tried again. It strikes me as basically running malware in the name of security.

Re:Developing inside a virtual machine by UltraSane on Wednesday January 01, 2025 @09:44PM (#42571136)
I worked at a government agency that used Zscaler to perform TLS MITM inspection. You have to create a tunnel to a Zcaler datacenter and send all your traffic to them encrypted with a certificate they provide so they can decrypt it. Then they encrypt it again and send it on its way. It can detect things that otherwise could not but you are putting a LOT of trust into Zscaler security because anyone who hacks them can see EVERYTHING you are doing. And it is a HUGE waste of processing power and joules. You can create exceptions for URLs and source IPs.

I much prefer filtering on the endpoint before TLS encryption.

Re:Developing inside a virtual machine by rawgabbit on Wednesday January 01, 2025 @09:57PM (#42571188)
I knew Zscaler did MITM. But I thought it only inspected hashes or summaries to detect malicious content. I didn’t know it would encrypt again.
Re:Developing inside a virtual machine by klooney on Wednesday January 01, 2025 @11:07PM (#42571535)
They even do per-service stuff- their big AI feature is that it will detect people pasting social security numbers or other PII into ChatGPT and block it.
Re:Developing inside a virtual machine by gruez on Thursday January 02, 2025 @09:57AM (#42574938)
>I didn’t know it would encrypt again.

"encrypt it again" in this case means establishing a new TLS connection to the original host and forwarding the decrypted contents in this new connection. This is obviously required if the original host only had a https endpoint, and (more importantly) so the traffic isn't exposed on the wider internet.

Re:Developing inside a virtual machine by bitwize on Thursday January 02, 2025 @01:16AM (#42572161)
You'd think last year's Clownstrike incident would put the lie to the efficacy of the fucking-for-virginity approach to endpoint security favored by organizations but no.

At the enterprise level, security isn't really about security, it's about having an audit trail so bad actors can be caught after the fact.

Re:Developing inside a virtual machine by daghamm on Thursday January 02, 2025 @04:05AM (#42572876)
You would be surprised how much of corporate cybersecurity is done like this. It has not in anyway improved sine crowdstrike, on the contrary EDR shenanigans has probably grow 100% since last year.

These security companies must have really good salesmen. Or maybe IT departments are always ran by clueless fools, who knows?

Re:Developing inside a virtual machine by vladvasiliu on Thursday January 02, 2025 @08:41AM (#42574323)
> Or maybe IT departments are always ran by clueless fools, who knows?

I think IT has its fair share of clueless fools, but what I've noticed is that when the "security department" is separate, people there tend to have no idea what they're talking about and rely on checklists. Plus, "everybody uses X, that means we're missing out".

Re:Developing inside a virtual machine by MaKey on Thursday January 02, 2025 @09:00AM (#42574453)
Corporate IT security seems to be mainly about checklists and compliance, not about actual security.
Re:Developing inside a virtual machine by mrguyorama on Thursday January 02, 2025 @12:29PM (#42576462)
There's no reason to do anything else. Nobody has gone to jail as of yet for not securing their company, and even "security" companies that get utterly popped still have plentiful business a year later.

There is no legal incentive to do good security. There is no market incentive to do good security. Why is it so surprising to people that we have abysmal security?

Re:Developing inside a virtual machine by vladvasiliu on Friday January 03, 2025 @03:23AM (#42583703)
In my case, it's surprising because companies waste a ton of money buying snake oil and aggravating their users for next to no benefit. You'd expect companies that "only care about their bottom line" to optimize this away, yet they don't.
Re:Developing inside a virtual machine by screcth on Thursday January 02, 2025 @09:15AM (#42574578)
The security team cares about minimizing risks to the company and to their own careers.

Deviating from what everybody else is doing makes it so that the burden of proving that your policies are sane is on you and if anything bad happens your head is the first to roll.

You use CrowdStrike and the company lost millions of dollars due to the outage? That's not your problem, you applied industry standard practices.

You don't use CrowdStrike and the company got hacked? You will have to explain to the executives and the board why you didn't apply industry standard practices and you will be fired.

Re:Developing inside a virtual machine by gruez on Thursday January 02, 2025 @09:58AM (#42574952)
>the fucking-for-virginity approach to endpoint security

???

Re:Developing inside a virtual machine by bitwize on Thursday January 02, 2025 @10:34AM (#42575307)
Compelling users to have software indistinguishable in its operation from malware running on their machines for security purposes is, as the expression goes, like fucking for virginity.
Re:Developing inside a virtual machine by UltraSane on Friday January 03, 2025 @04:10PM (#42589493)
It is like hiring bodyguards. Bodyguards could kill the person they are protecting at any time BUT they have an economic and legal incentive to not do so and so you bet that the odds of being killed by bodyguards is far lower than by some random stalker.

Like wise giving Crowdstrike root access to everything is a bet that you will on the whole be more secure than if you didn't and for most companies I believe this is true. But if you are Google or AWS you are going to be able to do better than Crowdstrike.

Re:Developing inside a virtual machine by chrisweekly on Wednesday January 01, 2025 @05:54PM (#42569992)
Given how much you hate it, any chance you documented how you did it?
Re:Developing inside a virtual machine by mongol on Wednesday January 01, 2025 @07:07PM (#42570375)
No not really. The employer has some documentation, it is not complete but is starting point when issues pop up. For example, a JDK neeed to have special certificates installed if Java tries to talk SSL. And when you juggle with different JDKs for different Java versions it becomes a nightmare. The best you can do is to try not to touch anything when it eventually works but eventually something unforeseen breaks it anyways.
Re:Developing inside a virtual machine by Atotalnoob on Thursday January 02, 2025 @01:21PM (#42577102)
All you really need to do is install the zscaler cert in the appropriate trust store.

It’s really a 1 step process in your dockerfile or other location.

Re:Developing inside a virtual machine by UltraSane on Wednesday January 01, 2025 @09:40PM (#42571118)
I have administered Zscaler and I bet the issue is that Zscaler is doing TLS MITM and every windows machine joined to the domain is configured to trust the Zscaler wildcard cert used for every site. This usually just works for anything joined to the domain but the cert has to be manually trusted for anything else. And yes it is amazingly annoying. I try to write a script or bake the cert into an OS image.