Securing data on the Web

You should consider security for your FileMakerRPro databases whenever they can be accessed over any type of network, whether peer-to-peer or for access from a web browser. Design your databases with your security needs in mind. You might need to maintain public and private data in separate files with separate levels of access. For example, if you have a database that contains all of your customer data, including credit card and shipping information, this data is most secure if it is never shared over the Web. However, this can be impractical. If you want to shield your customers’ credit card information while making their shipping addresses available for verification, one method is to create a separate database containing all of your customer ID numbers. Create a relationship from this database to your master database, and display only the related fields that you want to expose to your customers. This secondary database can then be shared over the Web, while your master database can remain offline. Note: FileMaker Pro doesn’t provide password encryption. To provide security for your database passwords over the Web, consider installing Secure Socket Layer (SSL) protection, which is available from third-party vendors and supported by the FileMaker Pro Unlimited software’s Web Server Connector.

---

Table of contents :
Access privileges vs. the Web Security Database……Page 1
Protecting specific records using access privileges……Page 3
Additional details about limiting access on a record-by-record basis……Page 4
Security tips……Page 6
Custom Web Publishing using the Web Security Database……Page 7
How the Web Security Database works……Page 8
Enabling the Web Security Database……Page 9
Assigning Web Security to your databases……Page 11
Protecting specific records in a database using the Web Security Database……Page 13
Changing Web Security settings remotelyfrom the Web……Page 14
Web Security Database tips……Page 19