Security Rationale of Grid Data Management Systems Security Requirements Analysis, Derivation of Security Policies, and Rationale of Security Services

Transcription

1 Security Rationale of Grid Data Management Systems Security Requirements Analysis, Derivation of Security Policies, and Rationale of Security Services Syed Naqvi 1,2, Philippe Massonet 1, Alvaro Arenas 2 1 Centre of Excellence in Information and Communication Technologies (CETIC) {Syed.Naqvi, Philippe.Massonet}@cetic.be 2 CCLRC Rutherford Appleton Laboratory {S.Naqvi, A.E.Arenas}@rl.ac.uk

2 Definition of Requirement In engineering, a requirement is a singular documented need of what a particular product or service should be or do. It is most commonly used in a formal sense in complex systems. In systems engineering, a requirement is a description of what a system must do. This type of requirement specifies something that the delivered system must be able to do. A security requirement is complementary to the functional requirement of a system. It should be based on an analysis of assets and services to be protected and the security threats from which these assets and services should be protected. 2

3 Grid Security Policy Local Security Policy (P L ) Application policy, Access Control Policy, Data Integrity Policy, Authentication Policy, Encryption Policy Global Security Policy (P G ) Defines general security policy of VOs Provides abstraction (virtualization) of all P L s P L1 P L2 Features Flexible policy-based access control mechanisms P G Inter-domain access control policies Secure group communication Delegation mechanisms to support scalability to large numbers of resources and users P L3 3

4 Security Rationale A rationale is a reasoned argument made to justify a course of action A security rationale shows how the security functional requirements from the Security Target are instantiated by the security enforcing entities. Security Rationale is like a checklist to verify that all security requirements are adequately addressed! 4

5 CC Example of Security Rationale 5

6 Functional View of Grid Data Management taken from Application Planner: Data location, Replica selection, Selection of compute and storage nodes Executor: Initiates data transfers and computations Metadata Service Replica Location Service Information Services Security and Policy Data Movement Data Access Location based on data attributes Location of one or more physical replicas State of grid resources, performance measurements and predictions Compute Resources Storage Resources 6

7 G3S: Grid Security Services Simulator First Simulator of Grid Security Services Provides interactive simulations for the Grid security functionalities Developed at Télécom Paris under the auspices of EU funded project SEINIT (Security Expert Initiative) Extension (Health Service Perspective) underway at the School of Mathematics, Statistics and Computer Science of Victoria University of Wellington (New Zealand) 7

8 G3S: Grid Security Services Simulator Open source code Developed in Java Can be executed as a standalone software Provides user friendly GUI Does not require knowledge of programming languages Can be integrated on the top of GridSim GridSim is a simulation toolkit for resource modelling and application scheduling for Parallel and distributed computing Some pervasive features are also included Automatic invocation of pre-requisite services 8

9 GridSim G3S Core Secure Document Exchange SecurityPolicy TrustManagement Attack Simulation 9

10 10

11 DEMO 11