Ipsum

Course Project: Mobile Device Security

Introduction

Your instructor will assign teams of three or four collaborating students. Each student will be responsible for an equal portion of the segmented Course Project. In Week 7, the project will be due and submitted by the team, along with a recording describing the project research and resulting network topology and morphology using a virtual tool like WebEx or Kaltura. The finished project document and team recording will be uploaded for grading by the course instructor.

This project provides an opportunity for students to survey current mobile security fundamentals within the context of a business or academic IT infrastructure that adds value to an organization.

Guidelines

Week 1—Topic

Begin thinking of mobile device security in a business situation. Select a fictional or real corporate or university environment that requires mobile access. Use the Q & A Forum to ask questions and discuss your ideas about the project.

Week 3—Proposal

Course Project Proposal (one to two pages, 35 points). Remember to properly cite any external sources used.

The proposal should contain the following items.

1. Cover page

2. Subject of the Course Project

3. Name of the company or organization

4. Brief description of the company chosen

· Value proposition of the company

· Size of the workforce (students included if the company chosen is an academic institution) with respect to IT infrastructure needs

· Overview of the different types of mobile networks available in the company

· Overview of types of mobile devices and storage media used in the company

· Identification of potential mobile security risks

5. Audience to whom you are presenting the recommendation(s)

6. References

Week 7

Technical Report (four to five pages, 65 points). Remember to properly cite any external sources used. The technical report should contain the following items.

1. Cover page

2. Introduction

3. Intentional versus unintentional mobility scenarios in the company

4. Protection of data

· Physical protection mechanisms

· Logical protection mechanisms

· Protecting heterogeneous information

· Protecting data in motion

· Data protection models

· Using a device-centric or data-centric model for the case study; which one is better?

· Encryption

· Types of encryption employed by the company's IT department

· Defense or countermeasures

· Auditing

· Deterrent controls

· Preventive controls

· Portable computer controls

· Smartphones and PDAs

· E-mail protection

· Conclusion

· References

Grading Rubric

Category	Proposal Points	Technical Report Points	%	Description
Documentation and Formatting	5	10	15	A quality paper will include a title page, abstract, proper citations using APA style, and a bibliography.
Organization and Cohesiveness	7	10	20	A quality paper will include an introduction based on a well-formed thesis statement. The logical order of the content will be derived from the thesis statement. The content will be properly subdivided into sections derived from the outline. In a quality paper, the conclusion will summarize the previously presented content and will complement the thesis statement from the introduction.
Editing	5	10	15	A quality paper will be free of any spelling, punctuation, or grammatical errors. Sentences and paragraphs will be clear, concise, and factually correct.
Content	18	35	50	A quality paper will have significant scope and depth of research to support any statements. Strategic implications will be explained and supported. Relevant illustrations or examples are encouraged. A quality paper will employ use of sound reasoning and logic to reinforce conclusions.
Total	35	65	100	A quality paper will meet or exceed all of the above requirements. All sections in the table of contents must be in the project to earn full credit.

Best Practices

1. The proposal must be submitted and feedback received from the professor before beginning the project.

2. The project should follow APA style for citing references in the text and on the bibliography page. No fewer than five references must be used for research, and they must be properly cited.

3. Credible reference sources are available through the DeVry Library and other sources.

4. The Technical Report paper must be no less than five to six pages in length, double-spaced, using a size 12 standard business font, and using one-inch margins and topic headings listed for the format requirements.