From Dwayne Wright PMP, PMI-ACP, CSM
Certified FileMaker Developer
If you have a field, layout or script that has a higher level of security sensitivity about it, you may want to give it a name that suggests otherwise. If a hacker were to find a way to get into your FileMaker file, you want to make it as tough as possible to get to sensitive data. I’m not saying that you have to develop a sophisticated code for naming your design elements but just try to make them less obvious. As possible set of examples could be ...
Credit Card Number - change to cc
Social Security Number - change to sn
Password - pw
Developer - change to clean, maintenance
Show Status Area - change to Window Refresh
Log In - change to Internal Navigation
Delete Records / Delete All - change to clean up records
Bypass Security Settings - change to anything else!
I’m sure you can come up with better names. These are just a few examples of possible areas where you could have a common name and perhaps one less obvious to a potential hacker.
PLEASE NOTE - The changing of the name of one of these elements by all means does NOT make it secure. If you have these examples in your files, make sure they are protected by correctly using FileMaker’s account and privilege settings.
More info about the author and FileMaker in general, contact me at firstname.lastname@example.org.
© 2007 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.