Developing a Security Plan

 <  Day Day Up  >  

Like the security assessment, a security plan needs to be developed after the structure of the database system is known. For existing systems, the structure is already known, but for new systems, the security plan needs to wait until the system structure plan is complete. As soon as all the tables and field structures have been determined, then you can go through that structure and determine the different levels of access that need to be used with each table and field.

System roles often match up well to job titles in an organization, but it often happens that two people with the same title need to have different roles within the system. Job titles are a good starting point for developing user categories, but don't overlook role differences just because two people have the same title.

You'll need to evaluate user categories in the context of each table. For example, members of a Sales category might need a high level of access in a Contacts table so that they can add, modify, and delete contacts, but they may have view-only access to an Accounts Receivable table. A great way to represent these table-by-table details of a security plan is to construct an access grid for each table. An example is shown in Table 12.1.

Table 12.1. Access Grid

User Category

Administrator

Manager

Sales

Accounting

Menu Access (Full, Editing Only, None)

Full

Full

Edit Only

Edit Only

Script Access (Yes, No, Limited)

Execute

Yes

Yes

Yes

Yes

Modify

Yes

No

No

No

Value List Access (Modifiable, View, None)

Modifiable

Modifiable

View

 

Record Access

View

Yes

Yes

Yes

Yes

Create

Yes

Yes

Yes

No

Edit

Yes

Yes

Limited

No

Delete

Yes

Yes

Limited

No

Field Access

Contact ID

Yes

Yes

No

No

First Name

Yes

Yes

Yes

Yes

Last Name

Yes

Yes

Yes

Yes

Address 1

Yes

Yes

Yes

Yes

Address 2

Yes

Yes

Yes

Yes

City

Yes

Yes

Yes

Yes

State

Yes

Yes

Yes

Yes

ZIP Code

Yes

Yes

Yes

Yes


After you've developed access grids for each table in the database system, you're ready to implement the security plan.

Start by first setting up the privilege sets you're going to need, then the accounts and the extended privileges. After those pieces are in place, you can create or modify scripts and calculations that test for the various security configurations.

 <  Day Day Up  >  


QUE CORPORATION - Using Filemaker pro X
QUE CORPORATION - Using Filemaker pro X
ISBN: N/A
EAN: N/A
Year: 2003
Pages: 494

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net