[ml] [redwinst@CS.JMU.EDU: ISSSE CfP txt version]

Ciaps,

   non so se e` in-topic per la ml; nel caso lo fosse, FYI :-)

bye,
GG sullivan

-- 
Lorenzo `Gigi Sullivan' Cavallaro <sullivan@xxxxxxxxxxxxx>
GPG key at http://security.dico.unimi.it/~sullivan/sullivan.asc

Until I loved, life had no beauty;
I did not know I lived until I had loved. (Theodor Korner)

See the reality in your eyes, when the hate makes you blind. (A.H.X)
> --- Begin Message ---
> ---
>
> Call for Papers, Panels, and Tutorials
>
> IEEE International Symposium on Secure Software Engineering (ISSSE '06)
>
> McLean, VA, March 13-15 2006
> (Near Washington, DC)
>
> http://www.jmu.edu/iiia/issse
>
> Submittals Due September 6, 2005
>
> ISSSE 2006 is sponsored by the IEEE Computer Society Technical Council on Software Engineering, and is in cooperation with the IEEE-CS Task Force on Information Assurance
>
> Today, security problems involving computers and software are frequent, widespread, and serious. The number and variety of attacks by persons and malicious software from outside organizations, particularly via the Internet, are increasing rapidly, and the amount and consequences of insider attacks remains serious. Over 90% of security vulnerabilities reported to the CERT Coordination Center result from defects in software requirements, design, or code. 
>
> Successful software security, however, is fundamentally a software engineering problem - encompassing producing and evaluating secure software. This new Symposium series is an effort to further the professional community's response to this need and reflects the growing interest existing within the commercial, governmental, educational, and research sectors on improving secure software engineering and its supporting knowledgebase to meet this need. 
>
> The Symposium covers all aspects of the processes, techniques, technology, people, and knowledgebase that have or need the capability to contribute to producing (more) secure software including their characteristics, interrelationships, creation, sources, transfer, introduction, use, and improvement. 
>
> The Symposium series is international in involvement and scope . The Co-Program Chairs of the first ISSSE are from the U.S. and from Europe.  Research reports, experience reports, and survey/historical articles are welcome if they meet the expected professional standards of quality, relevance, importance, and interest, and have not been published or submitted elsewhere.  Panels, workshop reports, tutorials and invited speakers will also be included in the Symposium. 
>
> Potential Topics include but are not limited to: 
>
> * Threat modeling and analysis of vulnerabilities
> * Security requirements and security policies
> * Secure architectures & design
> * Formal specification, designs, policies, and proofs
> * Model checking for security
> * Coding practices
> * Static analysis and other automated support
> * Processes for producing secure software
> * Testing of security in software
> * Certification and accreditation
> * Relationships among software correctness, reliability, survivability, safety, and 		security
> * Secure software project management 
> * Software Security-related measurement
> * Assurance cases
> * Size of exposure's implications for software development and assurance
> * Market and legal forces 
> * Lessons learned
> * Ethics and human factors
> * Technology transfer
>
> Submissions Guidelines
>
> Papers
>
> We welcome paper submissions of research or experience as well as survey/historical articles relating to the topic of secure software engineering. To allow blind refereeing, submissions should have the author(s) names, affiliations, and contact information on a separate first page and avoid in the initial submission any easy to avoid identifying content or references that are not central to the article. Authors should not make omissions that damage the merit of the article.
> Papers shall follow the IEEE Computer Society Press - Proceedings Author Guidelines for 8.5x11-inch Proceedings Manuscripts1 and contain an abstract, body, and references. Initial submissions shall be in Microsoft Word or Adobe PDF formats. All text, figures, and tables shall be in black and white, and clear and easy to read.
>  
> The bulk of the papers are expected to be 8 pages or less. Papers over 12 pages must justify their length by their outstanding merit, relevance, and wide interest. No papers will be accepted over 18 pages in length. Papers must have completeness, solid substance, and adequate detail; and this must justify their length.
>
> Panel Proposals
>
> We welcome proposals for panels on topics of high relevance and interest to the secure software engineering community. Panels are expected to be composed of a moderating chair plus approximately three panelists who make short presentations on different viewpoints, aspects, or experiences. Submissions should state the topic, and the name, affiliations, and qualifications of the chair and the participants plus the contributions expected from the latter. A contact point for the proposal should be identified. All panelists should have agreed to participate. Panels are expected to be either 45 or 90 minutes in duration, with roughly half of the time devoted to discussion. A one to two page paper suitable for inclusion in the proceedings should accompany the proposal. The paper should include a description of the topic and the key elements of the position of each participant.  
>
> Proposals for panels composed of reports from relevant workshops are welcome, but are expected to include one to two page written reports on each workshop suitable for inclusion in the proceedings.
>
> Tutorial Proposals
>
> Proposals are welcomed for both half and full day tutorials to occur on Monday March 13. The proposals should provide a statement of the audience and why the tutorial will generate attendance. Tutorials are expected to have an attendance of between 20 and 50 people, but more is possible. The proposal shall state the topic, the contents, the benefits to attendees, and identify the presenter(s) and their affiliation. Also cover the presenter's qualifications in the topic area, any record of successful tutorials or presentations, and evidence justifying a high expectation for the suitability for the audience and quality of content and presentation. A contact point for the proposal shall be identified.
>
> Submission Procedure
>
> All submissions of papers and proposals for tutorials and panels shall be submitted for consideration to redwinst@xxxxxxxx
>
> Important Dates:
>
> Full Papers, and Tutorial and Panel Proposals Deadline		6 September, 2005
> Notification of Acceptance (tentative)				6 December, 2005
> Final Paper Deadline (tentative)				6 January, 2006
>
> Program Committee 
> Co-Program Chairs: 
> Anthony Hall (UK)
> Jeannette Wing (US)
> Members:
> Matt Bishop (US)
> John Clark (UK) 
> Noopur Davis (US)
> Bart De Win (Belgium)
> Andrew Gordon (UK)
> Cynthia Irvine (US)
> Jan Jurjens (Germany)
> Khaled Khan (Australia)
> Jean-Louis Lanet (France)
> Gary McGraw (US)
> Mattia Monga (Italy)
> Peter Neumann (US)
> Peter Ryan (UK)
> John Viega (US)
> James Whittaker (US) 
>
> For more information contact: General Chair Sam Redwine redwinst@xxxxxxx
>
> ---
>
> --- End Message ---