Requirements gathering for secure access and use of a generic grid

Currently we are seeking assistance to build a list of use-cases that will lead us towards a set of functional requirements for access management and security for a generic grid. (The 'generic grid' is a production grid, with production applications and a set of users with a wide variety of skills and interests.) We are trying to avoid any limitations with current technologies and to think clearly about requirements before considering technology. This is an early workpackage for the ESP-GRID project.

Bibliography

RequirementsBibliography

 * sources and references to articles and papers used in this Requirements gathering exercise 

Focus Group

FocusGroup

 * Notes and reports from the focus group meeting

Use Cases

UseCases

 * use cases for a generic grid 

Top-level requirements described below under:

Major references used (dominant to the rest)

>90% of our requirments could come from [wiki:RequirementsBibliography Shawn Mullen et al's] (2004) document on "Grid Authentication, Authorization and Accounting Requirements". Working document but good enough! (MN has emailed Shawn Mullen to ask if more work has been done since May 04. See the [wiki:RequirementsBibliography bibliography notes] for more details.


Grid AAA requirements (authentication authorisation and accounting, and auditing) described under:

Authentication AuthN

Include Note

identity, anonymity, pseudonimity (secure anonymous communication), credential lifespan and renewal (short-term credentials), assurance levels (SEE ALSO Operational Characteristics), revocation, policies, documentation, usability, trust (SEE ALSO Operational Characteristics) and responsibility, secure roaming

Insert definition here and requirements follow...

Authorisation AuthZ

Include Note

identity, grouping users/roles, authorisation levels, revocation, attributes, policies, 'transparency', privacy, logging, credentials, fault tolerance, delegation, XXXXmore...

Insert definition here and requirements follow...

Accounting

Include Note

accurate billing and metering, (operational costs, service levels), monitoring or logging, resource and end entity - secure logging, scheduling and resource management. SEE ALSO Grid Auditing

Insert definition here and requirements follow...

Auditing

Include Note

'Accounting as a security component', monitoring or secure logging (resource access decisions, policies, policy changes, resource implication of policies), audit logs, intrusion detection, forensics, diagnostics, audit trail (AuthN and AuthZ). SEE ALSO GridAccounting

Insert definition here and requirements follow...

General references on AAA(+A)

[wiki:RequirementsBibliography Manandhar et al] (2004) mention the 3 primary AuthZ frameworks: Community AuthZ Service (CAS) from the Globus project, Virtual Organization Management System (VOMS) from the EU Data grid project and PERMIS with respect to a "Grid Authorization Framework for CCLRC Data Portal".


Grid protection of data requirements described under:

Include Note

.

Privacy

Include Note

use of data, (supported by confidentiality mechanisms including AuthZ), significant for health data etc.

Definition and requirements follow...

Confidentiality

Include Note

supported by access control within systems and encryption between and within systems, signalling policies, supports privacy, protects sensitive data

Definition and requirements follow...

Integrity

Include Note

provenance (i.e. maintaining integrity of chains/groups of related data), message integrity

Definition and requirements follow...

Digital rights management (DRM)

Include Note

XXXX

Definition and requirements follow...

General references on Grid protection of data

[wiki:RequirementsBibliography Kalra et al] (2004) Pseudonymised repository of histories of cancer patients that can be accessed by researchers.


Grid operational characteristics described under:

Include Note

.

Trust

Include Note

between collaborative organisations, policy framework, infrastructure

Definition and requirements follow...

Performance and scalability

Include Note

delegation(policies and trust frameworks, virtual grids)

Definition and requirements follow...


Manageability incl. architectural components

Include Note

policies, identity management, intrusion detection, anti-virus (i.e. architectural components - others include platform security, system level security design, firewall traversal).

Definition and requirements follow...

Interoperability

Include Note

between grid environments, policies

Definition and requirements follow...

Assurance

Include Note

(is this the same as we understand?), security assurance level

Definition and requirements follow...


Other Requirements

Additional requirements which need a better home include:

.

Single log-on

Include Note

delegate an entity's rights subject to policy Defintion and requirements follow...

Policy exchange

Include Note

establish a negotiated security context

Defintion and requirements follow...