Designing an Account Policy
Joel Christensen
Rasmussen College

Author Note This research is being submitted on May 12th, 2013, for Christine Palazzolo N437
Our organization needs to develop and design an account policy that meets our administrator’s needs and are able to manage all users accessing information. The policy will discuss how users and groups will be assigned certain level of access. The policy should include audits and normal maintenance of user and group access. We will research a variety of policies to see which policy framework works best for our organization. These policies can and will be adaptable for revisions as business changes, laws, and regulations. When designing our account policy we will develop a seven tier architecture process this will include physics data, data access, entity, business logic, page structure, logic control, and page presentation. I chose the seven tiers over a three tier. The seven tiers divide the data access layer and the presentation layer into more detailed layers. Under Linux, a user can log into the system and use any applications or files they are permitted to access after a normal user account is created. Linux determines whether or not a user or group can access these resources based on the permissions assigned to them. There are three different permissions for files, directories, and applications. These permissions are used to control the kinds of access allowed. Different one-character symbols are used to describe each permission in a directory listing. The following symbols are used: * r — Indicates that a given category of user can read a file. * w — Indicates that a given category of user can write to a file. * x — Indicates that a given category of user can execute the contents of a file.
A fourth symbol (-) indicates that no access is permitted.
Each of the three permissions are assigned to three different categories of users. The categories are: * owner — The owner of the file or application. * group —