Communications Security
======================================================================
Call for Papers:
16th ACM Conference on Computer and Communications Security (CCS) 2009
Nov 9 - 13, 2009: Hyatt Regency Chicago, IL, USA
http://sigsac.org/ccs/CCS2009
======================================================================
Important Dates:
Apologies for multiple copies of this announcement.
------------------------------------------------------
18th ACM Conference on Computer and Communications Security (ACM CCS 2011)
CALL FOR PAPERS
OCTOBER 17 - 21, 2011
SWISSOTEL Chicago, Chicago, IL, USA
http://sigsac.org/ccs/CCS2011
The annual ACM Computer and Communications Security Conference is
============================================================
Please excuse multiple copies of this message.
============================================================
CALL FOR PARTICIPATION
ACM Conference on Computer and Communications Security (CCS)
Nov 9 - 13, 2009: Hyatt Regency Chicago, IL, USA
http://sigsac.org/ccs/CCS2009
============================================================
Student Travel Grants application for CCS 2009 is due on Sept 25!
http://www.sigsac.org/ccs/CCS2009/stgrant.shtml
======================================================================
Call for Workshop Proposals:
16th ACM Conference on Computer and Communications Security (CCS) 2009
Web page: http://www.sigsac.org/ccs/CCS2009/cfw.shtml
======================================================================
Important Dates:
* Submission deadline: Saturday, February 28, 2009
======================================================================
=
========================================================================
Call for Papers: ACM CCS WORKSHOPS
co-located with the
16th ACM Conference on Computer and Communications Security (CCS)
2009
Nov. 9, 2009 - Nov. 13, 2009 -- Chicago, IL, USA
http://www.sigsac.org/ccs/CCS2009/
Introduction
============
Recent history has proven that web communications security is highly
lacking in redundancy. That is, simple breaks in common protocols,
such as SSL/TLS or the authentication mechanisms which support it,
often lead to catastrophic gaps in security. Recent examples of this
fragile architecture abound, and even when protocols and
implementations themselves are sound, research indicates browser user
instance, if you configure Outlook in "auto" mode, it will be
vulnerable to MitM every time.
I would argue that if server admins and MUAs don't do all of these
things, however, there is no "significant" improvement in
communications security. It's either possible to read some one else's
mail on the wire, or it's not. (We often like to think that security
is a continuum of being more or less secure based on level of effort,
but in many cases that's simply not true. You're either vulnerable to
an issue or you're not.)
* Legal and Social Aspect of Information Security
* Software Engineering and Security
* Security in Information Retrieval
* Network Security
* Forensics and Anti-Forensics
* Mobile Communications Security and Vulnerabilities
* CSIRTs, Incident Analysis and Response
Deadlines =========
* Legal and Social Aspect of Information Security
* Software Engineering and Security
* Security in Information Retrieval
* Network security
* Forensics and Anti-Forensics
* Mobile communications security and vulnerabilities
Deadlines
=========
- Guillaume Prigent (France)
Web Application Firewalls
- Sebastien Gioria (OWASP France)
UC Security (Unified Communications Security)
- Abhijeet Hatekar (Sipera Systems) (India)
SS7
- Philippe Langlois (France)
- Legal and Social Aspect of Information Security
- Software Engineering and Security
- Security in Information Retrieval
- Network security
- Forensics and Anti-Forensics
- Mobile communications security and vulnerabilities
Deadlines:
----------
* Legal and Social Aspect of Information Security
* Software Engineering and Security
* Security in Information Retrieval
* Network Security
* Forensics and Anti-Forensics
* Mobile Communications Security and Vulnerabilities
Deadlines =========
|
