U4. Security Models & Policy

Description

Masters Comp Sec Mind Map on U4. Security Models & Policy, created by Craig Parker on 13/11/2013.
Craig Parker
Mind Map by Craig Parker, updated more than 1 year ago
Craig Parker
Created by Craig Parker over 10 years ago
32
0

Resource summary

U4. Security Models & Policy
  1. Policy
    1. Policy= captures the requirements and describes the steps to be taken to achieve security
      1. Organisatonal Security Policy
        1. Rules that regulate how an organisation manages security
          1. Must be well defined
        2. Automated Security Policy
          1. Restrictions & properties that specify how a computing system prevents violations of the organisational security policy
        3. Models
          1. Models = an 'idealised' implementation of an organisation’s security policy.
            1. Models enforce the Access Control Structure policy and ensure "need to know"
              1. Models allow formal validation of your implementation against the security policy. Benchmarking
              2. Can be used to illustrate the Fundamental Design Principles
              3. State Machine Model (automaton)
                1. an abstract model that records relevant features of a system (IE: its security) at a particular point in tim
                  1. A state may change to another state at some later point in time, triggered possibly by a clock or some input event
                    1. movement from one state to another is known as a transition
                      1. the more states you try capture, the more complicated the model will become (more difficult to analyse).
              4. Basic Security Theorem
                1. If we can do these 3 things then we know that 'security' is preserved by all transitions and so the system will always be secure
                  1. 1. Define the State Set so that it captures some aspect of 'security
                    1. 2. Check that every state transition that begins in a 'secure' state ends in a 'secure' state
                      1. 3. Check that the initial state of the system is 'secure'.
                        1. Ensure you define what "secure" is!
                      Show full summary Hide full summary

                      Similar

                      U2.1 Comp Sec: deals with prevention & detection of unauthorised actions by users of a comp system
                      Craig Parker
                      U3.2 Access Control Structures
                      Craig Parker
                      U3. Labels & Access Control
                      Craig Parker
                      U2.2 Fundamentals
                      Craig Parker
                      U3.1 Access Control
                      Craig Parker
                      U3.3 Administration
                      Craig Parker
                      U4. Bell-LaPladula
                      Craig Parker
                      U4. Biba
                      Craig Parker
                      U4. Further Aspects of BLP
                      Craig Parker
                      U4. Harrison–Ruzzo–Ullman
                      Craig Parker
                      U4. Chinese Wall
                      Craig Parker