(DBWORLD) Call for Papers!

Srinivas Ganta (sganta@cygnacom.com)
Tue, 14 Jan 1997 19:52:54 -0600 (CST)

CALL FOR PAPERS
SECOND ACM WORKSHOP ON ROLE-BASED ACCESS CONTROL
http://www.list.gmu.edu/rbac.html
Date: November 6-7, 1997
Place: George Mason University

SPONSORED BY: ACM SIGSAC* and ACM Washington DC Chapter*
HOSTED BY: George Mason University

The central idea of Role-Based Access Control (RBAC) is that users
acquire and use permissions based on their current job functions,
assignments and activities in an organization. The driving motivation
for RBAC is to simplify security policy administration while
facilitating the definition of flexible, customized policies. RBAC
has been successfully applied since the mainframe era. Modern
information systems will continue to use classical RBAC models, but
the development of new modeling concepts and techniques will be
required to support large-scale, enterprise-wide, distributed systems.

The ACM workshop on RBAC brings together researchers, developers, and
practitioners to discuss new ideas, developments, applications,
requirements, problems, and solutions in the field of RBAC. The
workshop invites participation from the database, network, distributed
systems, operating system, security and application communities.=20
Attendance is limited to 40 participants to foster a workshop
atmosphere.

The inaugural workshop, held in November 1995, was successful in its
modest goal of taking a first step towards a consensus reference model
for RBAC. There was substantial agreement among attendees regarding
the general concepts that RBAC can represent. Yet, there were many
manifestations, elaboration=92s, and applications of these demonstrating
that RBAC is a rich and fruitful area for future work. Proceedings of
the first workshop are available from ACM.

Users, developers and researchers are invited to submit seven copies of
their papers (limit 7500 words) to the Program Chair at the address
given below before the due date. Papers must be original and should
not be under consideration for publication elsewhere. Copyrights for
accepted papers must be transferable to ACM (except for Government work).
Outstanding papers will be considered for publication in ACM=92s new=20
Transactions on Information and Systems Security (TISSEC). Proposals
for panels and group discussions should be sent, preferably by email, to =
the=20
Program Chair at ecoyne@seta.com. Proceedings of the workshop will be
published by ACM and will be distributed at the workshop.

Submissions should be sent to:
Ed Coyne
SETA Corporation
6862 Elm Street
McLean, Virginia, 22101-3833
Internet: ecoyne@seta.com

SCHEDULE:
Papers and Panel Proposals due: June 1, 1997
Notification of acceptance and advance program: July 15, 1997
Deadline for final version of papers: August 15, 1997
Workshop: November 6-7, 1997

REGISTRATION:
Information on registration and accommodations will be provided.
There will be a registration fee for all participants to cover meeting
costs. For further information about the workshop, contact Srinivas
Ganta at sganta@cygnacom.com or consult our web site.

CONFERENCE COMMITTEE:
Steering Committee Chair: Ravi Sandhu, George Mason University
General Chair: Charles Youman, SETA Corporation
Program Chair: Ed Coyne, SETA Corporation
Proceedings Chair: Trent Jaeger, IBM T.J. Watson Research Center
Local Arrangements and Publicity Chair: Srinivas Ganta, CygnaCom
Solutions Inc.

PROGRAM COMMITTEE:
David Ferraiolo, National Institute of Standards and Technology
Srinivas Ganta, CygnaCom Solutions, Inc.
Trent Jaeger, IBM T.J. Watson Research Center
LouAnna Notargiacomo, Oracle Corporation
Sylvia Osborn, University of Western Ontario
Steven Greenwald, Independent Consultant

* Pending Approval.

-------------------------------------------------------------------------------
The dbworld alias reaches many people, and should only be used for
messages of general interest to the database community.

Requests to get on or off dbworld should go to listproc@cs.wisc.edu.

to subscribe send
subscribe dbworld Your Full Name

to unsubscribe send
unsubscribe dbworld

to change your address
send an unsubscribe request from the old address
send a subscribe request from the new address

to find out more options send
help
------------------------------------------------------------------------FOOTER-