EASy Security Project

advertisement

Project Objectives

1.

Research a security incident using various resources.

2.

Use a standard (COBIT) to analyze a security incident.

3.

Recommend changes to improve the security of an organization supported by sound rationale.

4.

Create a basic plan of action to bring about recommended changes.

Project Overview & Components

The purpose of this project is to give experiences in research, analysis using a standard, recommending change based on sound rationale and creating a basic plan of action to bring about change for the better. Each group will select a known security incident and complete the following components via their wikis:

Evaluation and Selection of Security Incidents

Search and find 2 significant or newsworthy security incidents.

Incidents should be no older than 2000.

Can be a private or public organization.

Overview each of the 2 significant or newsworthy security incidents. Include: o

The name of the organization. o

The mission statement of the organization. o

The security incident o

Impacts of the incident

Select one of the organizations for analysis (First come; first served).

1

Created on September 22 nd

, 2008

Evan Sveum for TCS-401/601

Analysis of the Security Incident using COBIT (DS5: Ensure Systems Security)

Identify the elements / circumstances that contributed to the security incident using the following COBIT control objectives. It is likely that not all of the objectives will have a direct relationship with the security incident. However, each of the objectives, related to the incident, need to be addressed. The objectives include (See COBIT Student Book-Page 92 for details): o

5.1 Manage Security Measures o

5.2 Identification, Authentication and Access o

5.3 Security of Online Access to Data o

5.4 User Account Management o

5.5 Management Review of User Accounts o

5.6 User Control of User Accounts o

5.7 Security Surveillance o

5.8 Data Classification o

5.9 Central Identification and Access Rights Management o

5.10 Violation and Security Activity Reports o

5.11 Incident Handling o

5.12 Reaccreditation o

5.13 Counterparty Trust o

5.14 Transaction Authorisation o

5.15 Nonrepudiation o

5.16 Trusted Path o

5.17 Protection of Security Functions o

5.18 Cryptographic Key Management o

5.19 Malicious Software Prevention, Detection and Correction o

5.20 Firewall Architectures and Connections with Public Networks

2

Created on September 22 nd

, 2008

Evan Sveum for TCS-401/601

o

5.21 Protection of Electronic Value

Synthesis Through Recommended Changes in Control Practice

Make specific recommendations that would improve the security system. Recommendations should include a solid rationale based on the evidence provided via the Analysis of the Security

Incident using COBIT (DS5: Ensure Systems Security).

When making recommendations, please include a basic plan of action including cost, services provided and other reasonable planning details. The basic plan of action should include: o

People o

Procedures o

Hardware o

Software o

Telecommunications

Project Assessment

This project is worth 200 points overall. As you complete each portion of this project, please write a ½

page progress report & upload to appropriate drop boxes (see dropbox area). One progress report per group/per portion of the project (3 total)... See 'big yellow box/schedule' for due dates for each section of this project…

The following will be used to assess the completed project:

Project Criteria Points

Possible

Evaluation and Selection of Security Incidents (30 pts)

Searched and found 2 significant or newsworthy security incidents? Incidents no older than 2000?

Overview each of the 2 significant or newsworthy security incidents include:

The name of the organization?

The mission statement of the organization?

The security incident?

Impacts of the incident?

5

20

3

Created on September 22 nd

, 2008

Evan Sveum for TCS-401/601

Select one of the organizations for analysis?

Appropriate mix of media elements (more than just text)?

5

Analysis of the Security Incident using COBIT (DS5: Ensure Systems Security) (60 pts)

Identified the elements / circumstances that contributed to the security incident using the related / appropriate COBIT control objectives?

Synthesis Through Recommended Changes in Control Practice (60 pts)

60

Recommendations included a solid rationale based on the evidence provided via the

Analysis of the Security Incident using COBIT (DS5: Ensure Systems Security)?

Basic plan of action included cost, services provided and other reasonable planning details including:

People?

Procedures?

Hardware?

Software?

Telecommunications?

Wiki Formatting (50 pts)

Used an appropriate number of credible resources to build all elements of the project

(15 or more)?

Appropriate use of APA (Including Reference List & Parenthetical Citations)?

Note: Project will be considered

incomplete

if used incorrectly…

Easy to follow navigation to all project elements?

30

30

10

10

10

10

Instructor’s Impression?

10

Total Score

4

Created on September 22 nd

, 2008

Evan Sveum for TCS-401/601

Download