From: keefe@pacific.cmpe.psu.edu (Thomas F. Keefe)
Newsgroups: comp.security.misc
Subject: WG11.3 7th WC - Conference Dates
Date: 7 Nov 92 18:33:13 GMT
Organization: Penn. State
X-Xxmessage-Id: <A72175E6D101430F@tfkece.cmpe.psu.edu>
X-Xxdate: Sat, 7 Nov 92 13:32:22 GMT
X-Useragent: Nuntius v1.1.1d12

The dates of the 1993 IFIP WG 11.3 Working Conference
on Database Security have been changed to limit 
its interference with Rosh Hashanah (Sept. 16th).
The new dates are Sept. 12-15. The updated call
for papers is given below.

Thomas F. Keefe
----------------------------------------------------






         THE SEVENTH ANNUAL IFIP WORKING GROUP 11.3
          WORKING CONFERENCE ON DATABASE SECURITY

        Huntsville, Alabama, 12 - 15 September 1993

           Sponsored by IFIP Working Group 11.3

                      CALL FOR PAPERS

IFIP Working Group 11.3 has the following Aim and Scope:
     To advance technologies that support

          *    the statement of security requirements for  database
               systems,

          *    the design, implementation, and operation  of  data-
               base systems that include security functions, and

          *    the assurance that implemented database systems meet
               their security requirements.

     To promote wider understanding of  the  risks  to  society  of
     operating  database  systems  that  lack adequate measures for
     security or privacy.

     To  encourage  the  application  of  existing  technology  for
     enhancing the security of database systems.

The Working Group maintains a list of current research questions in
database  security to help frame its work.  This list is summarized
below.

     The purposes of this Working Conference are to present  origi-
nal  results in database security research and development, to dis-
cuss in depth the current state of research and practice  in  data-
base security, to enable participants to benefit from personal con-
tact and expand their knowledge, to support the activities  of  the
Working Group, and to disseminate the results of the discussion.

     Papers will be refereed by members of the  Working  Group  and
will be selected based on technical merit and their relationship to
the Aim and Scope.  The meeting will be organized to provide  ample
time  for  discussions,  both  formal  and  informal, of the papers
presented and of the research questions. Meeting attendance will be
limited to about forty participants.

                          CONFERENCE SITE

     The conference will be held at  the  Lake  Guntersville  State
Park Lodge, which is located on the top of Little Mountain and com-
mands a magnificent view of the 66,470 acre (26,910 hectare)  lake.
Available park activities include swimming, tennis, golf as well as
hiking within the heavily wooded 5,559 acre  (2,250  hectare)  park
that  ranges from mountain top to lake shore.  Within a short drive
of the lodge can be found the worlds largest collection  of  flying
replicas  of World War I aircraft at Lake Guntersville Aero as well
as one of the largest collections of outlet stores in the  country,
at  the  nearby town of Boaz. The lodge is located in northern Ala-
bama about 50 miles (80 km) east of Huntsville, which is the  loca-
tion  of  the  Alabama Space and Rocket Center (the world's largest
space center) and NASA's Marshall Space Flight Center.

                      INFORMATION FOR AUTHORS

     Authors are cordially invited to submit four copies  of  their
contributions  to Thomas F. Keefe at the address below. Submissions
should be received by April 9,  1993  and  must  not  exceed  8,000
words.  Complete details regarding the workshop will be sent to all
participants along with acceptance/rejection letters  by  June  14,
1993.  Final  papers  must be received in camera-ready form by July
16, 1993.  Conference proceedings will be edited and  published  by
North-Holland.

                 FOR FURTHER INFORMATION, CONTACT:

PROGRAM CHAIR

Thomas F. Keefe
Dept. of Electrical and Computer Eng.
18 Kathryn Bldg.
The Pennsylvania State Univ.
Univ. Park, PA 16802
U. S. A.
+1(814)865-9233 (voice)
+1(814)865-0192 (fax)
keefe@pacific.cmpe.psu.edu

GENERAL CHAIR

Thomas H. Hinke
Computer Science Dept.
University of Alabama in Huntsville
Computer Science Bldg.
Huntsville, AL 35899
U. S. A.
+1(205)895-6455 (voice)
+1(205)895-6239 (fax)
thinke@cs.uah.edu

IFIP WG11.3 CHAIR

Carl E. Landwehr
Naval Research Lab.
Code 5542
4555 Overlook Ave., SW
Washington, DC 20375-5000
U. S. A.
+1(202)767-3381 (voice)
+1(202)404-7942 (fax)
landwehr@itd.nrl.navy.mil

             SUMMARY OF RESEARCH QUESTION LIST


1.  What are good  techniques  for  describing  the  various
factors  involved in designing secure database systems, such
as:


     *    security and privacy policies or  policy  require-
          ments,

     *    threats to system security,

     *    costs/benefits of  meeting  security  and  privacy
          requirements (or risks of not meeting them)?


What relationships should exist between  these  descriptions
and  those already associated with database systems, such as
queries, views, and schemas?


2.  What are good methodologies for:


     *    obtaining these descriptions

     *    using them in developing secure  database  systems
          (including associated applications)

     *    determining that the implemented systems are  con-
          sistent with their descriptions/specifications?


3.  What are the functionality,  performance,  and  security
interactions  and tradeoffs of various technical features of
database systems, such as the supported:


     *    query facilities

     *    data/object model

     *    data types

     *    concurrency/recovery facilities

     *    inference/deduction capabilities


or the organizations of components (architectures)  of  such
systems, such as:


     *    distributed systems

     *    client/server architectures

     *    layered/modular internal system architectures?


4.  What information can be maintained  or  generated  by  a
database   system  to  assist  in  maintaining  security  or
privacy, and what are good techniques for using such  infor-
mation,  either  at  run-time  or in subsequent analysis, to
detect and discourage security violations?
Newsgroups: comp.security.misc