Re: How do I lock the unhide database window menu option?

I don't see it as glib ...

I meant with insufficient qualifying detail of course, not that you dont have
it!

it's pretty much common knowledge that Access/Jet security is really no
security at all, and
that SQL Server, Oracle, etc are far more secure. My comment was intended to
alert the poster that Access/Jet > is not a secure data store.

Perhaps in a direct comparison, there are two reasons a)Access passwords more
easily breakable b) SQL Server, whilst still "file-based", indeed has no
direct user-access to the file, or not in normal user circumstances.

But if a solution is implemented which is Internet/Intranet-based, the user
also does not have direct access to the files because there is no such
connection. They just have a .asp or like returning vetted data.

Therefore, in such circumstances (and ignoring IT personnel at the premises),
it wouldn't matter if the database was Access or SQL Server, or indeed no
ULS/password security at all for the data file itself?

Web-based (or "intranet-based") would depend entirely on some other
implemented user/password system, to do with the .asp?

But given not using intranet system/methodology (and I don't, yet), it seems
only true to say SQL Server is more secure than Access in SOME RESPECTS
(password cracking, obviously). It doesn't do much for abuse of allowed
access! Rick Brandt partially addresses this in his short statements (like,
depending on whether you want to protect from someone inside or outside the
organisation)

Whilst I fully appreciate the breakability of Access (god-knows I have a
history on the subject!), there are also cases where SQL Server improved
security is totally irrelevant. For example, in "shrink-wrapped" software my
concern is ripping off the software not the data! (the customer owns their
data not me) Well, in Access, the prog is just as easy to rip-off for sure
<guffaw>. And SQLServer does nothin' for me! However, quite clearly, I was
just making a point that there's a galaxy of reasons and practical
restrictions regarding what exactly security is for? Without knowing the
reasons and restriction criteria of the poster, I have no idea whether SQL
Server is a sensible suggestion or not!

To me, "sensitive info" means, say, what other similar employees may be
earning! Only the likes of accountants actually need that info. I wouldn't
rely on Access or SQLServer security. I'd put that in a SEPARATE
table/database which has RESTRICTED PHYSICAL ACCESS. (physical may mean the
restricted electronic paths to it)

Sensitive info...unfaithful love letters...oops I gotta go and check
something...

Thanks for a "robust" discussion! :-)
Chris


.

Relevant Pages

  • Re: SQL or Access DB
    ... As far as encryption goes though... ... with Sql Server you can use SQL DMO and encrypt your stored procedures ... installation - Security was absolutely critical and in most instances, ... > then we create a nice gui around this database and sell it to automotive ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Is there any way to prevent hacker trying to guess sa password?
    ... and port 1433 will not be open. ... If someone can crash SQL Server by connecting to port 1433, ... You don't need multiple security experts. ...
    (microsoft.public.sqlserver.security)
  • Re: Getting to the bottom of MSDE network connection problems ...
    ... Brilliant, Nick, especially the explanation for local network user being ... authenticated as GUEST in WinXP SP2. ... > on a desktop OS like XP (meaning that, you can not compare SQL Server ... > again and selected the security tab. ...
    (microsoft.public.sqlserver.msde)
  • [NT] SQL Extended Procedure Functions Contain Unchecked Buffers
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... SQL Server 7.0 and 2000 provide extended stored procedures, ... Several of the Microsoft-provided extended stored procedures have been ... Exploiting the flaw could enable an attacker to either cause the SQL ...
    (Securiteam)
  • RE: Login failed for user (null).
    ... used at signon to authenticate in SQL Server. ... connect the remote SQL Server database), is there any other data accessing ... What's the security identity used to access the remote SQL Server, ... the worker process identity. ...
    (microsoft.public.dotnet.framework.aspnet.security)