Securing a Backend

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Tony

    Securing a Backend

    G'day, The derivation of a (commercially valuable) relational schema has
    taken me a considerable amount of time. Now I want to secure the design in
    a client server environment. Hence to my question: How have developers
    successfully prevented access to their data tables and protected their
    database design?

    Looking forward to some suggestions.
    Tony


  • Tom van Stiphout

    #2
    Re: Securing a Backend

    On Wed, 25 Aug 2004 01:02:23 GMT, "Tony" <ricecustard@ho tmail.com>
    wrote:

    Access (better: Jet) is not a client/server database.
    To secure a Jet database you have to understand there are cheap
    password crackers available. If you are not too concerned with them,
    then download, study, and fully understand the Access Security FAQ
    from microsoft.com. You'll learn that it is indeed possible to
    disallow anyone but your application access to the back-end tables.

    Personally I would not put too much value on a database design. The
    commercial value is likely not in the db design, but in the
    application using it. Keep the db open for your clients to access it
    as well, to create ad-hoc reports etc.

    -Tom.

    [color=blue]
    >G'day, The derivation of a (commercially valuable) relational schema has
    >taken me a considerable amount of time. Now I want to secure the design in
    >a client server environment. Hence to my question: How have developers
    >successfully prevented access to their data tables and protected their
    >database design?
    >
    >Looking forward to some suggestions.
    >Tony
    >[/color]

    Comment

    • Keith Wilby

      #3
      Re: Securing a Backend

      "Tony" <ricecustard@ho tmail.com> wrote:
      [color=blue]
      > How have developers
      > successfully prevented access to their data tables and protected their
      > database design?
      >[/color]

      *First* read and understand this:

      <http://support.microsoft.com/default...access%2fconte
      nt%2fsecfaq.asp >

      You can then deny user access to your tables if you base all of your forms
      & reports on queries with 'owner' access. Of course you can also hide the
      db windoow and close the 'back door' methods of unhiding it.

      You can also check out my step-by-step example on securing an Access app on
      my web site (there's all sorts of junk on there, use the LH nav panel to
      navigate to the Access area).

      Regards,
      Keith.

      Comment

      • John Wilde

        #4
        Re: Securing a Backend


        "Keith Wilby" <keith.wilby@Aw ayWithYerCrap.c om> wrote in message
        news:Xns9550650 4CE9E8keithwilb y@10.15.188.42. ..
        [color=blue]
        > Regards,
        > Keith.
        > www.keithwilby.org.uk[/color]


        Keith--

        Is that a naked picture of you on your Web site, or do I need to adjust my
        color?

        --JW


        Comment

        • Keith Wilby

          #5
          Re: Securing a Backend

          "John Wilde" <wildjohn@hotma il.com> wrote:
          [color=blue]
          > Keith--
          >
          > Is that a naked picture of you on your Web site, or do I need to adjust
          > my color?[/color]

          Erm, adjust your colour, the picture may be naked but I'm not ;-) I've been
          meaning to change that photo for a while. It was taken on holiday in
          Florida and I can assure you I have shorts on!

          Comment

          Working...