At their heart, many critical systems and system infrastructures are composed of real-time and embedded systems (RTES). For example, RTES control our power grids, maintain our smart homes, steer our vehicles or they host the software in road-side units that allow our vehicles to drive more safely and more efficiently. For sure, they will open the way to even more challenging applications, such as in autonomous and cooperating vehicles, terrestrial or aerial.
However, most of these RTES are distributed or networked, which makes them vulnerable both to accidental faults and targeted attacks and advanced and persistent threats. Worse, the compromise of a few nodes may bring down the entire system, in particular if attacks persist.
The grand challenges brought in by these scenarios include ensuring continuous unmaintained opera on under faults and attacks. Systems may possibly utilize easier to upgrade computational resources in mobile phones or road side units whose trustworthiness needs to be established while the RTES approaches these units. And while attackers may try to compromise the RTES’ functionality or timing, we seek to protect the integrity and timeliness of systems and the privacy of their users. Mastering these challenges requires the expertise of several research areas, and so, the goal of this workshop is to bring together researchers and engineers from the security, dependability, distributed systems and real-time communities, in order to discuss and promote new and exciting research ideas and initiatives, and to identify and discuss the challenges that lie ahead for such critical applications.
CERTS 2018 strives for an inclusive and diverse program and solicits short and long technical papers on open problems, experiments, case studies, new ideas, or future challenges.
SCOPE and TOPICS OF INTEREST
CERTS 2018 is open to all topics at the intersection of security and dependability of embedded and real-time systems, with an emphasis on criticality. Hence, the areas of interest include (but are not limited to):
* Security and dependability of cyber-physical systems (CPS) and other real-time and embedded systems
* Vulnerabilities and protective measures for CPS infrastructure
* Fault and intrusion tolerant distributed real-time systems
* Confidentiality and privacy in RTES and CPS
* System architects encompassing combinations of distribution, security, dependability and timeliness.
Contributions could include: technical presentations of systems, system models and architectures, methodologies, tools, protocols and infrastructures to improve dependability/security of RTES/CPS, open problems and challenges and experimental papers that include experience reports and negative results, among others.
All papers must be original and not simultaneously submitted to another journal or conference. The following paper categories are welcome:
* Papers describing original research in the area of security and dependability for RTES/CPS
* Sibin Mohan, University of Illinois at Urbana-Champaign
* Mikael Asplund, Linköpings Universitet
* Marcus Voelp, SnT University of Luxembourg
* Paulo Verissimo, SnT University of Luxembourg
* Antonio Casimiro, University of Lisboa
* Rodolfo Pellizzoni, University of Waterloo
TECHNICAL PROGRAM COMMITTEE
* Antônio Augusto Fröhlich, Federal University of Santa Catarina
* Rakesh Bobba, Oregon State University
* Christian Esposito, University of Naples Federico II
* Martin Gilje Jaatun, University of Stavanger
* Karl Goeschka, Vienna University of Technology
* Zbigniew Kalbarczyk, University of Illinois
* Ravi Prakash, University of Dallas
* Sasikumar Punnekat, Maelardalen University
* Hans Reiser, Universität Passau
* Guillermo Rodriguez-Navas, Maelardalen University
* José Rufino, Faculdade de Ciencias da Universidade de Lisboa
* Elad Schiller, Chalmers University of Technology
* Elena Troubitsyna, Abo Akademi
* Martin Törngren, KTH
* Bryan Ward, MIT Lincoln Laboratory
* Heechul Yun, Kansas University
* Saman Zonouz, Rutgers University
* Sibin Mohan [firstname.lastname@example.org]
* Mikael Asplund [email@example.com]
[Apologies if you receive multiple copies of this message]