Skip to main content
Sign In |
  Help (new window)

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Identify Security Objectives (Create a Quality of Service Requirement)  

Activity - Identify Security Objectives (Create a Quality of Service Requirement)

View All Site Content

Recent Changes
Activity Information

Identify Security Objectives

Create a Quality of Service RequirementIdentify Security Objectives

Description

Overview:

Security objectives determine the levels to which the solution will protect itself and its assets. There may be data that needs to be protected, regulatory requirements, or intangible assets such as company reputation, trade secrets, or intellectual property. Security objectives should be specific, testable statements about what is to be protected. They should not specify how. Security objectives usually start with a "verb" such as "Prevent unauthorized users from obtaining account information for our customers". The asset should be clearly identified.

Roles

PerformerBusiness Analyst
AssistantsArchitect

Attributes

CategoriesMSF Agile Principles - Partner with Customers, Iteration, MSF Agile Principles - Establish Clear Accountability, Build, Security, AI2.4 Application Security and Availability, AI1.1 Def and Maintenance of Business Func and Tech Requirements

Steps

  1. Document the Security Objective:
    Add a description of the security objective in the description field of the quality of service requirement work item. Be sure that the security objective refers to a specific asset and is testable. Leave design to the architects and developers.

    If the brief description is not sufficient for complete understanding, write a more detailed form, providing goals and rationale. Clarify an vague or ambiguous areas of the objective.

  2. Attach Supporting Information:
    Attach any references to regulatory information where applicable. Attach any scenarios that relate to the security objective. If the security objective affects all of the scenarios or a majority of them, simply note this rather than attaching very large numbers.

Inputs and Outputs

WorkProductInputOutputAllowable States
Quality of Service RequirementActive

Successors

TypeNameDependency Type
Divide Quality of Service Requirements into TasksFinish-Start

Last modified at 1/17/2008 11:18 PM  by Administrator