paint-brush
Secure and Dynamic Publish/Subscribe: LCMsec: Attacker Model and Security Goalsby@marshalling

Secure and Dynamic Publish/Subscribe: LCMsec: Attacker Model and Security Goals

by MarshallingJuly 10th, 2024
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

LCMsec aims to provide confidentiality and integrity of not only the messages in transit, but also the channelname associated with them. We also provide a notion of authenticity: messages are guaranteed to have originated from a trusted entity within the LCMDomain. We provide a reduced form of security against an attacker, who has no permission to send on a specific channel.
featured image - Secure and Dynamic Publish/Subscribe: LCMsec: Attacker Model and Security Goals
Marshalling HackerNoon profile picture

Authors:

(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany ([email protected]);

(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany ([email protected]).

Abstract and Introduction

Related Work

Description of LCM

Attacker Model and Security Goals

LCMSec: The Proposed Protocol

Implementation and Evaluation

Conclusion

Appendix and References

IV. ATTACKER MODEL AND SECURITY GOALS

We consider active and modifying attackers in the system. Security is provided only against outsiders: we do not consider an attacker who has the permission to send on the multicast group in question (please refer to the discussion on permission management in Section V-B1). The attacker has considerable, but limited resources and cannot break common cryptographic primitives.


Since channelnames in LCM are usually domain-specific topics, they should remain confidential. LCMsec aims to provide confidentiality and integrity of not only the messages in transit, but also the channelname associated with them. We also provide a notion of authenticity: messages are guaranteed to have originated from a trusted entity within the LCMDomain, but cannot be attributed to a specific entity.


We provide a reduced form of security against an attacker, who has no permission to send on a specific channel, but can send on some other channel within the group. Against this type of attacker, the integrity and accountability guarantees remain unchanged, however, confidentiality is provided only for the contents of messages, not for the channelname (or topic) associated with messages. We elaborate on the reason for this trade-off in Section V-A.


This paper is available on arxiv under CC BY 4.0 DEED license.