Security

Data Distribution Service (DDS) Brief

Date: 
August, 2011

This paper describes the problems DDS data-centric messaging technology was designed to address, including flexible deployment, performance and scalability, robust architecture, and secure communication. It was written from the perspective of a US Navy user, but the problems and solutions it describes are not specific to that environment.

DDS Security Requirements

Date: 
July, 2010

Raytheon Integrated Defense Systems position presentation for the OMG DDS Security Panel

Security requirements on DDS as perceived by Combat System applications

Securing access to Distributed Pub-Sub Information in a System-of-Systems

Date: 
July, 2010

Classical approaches to distributed system security often rely on single-purpose entities to authenticate clients, enforce access and security policy, or at least distribute authentication tokens.  While these models are reasonable for controlling access to a centralized resource (such as a database), they are not suitable for highly-distributed and dynamic systems where fielded nodes with intermittent connectivity require access to real-time data.

DDS Security Extensions RFP Proposal

Date: 
July, 2010

Proposed RFP to add standard interoperable mechanisms to communicate data securely using DDS. The proposed standard would add several new capabilities to DDS:

Using SELinux to secure DDS applications: Proper configurations and Lessons Learned

Date: 
July, 2009

hen DDS is used in complex distributed systems-of-systems, numerous security concerns may arise. These include ensuring availability of the system, resistance of the system to un-trusted network traffic, and confidentiality of sensitive data. As systems are increasingly interconnected, it is crucial that security concerns be considered early in the design process.

Syndicate content