X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8C17352EB8 for ; Sat, 13 Aug 2005 02:22:56 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48848-01 for ; Sat, 13 Aug 2005 05:22:53 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id C091852D10 for ; Sat, 13 Aug 2005 02:22:52 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j7D5Mmeb050037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2005 23:22:51 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j7D5MmQx048423; Fri, 12 Aug 2005 23:22:48 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j7D5MmkX048422; Fri, 12 Aug 2005 23:22:48 -0600 (MDT) (envelope-from mfuhr) Date: Fri, 12 Aug 2005 23:22:48 -0600 From: Michael Fuhr To: wisan watcharinporn Cc: pgsql-admin@postgresql.org Subject: Re: how to protect root access database Message-ID: <20050813052248.GA48235@winnie.fuhr.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200508/170 X-Sequence-Number: 18489 On Sat, Aug 13, 2005 at 03:37:37AM +0000, wisan watcharinporn wrote: > i have database with critical data (such patient information) > how can i protect my database from root access > because this host in company can access with root from many person > (person who manage some service application on host but must not access > this patient information) If you're handling critical, confidential information then you should consult a security professional. No offense intended, but if you have to ask these kinds of questions then you aren't qualified to implement the solution. Even if you encrypt the data so root can't read it, root could still corrupt or destroy it (intentionally or accidentally) with the privilege it wields. If the data is critical and confidential then only trustworthy persons should have access (remote or physical) to the system that stores it. A system that gives root access to "many persons" is a dangerous place to store such data. For the sake of your patients' safety and privacy, please consult a security professional who knows what they're doing. -- Michael Fuhr