Creating Security Mechanism Aspect Models from Abstract Security Aspect Models

1
Creating Security Mechanism Aspect Models from
Abstract Security Aspect Models
Geri Georg, Robert France, Indrakshi
RayDepartment of Computer Science, Colorado
State University
2

• The AOM program at Colorado State University
• focus on design goals that cross-cut a primary
  functionality design
• develop techniques that support model
  composition for the purpose of complete model
  analysis to
• identify cross-cutting goal conflicts
• identify conflicts between primary functionality
  and cross-cutting goals
• identify the best potential design realization
  of a particular goal

3
Multiple Levels of Abstraction

• different kinds of conflicts can be identified
• high levels of abstraction relation conflicts,
  multiplicity conflicts
• lower levels of abstraction degree to which
  goals are realized
• make trade-off decisions between multiple design
  realizations
• e.g. choosing an optimal mechanism for access
  control given an already chosen authentication
  mechanism

4
Abstract Authentication Aspect
static diagram of a 2-way authentication aspect
behavioral diagram of a 2-way authentication
aspect

• 2-way authentication
• two entities authenticate each other before
  communication is established
• authentication occurs in parallel

5
Secure Remote Password (SRP) Mechanism

• Static diagram of SRP
• classes and methods correspond to classes and
  methods of the abstract aspect static diagram
• creation of the diagram is not yet a formal
  refinement this is an area of on-going research

6
Secure Remote Password (SRP) Mechanism
Dynamic diagram of SRP
7
Conclusions

• model analysis at multiple levels of
  abstraction
• help find different kinds of conflicts
• enable design realization trade-off analysis in
  areas such as security where there are many
  possible mechanisms that deliver similar design
  goal realization at an abstract level
• it is possible to create more detailed models
  from abstract aspect models
• more formal algorithms are needed
  before automation is feasible
• notation conventions will be necessary to
  deal with mathematical versus modeling notation
  conflicts