discussing developing secure systems with umlsec 15 feb 2006 - joe combs
DESCRIPTION
Introducing UMLSec Extension of Unified Modeling Language - de-facto standard for OO development Attempt to encapsulate & make available to developers knowledge on prudent security engineering Encapsulation and modularity makes OO systems very well suited to considering securityTRANSCRIPT
![Page 1: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/1.jpg)
Discussing “Developing Secure Systems with UMLSec”
15 FEB 2006 - Joe Combs
![Page 2: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/2.jpg)
What Problem are we Trying to Solve?Blindly inserting security mechanisms into a
system doesn’t work
Need to bring efforts to mitigate these design limitations before system is actually implemented
![Page 3: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/3.jpg)
Introducing UMLSec• Extension of Unified Modeling
Language - de-facto standard for OO development
• Attempt to encapsulate & make available to developers knowledge on prudent security engineering
• Encapsulation and modularity makes OO systems very well suited to considering security
![Page 4: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/4.jpg)
UML Diagrams of Interest• Use Case - typical interaction between user and system
• Activity - workflow modeling/detailed explanation of use case
• Class - static structure of the system
• Interaction - sequence or collaboration diagram describes interaction between objects via message exchange
• State Chart - dynamic component behavior within an object
• Package - groups parts of a system into higher level units
• Deployment - describes physical arrangement in a real-world instance
![Page 5: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/5.jpg)
UMLSec Notation• Stereotypes
• <<stereotype>>• Extensibility mechanism used to create meta-information
about an entity in the diagram
• Tag-Value Pairs• {tag,value}• Extensibility mechanism to describe a property of a model
element
![Page 6: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/6.jpg)
Use Case Diagram
<<fair exchange>>: if “buys goods” then eventually “sells goods”
![Page 7: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/7.jpg)
Activity Diagram
Solution on right gives fair exchange if payment is <<provable>>
![Page 8: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/8.jpg)
Class Diagram
Ensure class structure provides data security
Key::newkey() guarantees confidentiality & integritybut random does not!
![Page 9: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/9.jpg)
Interaction Diagram
•Purchase system sends Init message to access card passing a session key signed with M’s private key and encrypted with C’s public key
•C decrypts the session key with its private key and verifies signature with M’s public key
•Once session key has been verified in this way, C can encrypt and send secrets using the session key and pass to M on the Resp message
![Page 10: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/10.jpg)
State Chart Diagram
Ensure behavior within a component - access control, database security, etc.
Transition labels:•events - message called on this object•[conditions] - must be true for transition to fire•\actions - carried out if transition fires
![Page 11: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/11.jpg)
Package Diagram
Uses visibility of parts within packages to reason about access privileges
![Page 12: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/12.jpg)
Deployment Diagram
Express security requirements on physical layer of the system:•communication links•hardware security•etc.
![Page 13: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/13.jpg)
Security Patterns
Operation rx() leaks information on the account balance
![Page 14: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/14.jpg)
The Wrapper Pattern
Ensures no low read after a high write
![Page 15: Discussing Developing Secure Systems with UMLSec 15 FEB 2006 - Joe Combs](https://reader035.vdocuments.site/reader035/viewer/2022062908/5a4d1b957f8b9ab0599c33a8/html5/thumbnails/15.jpg)
Now What?• UMLSec provides a mechanism for
communicating security concerns, bringing security up to the requirements and design phases of the lifecycle
• Where can this go from here?• Incorporate UMLSec notation for association,
generalization, etc.• Formal methods approaches?