On Nov 22, 2006, at 10:51 PM, Skeeve Stevens wrote:
> Those security issues are Human. I don't want the others - Network
> Admins
> having the ability to create/gain access to the FileMaker solution
> due to
> the sensitive nature of the content. My other option is to setup
> its own
> domain/ldap which they don't control, but due to policies that
> might be an
> issue.
Those "others" will have the ability to gain access to the solution
by virtue of the fact that they will have physical access to the files.
You can create an independent AD or OD domain on the server on which
FMS is installed but if those "others" have access to the machine
then they can get in there too. I have found that you need to have a
trust relationship with the network admins, otherwise access to your
solution is at their whim and fancy. They will probably be in charge
of the backup system as well, which provides them the ability to gain
a copy of the solution without your knowledge. One can then take that
copy home, run a password utility on it, and peruse the data to one's
heart's content.
If you need to secure sensitive data that no one should see except as
authorized then you will probably need to encrypt it. I believe Troi
Automatisering have a plug-in for that.
Corn Walker
Hatfield, MA
"Never speak more clearly than you think."
--
To unsubscribe: send an email to <
[hidden email]>
Archives:
http://www.nabble.com/FMPExperts-f735.htmlFMPexperts is hosted by Ironclad Networks <
http://www.ironclad.net.au/>