Pos/355 File Management

File Management Paper

Drew Lanto

POS/355

November 9, 2015

Bob O'Connor

File Management Paper

In this paper I will attempt to explain how to protect a file from being viewed or edited by those who you do not want to have access to the file. There are certain files you do not want everyone to have access to. So, it is important to make sure only those who need access have that access. In our scenario, we want to allow 4,990 out of 5,000 people to have access to this one file, all this being done in a UNIX based system.

A file system allows for organizing data storage for files, and what can be done with those files (William Stallings\University of Phoenix, 2015). UNIX files are owned by either an individual or a group. The file can be shared by giving permissions to the individuals or groups you want to have access to the file. In our scenario, we are choosing to give access to a group of people. There will specifically be ten people who will be restricted from having access to the file.

There are numerous options to give a user or group in creating a file system. You can give access to create a file, delete a file, open a file, close a file, read a file or write to a file.

The first step is to create a group. This group would include all the users needing access to the file. The administrator would be able to add or remove users from this group depending on whether the user requires access to the file.

Next is to give the user group certain access such as (William Stallings\University of Phoenix, 2015):

1. None – Users are not even aware of the file and cannot access it.

2. Knowledge – Users can see the file and who create it, but can only edit it after requesting the access.

3. Execution – Can open a file but cannot copy it.

4. Reading – Can open and execute the file.

5. Appending – Files can be opened and added to, but cannot delete or modify.

6. Updating – The user can modify the file, sort of like having...