Forgot your password?
typodupeerror
Security Operating Systems Software

Is Whitelisting the Answer To the Rise In Data Breaches? 195

Posted by timothy
from the none-shall-pass dept.
MojoKid writes "It doesn't take a rocket scientist to figure out that cyber criminals are quickly getting more sophisticated than current security, intrusion detection and prevention technology can defend against. And you have to wonder if the computer security industry as a whole is willing to take the disruptive measures required to address the issue head-on. One way to tackle the surging data breach epidemic is with a technology called "whitelisting." It's not going to sound too sexy to the average end user and frankly, even CIOs may find it unfashionable but in short, whitelisting is a method of locking-down a machine such that only trusted executables, DLLs and other necessary system and application components are allowed to run – everything else is denied. A few start-up security companies are beginning to appear in this space. The idea is to start with a known, clean system installation and then lock it down in that state so absolutely nothing can be changed. If you follow system security, regardless of your opinion on the concept of whitelisting, it's pretty clear the traditional conventions of AV, anti-malware, intrusion detection and prevention are no longer working."
This discussion has been archived. No new comments can be posted.

Is Whitelisting the Answer To the Rise In Data Breaches?

Comments Filter:
  • Brilliant... (Score:1, Insightful)

    by Anonymous Coward on Sunday February 09, 2014 @05:13AM (#46201211)

    ... next we'll make it impossible to emulate a trusted DLL ... oh, wait.

  • Seriously? (Score:5, Insightful)

    by gman003 (1693318) on Sunday February 09, 2014 @05:32AM (#46201295)

    Why the flying fuck does anybody think Slashdot readers need to have "whitelisting" defined for them, let alone think they can pass it off as a "new technology"? Did Dice start putting those retarded SlashBI articles in main Slashdot now?

  • Re:Do it in ROM (Score:4, Insightful)

    by TheReaperD (937405) on Sunday February 09, 2014 @05:49AM (#46201365)

    Sadly, the worst problem for system security is humans. If you required the flipping of a physical switch then malware would simply tell the user to flip the switch to see your choice of free porn, music, movies, games, etc. and the human will flip the switch (or any other method that requires human action). Humans are stupid... sad but, true.

  • Re:Seriously? (Score:5, Insightful)

    by TheReaperD (937405) on Sunday February 09, 2014 @05:55AM (#46201387)

    Though most, if not all of us, know what whitelisting is, I do prefer they explain it rather than assuming we know it. I've ran across too many articles in the past that assumed I knew some piece of information when I didn't. Sure, I can look it up but, that's annoying when your just trying to read "news." Though this is a site for "nerds", that is a broad term. There's computer nerds, science nerds, comic nerds, etc. Now, the passing it off as new... I've got nothing; that's just lame.

  • Re:Seriously? (Score:5, Insightful)

    by Anonymous Coward on Sunday February 09, 2014 @05:57AM (#46201397)

    Uh, yeah. The sort of dumbfuck managers who might conceivably read slashbi are the exact audience the beta design (fuck beta, BTW) is meant to appeal to.

    The big idea, though unspoken, is clear: to keep the slashdot name, but shift in both content and presentation from a discussion site seeded with news for nerds to a straight-up news site (with discussion as an afterthought) for PHBs. SlashBI doesn't work because that name is not (and has never been) perceived to carry an aura of technical knowledge -- but PHBs have been hearing about this slashdot thing for a decade now. Rolling out a PHB-friendly site under the "slashdot" brand will help PHBs play one of their favorite games, namely indulging in the fantasy of deep technical knowledge without the inconvenience of learning -- and that means Dice makes big bucks placing ads in front of this "decision maker"-heavy audience. (This new audience is not only worth more to advertisers, they're also substantially less likely to use ad blockers than the old /. community.)

  • Re:"whitelisting" (Score:5, Insightful)

    by Z00L00K (682162) on Sunday February 09, 2014 @06:14AM (#46201437) Homepage

    Most data breaches have occurred within a company, and the only way around it is to segment the networks and servers so that only select computers have access to financial data, others have access to HR data and yet others have access to strategic documents. Then it depends on company type if yet more segments are needed. In most cases the software development can go in one segment - the majority of the software developed is bread&butter. But in other cases special projects may need their own segment. Also make sure that all printers have their own sub-segment of each segment to make sure that any printer that has been hacked isn't going to have access to all the data, just the print data.

    Of course - this goes against the strategy of installing everything in one huge server running virtual servers.

    Whenever there is a need to exchange data it has to require manual action between individuals in both segments.

    And for browsing the internet - run a sandbox solution to isolate any browsing from the remaining network. It may mean that the web browser is on a special server. If that server is contaminated it's not a big problem to rebuild it.

  • old idea (Score:4, Insightful)

    by Tom (822) on Sunday February 09, 2014 @06:33AM (#46201489) Homepage Journal

    The idea is one of the oldest in IT security.

    And it works really, really well.

    And it is a PITA to administrate if you have a system that changes, as lots of systems do. For your regular service server, much less a desktop system, where new releases require new libraries, system updates are regular and new application required every now and then, it is almost impossible to actually do it.

    On a locked-down system that needs to do one thing, but do that thing reliably and securely, it's a fantastic security measure that will eliminate about half of your security headaches right there.

    It's the same idea as SELinux, just on a different level, and it shares many of the disadvantages, namely that it makes policy management into a full-time job.

  • Re:Do it in ROM (Score:4, Insightful)

    by Tom (822) on Sunday February 09, 2014 @06:51AM (#46201545) Homepage Journal

    I would like to see the filesystem of an OS partitioned into several levels: read-only disk drives where stuff never changes unless an update occurs (kernel, device drivers, configuration files), read-write disks where log files are update by the minute, hour or day, and local/user partition which is updated by the user.

    You mean the way that almost every installation guide for every Unix system ever recommends you do it, and almost nobody ever does?

  • by Dr_Barnowl (709838) on Sunday February 09, 2014 @07:04AM (#46201581)

    While I admit that as a programmer I will inevitably have a skewed point of view, I view it as ill-advised.

    A computer is useful primarily because it is NOT a special purpose tool, but a general purpose one.

    Whitelisting cripples your computer. If you can't run software without it being on a whitelist, you can't even write a shell script, or a VBA macro. Your computer stops being useful as a general purpose tool - only the software that has been approved remains useful.

    Yes, I get that most users are numpties and probably do need to be kept from hurting themselves. But this kind of policy cuts down the tall poppies - the ones who actually can make their computer work for them, instead of just working at their computer, and removes the possibility that any more will arise - no-one will voluntarily seek the rights they need to approve of their own software, because they'll be singled out as potential hackers and troublemakers, and any data breaches that do occur will be attributed to them.

    As applied within our organization, it's also soul-crushingly annoying to programmers. We'll have the rights to approve of any software we want to run, but we have to click through an approval dialog for each... new..... file... which of course, means that every time we rebuild our code we face a clickfest just to debug it, or run unit tests on it, etc.... most of us have shied away from being "upgraded" to Windows 7 because of this. Several of us just wish we could change to Linux, being Java programmers.

    Indeed, many of our internal teams are also getting the self-approval rights, which just trains them to click "Approve" and you're all the way back to UAC again, no extra security, just extra hassle, reduced performance of the computer (which is now hashing every file you access on the drive to see if it's on the whitelist), and more money diverted into the coffers of the kind of company that sponsored this story in the first place.

  • No. (Score:5, Insightful)

    by gweihir (88907) on Sunday February 09, 2014 @08:02AM (#46201755)

    As usual with this type of headline, this is not a solution. In fact, it is not a solution at all. Just think of the most common way to compromise an executable: Buffer overflow. In that case, code is put somewhere in the memory area of the running process and then the process is coerced to execute it. This means the attack code runs in the context of the already running process afterwards and white-listing has zero impact. The only effect it has is that it gets harder for the attacker to start additional processes.

    As for code-injection attacks, these are usually done with interpreted code, and white-listing does not even apply to that.

    This is another technology that at best makes it harder for script-kiddies to break into a system, but has basically no impact on competent attackers.

    Incidentally, techniques like SELinux allow far more than a simplistic "white-listing", and have done so for quite a while.

  • Re:Seriously? (Score:5, Insightful)

    by Arrogant-Bastard (141720) on Sunday February 09, 2014 @08:04AM (#46201765)
    The inferior people at Dice -- you know, the same ones trying to shove their shitty Beta site down our throats -- are actually not clueful enough to realize that this is a very old idea. Whitelisting OS resources, applications, networks, IP addresses, etc. has long been an effective security measure, and I've deployed everywhere I've been for the past 15 years or so.

    It appears that the Dicedroids think everyone is as stupid and clueless as they are.
  • Re:SLASHCOTT (Score:3, Insightful)

    by Jaruzel (804522) on Sunday February 09, 2014 @08:22AM (#46201813) Homepage Journal

    I'm SO sick of this 'Fuck Beta' crap.

    YOU the /. community are one of most technically-able groups of users on the internet. Therefore, instead of whining about a FREE service that you no longer enjoy, why not group together and build something better? If it's better than /. (not hard...) then your user base will come. A handful of you could throw up a simple blogging system in a few hours, whilst you work on something permanent...

    So instead of bitching about it to corporate owners who do not care, get off your arses and build something better.

    http://altslashdot.org/ [altslashdot.org] seems to be offline at the time of writing - a good effort but when I did look at it yesterday it seems to be 90% ideas, and sod all development. The best sites on the net, didn't spring into life fully formed, they evolved. The important thing is to just get something up and working as fast as possible.

    (Why am I not joining the effort? I'm a Windows guy, my linux foo is simply not good enough else I would.)

    -Jar

  • Re:"whitelisting" (Score:5, Insightful)

    by anubi (640541) on Sunday February 09, 2014 @08:58AM (#46201947) Journal
    A LOT of us are doing a form of whitelisting for exactly the same reason.

    How many of us are running programs similar to NOSCRIPT mostly because of hostile code and inattentive webmasters unwittingly distributing malicious code wrapped in advertisements?

    I learned about NOSCRIPT right here on Slashdot ( Thanks, guys!!! ) in response to one of my posts where I was whining ( loudly ) about not being to be on the net for more than a few hours before I had to reboot Windows to try to get my system back.

    There is a lot of nasty stuff out there, and it seems most of it comes riding in on scripting or coaxing me to run their attachment. Often I have seen them try to piggyback on the trust I have for a business - a business that places that trust at risk if the business insists I enable javascript for his site, then the bad guy uses that coercion of the business model to his own advantage.

    I think that is what a lot of the clamor here has been all about. We see wealthy investor type men taking control from the techie base and may force us to "drop our defenses" in order to communicate, and we are collectively screaming "NO" as loud as we can to the deaf ears of the businessman.

    I think we have all seen the suit people take down a business, and we don't want it happening here.
  • by Tom (822) on Sunday February 09, 2014 @10:34AM (#46202373) Homepage Journal

    Oh please do you REALLY think that is the cause of Windows infections?

    Your reply was misplaced by the comment system, it seems, because it doesn't seem to refer to anything I actually said.

    The social engineering angle is how you get users to execute crap they got sent by mail. The (old) idea under discussion here is a system that would make that execution impossible, even if you get the user to click the link.

    That said, the user is not the weakest link. That's a cop-out by IT people who don't want to look beyond technical solutions into cognitive sciences, for example. There's been a bit of research into these areas in the past 10 or so years, but the conferences on the topic are still very small and mostly academic.

    There's quite a lot you can do to prevent or at least make these kinds of attacks more difficult. But most of it is outside the techie comfort zone, and it means actually having to talk to users and understand them instead of labeling them "lusers" and stuff.

Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"

Working...