Re: [Full-Disclosure] Re: Pudent default security

From: Jay Sulzberger (jays_at_panix.com)
Date: 09/29/03

  • Next message: Michal Zalewski: "[Full-Disclosure] Re: Pudent default security - Was: CyberInsecurity: The cost of Monopoly" 
    To: erc@pobox.com
Date: Mon, 29 Sep 2003 00:41:35 -0400 (EDT)

    On Sun, 28 Sep 2003, Ed Carp wrote:

    > On Mon, 29 Sep 2003, Jay Sulzberger wrote:
    >
    > > > Yes, that is what I was trying to say, however lamely. The preponderance
    > > > of discussions and papers on security today focus on the network and how to
    > > > control the flow of data/packets. But in the final analysis, the problems
    > > > always come down to the individual machine, be it server or workstation.
    > > > Why aren't security ideas focusing on that problem primarily? Oh, we all
    > > > know you shouldn't run unnecessary services, but that's about as far as the
    > > > wisdom goes.
    >
    > And that's why the MS Blaster worm and variants have been so successful -
    > most admins think that because they have a properly configured firewall in
    > place, they're invulnerable - never realizing that all it takes is someone
    > with an infected laptop to plug in behind the firewall, and they're toast.
    > But it's somewhat understandable, because all the trade mags have been
    > harping on is a centralized firewall for years.
    >
    > > > IMO the vendors should be providing these types of tools as an integral
    > > > part of the OS in addition to shipping in an off-by-default model. It
    > > > should be trivial to "do security" in an OS. (It still blows my mind that
    > > > every WinXP box comes with UPnP on by default. RPC I can *almost*
    > > > understand, but UPnP???) I'm saying we need a paradigm shift in *thinking*
    > > > about how an OS should be configured out of the box *and* a paradigm shift
    > > > in the ease of configuration on an enterprise level.
    >
    > At least it comes with some sort of firewall - a step in the right
    > direction, I think. Too bad no one in my company runs XP - too
    > unstable...

    Tiny attribution alert: I wrote none of the words above.

    oo--JS.

    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html

  • Next message: Michal Zalewski: "[Full-Disclosure] Re: Pudent default security - Was: CyberInsecurity: The cost of Monopoly"

    Relevant Pages

    • Re: F**kin hackers!
      ... Successful information gathering doesn't guarrantee successful penetration. ... If your firewall is stopping open TCP and UDP connections, ... As usually, I have to note that firewall is just one measure, and you need ...
      (microsoft.public.win2000.security)
    • Re: XP-98 probs (cross-posted)
      ... She should be running a firewall and have up to date patched software. ... > it is different from that on the one and only successful connect. ... Cable operators here often have fairly stable IP assignments as well -- only ... > reinstalled NetMeeting and I guided her through the setup over the ...
      (microsoft.public.internet.netmeeting)
    • Re: XP-98 probs (cross-posted)
      ... > She should be running a firewall and have up to date patched software. ... not firewalled computer on a cable connection for 15 minutes ... >> it is different from that on the one and only successful connect. ... >> reinstalled NetMeeting and I guided her through the setup over the ...
      (microsoft.public.internet.netmeeting)
    • Re: FTP attempt yields.......ftp: connect :Unknown error number
      ... tried to upload a website from Dreamweaver towww.angelfire.comand ... websites to connect with angelfire and that was successful. ... Which firewall are you using? ...
      (microsoft.public.windowsxp.network_web)
    • New Windows 2003 unable to ping Firewall
      ... I did some ping test to the firewall to ... first incident happen in just a few hours of successful ... installation to a Check Point 4.1 firewall. ...
      (microsoft.public.windows.server.networking)
    • Quantcast