X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8F65711F6289 for ; Tue, 25 Apr 2006 20:04:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 51093-08 for ; Tue, 25 Apr 2006 20:04:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id F354611F6280 for ; Tue, 25 Apr 2006 20:04:03 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 29934314C2; Wed, 26 Apr 2006 01:04:04 +0200 (MET DST) From: Chris Browne X-Newsgroups: pgsql.general Subject: Re: Database Selection Date: Tue, 25 Apr 2006 22:58:50 +0000 Organization: cbbrowne Computing Inc Lines: 34 Message-ID: <60u08hp8id.fsf@dba2.int.libertyrms.com> References: <1145863743.280424.116910@y43g2000cwc.googlegroups.com> <1145946406.876724.302030@g10g2000cwb.googlegroups.com> <1145980154.23538.212.camel@state.g2switchworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) Cancel-Lock: sha1:jYOGC25Kh53By1MOMUaHr6DFtok= To: pgsql-general@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/1121 X-Sequence-Number: 94562 smarlowe@g2switchworks.com (Scott Marlowe) writes: > About the security thing. Security is a process, and you won't get > it from using two different database engines. I'd argue that security is an "emergent property" which is either supported by or undermined by particular facts/features/configurations. It's not something you can have; instead, conditions may either: a) Leave you vulnerable to particular attacks, or b) Protect you from particular attacks. "Being secure" means that you have done an analysis of some set of attacks and relevant vulnerabilities, and verified that your conditions provide protection against those attacks. Having multiple databases around would protect certain vulnerabilities; whether they are *relevant* is a whole other matter. The notion of having a mental model of what security is, that's something I'd consider vitally important. If you can't articulate some sort of model that involves the notions of: - Attacks, vulnerabilities, and protection against such - Having some classification of kinds of possible attacks then I don't think it's possible to articulate that there is any resultant security. You might be secure, for some definition thereof, but if you can't articulate that definition... -- output = ("cbbrowne" "@" "acm.org") http://cbbrowne.com/info/security.html Friends help you move. Real friends help you move bodies.