News for hackers. Stuff that matters.
Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by xyzzy_plugh on Monday October 02, 2017 @12:32PM (#15385259)
I agree. I used to be the sole maintainer of a small Linux distribution for my employer (only a side-project, responsibility wise). This was a Fortune 50 company. I'd often have patches applied and new versions released within hours. It's very easy to do. Usually by the time someone else in the office found out, it had been patched long ago. And I'd like to be clear that I am not actively subscribed to any lists, I just casually find these issues by reading where other professionals write, often. And lo, we were more up to date than most other companies.

Sure, we were vulnerable for a brief window, and without a doubt there were other vulnerabilities, but we were pretty much as safe as possible, let alone for a half-person team.

You just don't leave windows broken. You don't leave the holes unfilled. If you find a crack in the foundation, you fix it. To do otherwise is not only irresponsible to your peers and employer, but to your customers.

My only criticism is that often the roles responsible for such things are unpleasant, come with little respect, visibility and/or pay. Companies should just suck it up and overpay a handful of engineers and security specialists, charged with the responsibility of ensuring the company avoids being vulnerable. Think of it as insurance -- it's worth far more than a bad press cycle or having your customers exploited and rightful loss of trust. The bang for your buck is off the charts.

Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by 3pt14159 on Monday October 02, 2017 @01:55PM (#15386145)
Executives don't realize that it can end a company until it does. Apple gets it. Google gets it. Facebook gets it. But very few other companies do. Cyber vulnerabilities killed Nortel back in the day. Huawei got not just designs, but details about bids, key people, everything.
Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by thephyber on Monday October 02, 2017 @02:03PM (#15386241)
Maybe 5-10 years ago companies didn't realize it. I think every major corporation has started to consider that kind of scenario now. Smaller companies may still delude themselves into thinking they aren't targets, but they probably are much less capable than big companies of investing in the required preparations to prevent those attacks.

The "black swan" events aren't costless to mitigate. In fact, they are extremely expensive. And just like there can be a black swan for cyberattacks, there can be a black swan like a terrorist attack (like companies in World Trade Center Towers 1 and 2), a massive natural disaster (think businesses in Puerto Rico right now), massive electrical outages (say an EMP or simply just Enron malfeasance), etc.

Spending to protect against and mitigate all possible black swans approaches infinity and doesn't every pay off until the extremely rare but extremely impactful event ever happens. And in cyber security, you never know because your defenses prevented it before it ever started.

Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by 3pt14159 on Monday October 02, 2017 @07:00PM (#15388712)
If they were doing as you describe they would at the very least keep their versions of Windows updated and they would enable things like two-factor authentication and TLS for their email. They don't. We're not talking expensive to prevent black swan, we're talking routine defences against white swans.
Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by zhengyi13 on Tuesday October 03, 2017 @11:30AM (#15393046)
Has this been written about anywhere? If there's a document that covers this as a case of industrial espionage, I'd love to read it.
Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by 3pt14159 on Tuesday October 03, 2017 @06:37PM (#15396795)
Yes. Read the book Cyberspies it covers this and other events.
Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by thephyber on Monday October 02, 2017 @01:57PM (#15386160)
> Companies should just suck it up and overpay a handful of engineers and security specialists, charged with the responsibility of ensuring the company avoids being vulnerable. Think of it as insurance -- it's worth far more than a bad press cycle or having your customers exploited and rightful loss of trust. The bang for your buck is off the charts.

While my gut agrees with your proposal, my brain tells me that simply patching doesn't fix either the most common issues (basic fraud, phishing, social engineering, malicious insider, etc) or the most dangerous issues (infected supply chain, zero days, etc).

Companies will still pay for insurance because your proposal doesn't insure against those other scenarios, so they will see insurance as a crutch which mitigates some of the costs which come with unpatched vulns and the race to patch.

Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by xyzzy_plugh on Monday October 02, 2017 @04:34PM (#15387691)
Of course, I'm not saying that you don't need to handle all those things -- you do. You have to have insurance, and anti-fraud departments, etc.

But compared to the costs associated with insurance or damage control, having a small team of security minded people that can make changes is basically free.