<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi="x">
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Call for Papers<br>
Americas Conference Information Systems<br>
Detroit Michigan August 4-7, 2011</font></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma"></font> </div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Description:<br>
</font></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Information security has risen to become a major issue in today’s enterprise environment. Most of the issues being addressed in information security can trace at least one root cause to a vulnerability
resulting from software that is not performing as intended. Secure software is software that is able to perform in a predictable manner even in a hostile environment. Secure software is designed to resist most attacks, and to tolerate attacks it cannot resist,
and to recover quickly from attacks. Unfortunately most software is not secure and vulnerabilities plague most systems. A lot of industry led efforts have raised the bar in the area of software assurance. These efforts include Secure Development Lifecycles,
tools such as Threat Modeling and Fuzzing, industry efforts such as SAFECode.</font></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Significant research opportunities exist to address the myriad of issues associated with the production of secure code. This mini-track presents a venue for researchers to present new and novel methods
of attacking this critical problem. From technical solutions associated with code, to behavioral research associated with the software engineering process, to a myriad of associated underlying contributing factors, this mini-track is intended to bring researchers
together to share information and learn from each other. Teaching cases and business cases demonstrating methods of success are also invited and welcomed.</font></div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma"></font> </div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Suggested topics include, but are not limited to:<br>
• Tools to improve software assurance<br>
• Methods to improve software assurance<br>
• Development techniques to build security in, rather than add it on after the fact<br>
• Models to enable better software assurance measurement<br>
• Theory, design and research issues associated with software assurance mechanisms<br>
• Frameworks associated with software assurance<br>
• Workforce, education and training issues that can improve software assurance<br>
• The role of government regulation in resolving software assurance issues</font></div>
<font color="#000000" size="2" face="Tahoma">
<div dir="ltr"><br>
Important Dates<br>
2/17/2011 Submission deadline <br>
3/24/2011 Authors notified of paper acceptance decision <br>
4/21/2011 Camera-Ready Papers due<br>
8/4 – 7/2011 AMCIS in Detroit</div>
<div dir="ltr"> </div>
<div dir="ltr">Submissions via manuscript central system: <a href="http://mc.manuscriptcentral.com/amcis2011">
http://mc.manuscriptcentral.com/amcis2011</a> <br>
AMCIS website <a href="http://amcis2011.aisnet.org/">http://amcis2011.aisnet.org/</a><br>
Track: Information Systems Security and Privacy <br>
Mini-track: Software Assurance</div>
<div dir="ltr"> </div>
<div dir="ltr">Chairs’ Contact Information<br>
Wm. Arthur Conklin<br>
University of Houston<br>
<a href="mailto:waconklin@uh.edu">waconklin@uh.edu</a></div>
<div dir="ltr"> </div>
<div dir="ltr">Dan Shoemaker<br>
University of Detroit – Mercy<br>
<a href="mailto:shoemadp@udmercy.edu">shoemadp@udmercy.edu</a></div>
<div dir="ltr"> </div>
<div dir="ltr">Carol Woody<br>
SEI/CMU<br>
<a href="mailto:cwoody@cert.org">cwoody@cert.org</a><br>
</div>
<div dir="ltr"></font> </div>
</body>
</html>