Re: MDF file level security from copying
From: BP Margolin (bpmargo@attglobal.net)
Date: 05/25/02
- Next message: Sholana: "Recovery from Digispid.B.Worm"
- Previous message: Dave: "Recovery from Digispid.B.Worm"
- In reply to: Ayman: "Re: MDF file level security from copying"
- Next in thread: Ayman: "Re: MDF file level security from copying"
- Reply: Ayman: "Re: MDF file level security from copying"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "BP Margolin" <bpmargo@attglobal.net> Date: Sat, 25 May 2002 11:49:38 -0400
Ayman,
Sounds to me as if your first issue is the physical security of the machines
hosting SQL Server. Security starts with making sure that it is impossible
for unauthorized personnel to physically or logically access the MDF files.
Neither Windows 98 nor Windows ME were meant as enterprise level operating
systems.
-------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.
"Ayman" <aimaimoni@hotmail.com> wrote in message
news:7e7301c203b7$7ef689a0$3bef2ecf@TKMSFTNGXA10...
> Hi All,
> I have the same concern of Stephen, I thought that there
> is a way to protect the MDF files , specially in those
> located on FAT like Windows 98 and Windows ME , but it
> seems that the only way is to put it in EFS (NTFS) of
> Windows 2000, which I think it is not 100% secure as the
> recovery agent of that system could de-crypt it.
>
> Is there are any other ways ??
> Best Regards,
>
>
>
> >-----Original Message-----
> >Stephen,
> >
> >If you can restrict the application to Windows 2000, then
> you can use
> >Encrypted File System. For additional information, see
> section "Using
> >Encryption Methods" (adminsql.chm::/ad_security_93u6.htm)
> in the SQL Server
> >2000 Books Online.
> >
> >BTW, if you are concerned about the database schema, as
> opposed to the
> >actual data, then you are essentially out of luck. If a
> competitor can
> >purchase your product, then they can see your database
> schema.
> >
> >Bottom line: the protection of intellectual property is
> best addressed via
> >legal mechanisms rather than trying to rely upon
> technical solutions.
> >
> >-------------------------------------------
> >BP Margolin
> >Please reply only to the newsgroups.
> >When posting, inclusion of SQL (CREATE TABLE ...,
> INSERT ..., etc.) which
> >can be cut and pasted into Query Analyzer is appreciated.
> >
> >"Stephen Schmid" <steve_schmid@msn.com.au> wrote in
> message
> >news:446101c1fe10$f5c8bd70$9ee62ecf@tkmsftngxa05...
> >> How can I implement a security mechanism with a SQL
> Server
> >> database that protects me from someone copying the mdf
> >> file while the sql server is stopped?
> >> Once copied the database can be be simply attached on a
> >> separate server and they have it.
> >>
> >> Background: product for market about to launch using
> MSDE
> >> 2000 for DBMS. Win98 min OS level. Our competitiors
> would
> >> love to get their hands on our database schema and they
> >> will have access to the computer running our instance of
> >> MSDE 2000.
> >>
> >>
> >
> >
> >.
> >
- Next message: Sholana: "Recovery from Digispid.B.Worm"
- Previous message: Dave: "Recovery from Digispid.B.Worm"
- In reply to: Ayman: "Re: MDF file level security from copying"
- Next in thread: Ayman: "Re: MDF file level security from copying"
- Reply: Ayman: "Re: MDF file level security from copying"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
