13.pdf

11
June 1, 2004 Computer Security: Art and Science ©2002-2004 Matt Bishop Slide #13-1 Chapter 13: Design Principles • Overview • Principles Least Privilege Fail-Safe Defaults Economy of Mechanism Complete Mediation Open Design Separation of Privilege Least Common Mechanism Psychological Acceptability

Upload: s-m-keerthana-muniappan

Post on 13-Apr-2015

16 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-1

Chapter 13: Design Principles

• Overview• Principles

– Least Privilege– Fail-Safe Defaults– Economy of Mechanism– Complete Mediation– Open Design– Separation of Privilege– Least Common Mechanism– Psychological Acceptability

Page 2: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-2

Overview

• Simplicity– Less to go wrong– Fewer possible inconsistencies– Easy to understand

• Restriction– Minimize access– Inhibit communication

Page 3: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-3

Least Privilege

• A subject should be given only thoseprivileges necessary to complete its task– Function, not identity, controls– Rights added as needed, discarded after use– Minimal protection domain

Page 4: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-4

Fail-Safe Defaults

• Default action is to deny access• If action fails, system as secure as when

action began

Page 5: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-5

Economy of Mechanism

• Keep it as simple as possible– KISS Principle

• Simpler means less can go wrong– And when errors occur, they are easier to

understand and fix• Interfaces and interactions

Page 6: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-6

Complete Mediation

• Check every access• Usually done once, on first action

– UNIX: access checked on open, not checkedthereafter

• If permissions change after, may getunauthorized access

Page 7: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-7

Open Design

• Security should not depend on secrecy ofdesign or implementation– Popularly misunderstood to mean that source

code should be public– “Security through obscurity”– Does not apply to information such as

passwords or cryptographic keys

Page 8: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-8

Separation of Privilege

• Require multiple conditions to grantprivilege– Separation of duty– Defense in depth

Page 9: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-9

Least Common Mechanism

• Mechanisms should not be shared– Information can flow along shared channels– Covert channels

• Isolation– Virtual machines– Sandboxes

Page 10: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-10

Psychological Acceptability

• Security mechanisms should not add todifficulty of accessing resource– Hide complexity introduced by security

mechanisms– Ease of installation, configuration, use– Human factors critical here

Page 11: 13.pdf

June 1, 2004 Computer Security: Art and Science©2002-2004 Matt Bishop

Slide #13-11

Key Points

• Principles of secure design underlie allsecurity-related mechanisms

• Require:– Good understanding of goal of mechanism and

environment in which it is to be used– Careful analysis and design– Careful implementation