The Bell-LaPadula Model CSM27 Computer Security Dr Hans Georg - - PowerPoint PPT Presentation

the bell lapadula model
SMART_READER_LITE
LIVE PREVIEW

The Bell-LaPadula Model CSM27 Computer Security Dr Hans Georg - - PowerPoint PPT Presentation

The Bell-LaPadula Model CSM27 Computer Security Dr Hans Georg Schaathun University of Surrey Autumn 2008 Week 6 Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 Week 6 1 / 32 The session Outline The session 1 Finite


slide-1
SLIDE 1

The Bell-LaPadula Model

CSM27 Computer Security Dr Hans Georg Schaathun

University of Surrey

Autumn 2008 – Week 6

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 1 / 32

slide-2
SLIDE 2

The session

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 2 / 32

slide-3
SLIDE 3

The session

Session objectives

Be able to use the principle of finite automata to describe security models. Understand the confidentiality policy of Bell-LaPadula Understand the limitations of Bell-LaPadula

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 3 / 32

slide-4
SLIDE 4

Finite Automata

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 4 / 32

slide-5
SLIDE 5

Finite Automata

A finite automata

state-machine ≈ automata A set of states, Q An input alphabet Σ

labels for the state transitions

inital state q0 ∈ Q accepting states A ⊂ Q transition function δ : Q × Σ → Q

equivalent to the edges (arrows)

1 2 3 4 5 1 1 1 1 1 1

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 5 / 32

slide-6
SLIDE 6

Finite Automata

A finite automata

A state can be good or bad

secure or insecure

Transitions from good to bad states are dangerous. Two criteria

Start state be secure No transition from secure to insecure

1 2 3 4 5 1 1 1 1 1 1

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 6 / 32

slide-7
SLIDE 7

Finite Automata

A finite automata

A state can be good or bad

secure or insecure

Transitions from good to bad states are dangerous. Two criteria

Start state be secure No transition from secure to insecure

1 2 3 4 5 1 1 1 1 1 1

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 6 / 32

slide-8
SLIDE 8

Finite Automata

A finite automata

A state can be good or bad

secure or insecure

Transitions from good to bad states are dangerous. Two criteria

Start state be secure No transition from secure to insecure

1 2 3 4 5 1 1 1 1 1 1 1

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 6 / 32

slide-9
SLIDE 9

Bell-LaPadula

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 7 / 32

slide-10
SLIDE 10

Bell-LaPadula

The principle of an automata model

1

Describe all secure states

2

Describe transitions from secure states

3

Prove that no transition leads from secure to insecure If this is possible, the system is provably secure. Bell-LaPadula is one description of secure states. Similar principles apply to e.g. database development

Database has to be maintained in a consistent state No operation (transition) allowed to bring the database to an inconsistent state

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 8 / 32

slide-11
SLIDE 11

Bell-LaPadula

Elements of Access Control

a set of subjects S a set of objects O set of access operations A = {execute, read, append, write} A set of security levels L, with a partial ordering ≤

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 9 / 32

slide-12
SLIDE 12

Bell-LaPadula

The State Set

A state : (b, M, f), includes Access operations currently in use b

List of tuples (s, o, a), s ∈ S, o ∈ O, a ∈ A.

Access permission matrix

M = (Ms,o)s∈S,o∈O, where Ms,o ⊂ A

Clearance and classification f = (fS, fC, fO)

fS : S → L maximal security level of a subject fC : S → L current security level of a subject (fC ≤ fS) fO : O → L classification of an object

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 10 / 32

slide-13
SLIDE 13

Security Properties

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 11 / 32

slide-14
SLIDE 14

Security Properties

Simple Security Property (SS-property)

A state (b, M, f) satisfies the SS-property if

∀(s, o, a) ∈ b, such that a ∈ {read, write} fO(o) ≤ fS(s)

I.e. a subject can only observe objects of lower classification

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 12 / 32

slide-15
SLIDE 15

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-16
SLIDE 16

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-17
SLIDE 17

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-18
SLIDE 18

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-19
SLIDE 19

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-20
SLIDE 20

Security Properties

What about write access?

What policy do we need for write access? Integrity: no write-up (to higher security levels) Confidentiality: no write-down (to lower security levels) Bell-LaPadula concerns confidentiality Subject must not transmit messages to subjects at lower levels Current security level allows communications

A subject has to be downgraded to send messages

Because subjects are computer programs

they can be made to forget their knowledge when downgraded

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 13 / 32

slide-21
SLIDE 21

Security Properties

*-property

A state (b, M, f) satisfies the *-property if

∀(s, o, a) ∈ b, such that a ∈ {append, write} fC(s) ≤ fO(o)

and

if ∃(s, o, a) ∈ b where a ∈ {append, write}, then ∀o′, a′ ∈ {read, write}, such that (s, o′, a′) ∈ b fO(o′) ≤ fO(o)

I.e. a subject can only alter objects of higher classification, and cannot read a high-level object while writing to a low-level

  • bject.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 14 / 32

slide-22
SLIDE 22

Security Properties

Discretionary Security Property

Previous security properties provide Mandatory Access Control

i.e. a centrally defined access policy

The security levels are defined by a central policy Discreationary Access Control (DAC) decentralises the control The access control matrix M allows DAC in Bell-LaPadula A state (b, M, f) satisfies the DS-property if

∀(s, o, a) ∈ b a ∈ Ms,o.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 15 / 32

slide-23
SLIDE 23

Security Properties

Discretionary Security Property

Previous security properties provide Mandatory Access Control

i.e. a centrally defined access policy

The security levels are defined by a central policy Discreationary Access Control (DAC) decentralises the control The access control matrix M allows DAC in Bell-LaPadula A state (b, M, f) satisfies the DS-property if

∀(s, o, a) ∈ b a ∈ Ms,o.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 15 / 32

slide-24
SLIDE 24

Security Properties

Discretionary Security Property

Previous security properties provide Mandatory Access Control

i.e. a centrally defined access policy

The security levels are defined by a central policy Discreationary Access Control (DAC) decentralises the control The access control matrix M allows DAC in Bell-LaPadula A state (b, M, f) satisfies the DS-property if

∀(s, o, a) ∈ b a ∈ Ms,o.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 15 / 32

slide-25
SLIDE 25

Security Properties

Discretionary Security Property

Previous security properties provide Mandatory Access Control

i.e. a centrally defined access policy

The security levels are defined by a central policy Discreationary Access Control (DAC) decentralises the control The access control matrix M allows DAC in Bell-LaPadula A state (b, M, f) satisfies the DS-property if

∀(s, o, a) ∈ b a ∈ Ms,o.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 15 / 32

slide-26
SLIDE 26

Limitations

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 16 / 32

slide-27
SLIDE 27

Limitations

The Criticism of McLean

What happens if we . . .

downgrade all subjects to lowest security level downgrade all objects to lowest security level enter all access rights in the ACM M

Is the system secure? It satisfies every security property of BLP!

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 17 / 32

slide-28
SLIDE 28

Limitations

The Criticism of McLean

What happens if we . . .

downgrade all subjects to lowest security level downgrade all objects to lowest security level enter all access rights in the ACM M

Is the system secure? It satisfies every security property of BLP!

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 17 / 32

slide-29
SLIDE 29

Limitations

The sides of the conflict

A system which can be brought to a state with no restrictions cannot be secure. McLean This is application dependent. If the users need it, it should be possible. Otherwise it should not be implemented. Bell

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 18 / 32

slide-30
SLIDE 30

Limitations

Tranquility

McLean’s scenario is really out of scope for BLP BLP considered tranquil systems,

where permissions do not change

Either a system or an operation may be tranquil

A tranquil operation does not change access rights. A tranquil system has no non-tranquil operations.

Tranquility is a particular concern when

  • peration tries to remove an access right currently in use

How should this be resolved?

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 19 / 32

slide-31
SLIDE 31

Limitations

Covert Channels

Low-level subject sl creates object o High-level accomplice sh either

reclassifies o to its own level (Message 1) leaves o unchanged (Message 0)

sl tries to access o, which is either

success (Message 0) access denied (Message 1)

One bit of information is transmitted sh → sl

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 20 / 32

slide-32
SLIDE 32

Limitations

Covert Channels

Low-level subject sl creates object o High-level accomplice sh either

reclassifies o to its own level (Message 1) leaves o unchanged (Message 0)

sl tries to access o, which is either

success (Message 0) access denied (Message 1)

One bit of information is transmitted sh → sl

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 20 / 32

slide-33
SLIDE 33

Limitations

Covert Channels

Low-level subject sl creates object o High-level accomplice sh either

reclassifies o to its own level (Message 1) leaves o unchanged (Message 0)

sl tries to access o, which is either

success (Message 0) access denied (Message 1)

One bit of information is transmitted sh → sl

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 20 / 32

slide-34
SLIDE 34

Limitations

Covert Channels

Low-level subject sl creates object o High-level accomplice sh either

reclassifies o to its own level (Message 1) leaves o unchanged (Message 0)

sl tries to access o, which is either

success (Message 0) access denied (Message 1)

One bit of information is transmitted sh → sl

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 20 / 32

slide-35
SLIDE 35

Limitations

Limitations

BLP’s concern is confidentiality

limits the access and sharing of information no integrity policy no availability policy

BLP assumes a fixed rights

assumes tranquility no model for access management no model for policy making

Allows Covert Channels

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 21 / 32

slide-36
SLIDE 36

Multics

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 22 / 32

slide-37
SLIDE 37

Multics

What and when was Multics?

Massive research project in early 70-s Objective: Secure, reliable, etc multiuser OS

i.e. Multics

The Bell-LaPadula model was a result of the research The ambitions made Multics too heavy-weight for most

Unix is a spin-off by some project members simpler and more user-friendly,

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 23 / 32

slide-38
SLIDE 38

Multics

Objects

Objects : memory segments, I/O devices, et c.

hierarchically organised in directory tree information stored in parent directory

Access Control List (ACL) representing M Security level (classification) fO

Access to an object traverses path from root

Access requires access to all ancestors Low-level object in high-level directory makes little sense

Compatibility: Every object has security-level dominating that of the parent directory

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 24 / 32

slide-39
SLIDE 39

Multics

Objects

Objects : memory segments, I/O devices, et c.

hierarchically organised in directory tree information stored in parent directory

Access Control List (ACL) representing M Security level (classification) fO

Access to an object traverses path from root

Access requires access to all ancestors Low-level object in high-level directory makes little sense

Compatibility: Every object has security-level dominating that of the parent directory

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 24 / 32

slide-40
SLIDE 40

Multics

Objects

Objects : memory segments, I/O devices, et c.

hierarchically organised in directory tree information stored in parent directory

Access Control List (ACL) representing M Security level (classification) fO

Access to an object traverses path from root

Access requires access to all ancestors Low-level object in high-level directory makes little sense

Compatibility: Every object has security-level dominating that of the parent directory

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 24 / 32

slide-41
SLIDE 41

Multics

Subjects

Subject = process

Descriptor segment describes the process, its rights, and its accesses Segment Descriptor Word (SDW) [representing b] for each object currently accessed segment-id ptr r: on e: off w: one

fC : Current-level table fS : Process-level table active segment table : which processes are active

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 25 / 32

slide-42
SLIDE 42

Multics

Translating policies

Every parameter of the BLP state

has a representation in Multics data fields

Security policies can be rephrased,

referring to Multics data fields

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 26 / 32

slide-43
SLIDE 43

Multics

Translating policies

Every parameter of the BLP state

has a representation in Multics data fields

Security policies can be rephrased,

referring to Multics data fields

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 26 / 32

slide-44
SLIDE 44

Multics

Example: The SS-property

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 27 / 32

slide-45
SLIDE 45

Multics

Kernel primitives

Kernel primitives ∼ state transitions

release_read give_read create_object delete_object revoke_read change_subject_current_security_level

Ideally CPU instructions and OS kernel primitives match

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 28 / 32

slide-46
SLIDE 46

Multics

Kernel primitive: get_read

Example: get_read

Subject s wants to read object o so s asks OS to add (s, o, read) to b

The OS has to check this with the security policy, i.e.

The ACL of o includes (s, read) fO(o) ≤ fS(s) Either

fO(o) ≤ fC(s); or Subject s is trusted.

Access permitted if and only if all three conditions are met.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 29 / 32

slide-47
SLIDE 47

Conclusion

Outline

1

The session

2

Finite Automata

3

Bell-LaPadula

4

Security Properties

5

Limitations

6

Multics

7

Conclusion

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 30 / 32

slide-48
SLIDE 48

Conclusion

Multics and security models

The state-machine is an effective model of a computer system Bell-LaPadula describes secure states and transisions If all transitions (and starting state) are secure, the system has to be secure In multics,

data-fields correspond to state parameters kernel primitives correspond to transitions

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 31 / 32

slide-49
SLIDE 49

Conclusion

Exercise sheet

Write a short essay stating your position in the Bell vs McLean debate. It is helpful to address as many of the strengths and weeknesses of BLP as possible, in order to build an argument for your view. Suggested length 1

2-2 pages. Longer is not necessarily better.

Dr Hans Georg Schaathun The Bell-LaPadula Model Autumn 2008 – Week 6 32 / 32