Channels ▼


Security Added to Real-Time Messaging Middleware

Real-Time Innovations has announced that its RTI Data Distribution Service real-time messaging middleware, has been integrated with Security-Enhanced Linux (SELinux). This combination provides real-time, high-performance distributed applications with the ability to securely distribute data by combining RTI's network communications with the Mandatory Access Control (MAC) facilities of SELinux.

RTI Data Distribution Service lets distributed applications securely exchange messages and data by authenticating peers and encrypting information that is sent over the network. The MAC capabilities of SELinux add several additional levels of protection against mis-configuration, software errors and application vulnerabilities:

  • System-wide security policies control which applications are allowed to communicate with each other. Even applications with the appropriate credentials and keys can communicate only if explicitly provisioned to do so.
  • Files containing keys, configuration information and logs are protected from unauthorized access.

The use of RTI Data Distribution Service with SELinux lets high-performance distributed systems meet stringent government and commercial security standards, including DCID 6/3 PL4, DoD 8500.2, NIST 800-53, PCI, SOX and HIPPA. The SELinux security type enforcement introduces a small increase in latency of roughly two percent regardless of message size.

"RTI Data Distribution Service and SELinux are well suited because of RTI's peer-to-peer messaging architecture," said Karl MacMillan, director of Core Technology at Tresys. "RTI's infrastructure is completely embedded within communicating applications, without separate processes such as message brokers or servers and as a result, SELinux is able to fully control all communication. Most other messaging implementations depend on shared processes, which introduce security vulnerabilities and significantly complicate security management."

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.