Security and robustness for collaborative monitors

Bas Testerink*, Nils Bulling, Mehdi Dastani

*Corresponding author for this work

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    Abstract

    Decentralized monitors can be subject to robustness and security risks. Robustness risks include attacks on the monitor’s infrastructure in order to disable parts of its functionality. Security risks include attacks that try to extract information from the monitor and thereby possibly leak sensitive information. Formal methods to analyze the design of a monitor with respect to these issues can help to create more secure designs and/or identify critical parts. In this paper we specify a model for analyzing robustness and security risks for collaborative monitors constructed from a network of local monitors.

    Original languageEnglish
    Title of host publicationCoordination, Organizations, Institutions, and Normes in Agent Systems XI - COIN 2015 International Workshops COIN@AAMAS, Revised Selected Papers
    PublisherSpringer
    Pages376-395
    Number of pages20
    Volume9628
    ISBN (Print)9783319426907
    DOIs
    Publication statusPublished - 2016
    EventInternational Conference on Coordination, Organisations, Institutions and Norms in Agent Systems, 2015 - Istanbul, Turkey
    Duration: 4 May 20154 May 2015

    Publication series

    NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
    Volume9628
    ISSN (Print)03029743
    ISSN (Electronic)16113349

    Conference

    ConferenceInternational Conference on Coordination, Organisations, Institutions and Norms in Agent Systems, 2015
    Country/TerritoryTurkey
    CityIstanbul
    Period4/05/154/05/15

    Keywords

    • Monitoring
    • Runtime verification
    • Security

    Fingerprint

    Dive into the research topics of 'Security and robustness for collaborative monitors'. Together they form a unique fingerprint.

    Cite this