RTI Security Plugins Getting Started Logo
6.1.0
  • 1. Introduction to RTI Security Plugins
    • 1.1. Key Features
    • 1.2. Paths Mentioned in Documentation
  • 2. DDS System Threats
  • 3. Securing a DDS Domain
    • 3.1. Securing a DomainParticipant
  • 4. Hands-On 1: Securing Connext DDS Applications
    • 4.1. Generating a Connext DDS Project
    • 4.2. Adding Security Artifacts to Your Project
    • 4.3. Enabling Security in Your QoS Profiles
    • 4.4. Linking Your Applications Against RTI Security Plugins and OpenSSL Libraries
      • 4.4.1. Building the Application
    • 4.5. Running the Applications
      • 4.5.1. Configuring the Environment in Both Command Prompts
      • 4.5.2. Checking Communication
    • 4.6. Checking that Your Applications Communicate Securely
      • 4.6.1. Verifying that Eavesdropping Attempts are Frustrated
      • 4.6.2. Detecting Eavesdropping Attempts
    • 4.7. Further Exercises
      • 4.7.1. Give Different Credentials to Each Application in Your System
    • 4.8. Troubleshooting
  • 5. Hands-On 2: Defining Your System’s Security Requirements
    • 5.1. Specifying the Security Requirements
    • 5.2. Composing a Governance File with the Security Requirements
    • 5.3. Signing the Governance File
    • 5.4. Updating the QoS Profiles in Your Project
    • 5.5. Checking that the Specified Security Rules Are Applied
      • 5.5.1. Verifying Communication
      • 5.5.2. Checking the New Security Rules
    • 5.6. Further Exercises
      • 5.6.1. Protecting the Domain
      • 5.6.2. Adding a Topic Rule for the PatientMonitoring Topic
    • 5.7. Troubleshooting
  • 6. Hands-On 3: Defining the DomainParticipant Permissions
    • 6.1. Granting Permissions to Your Secure Participants
    • 6.2. Binding the Permissions File to Your DomainParticipants
    • 6.3. Signing the Permissions Files
    • 6.4. Updating the QoS Profiles in Your Project
    • 6.5. Checking that the New Permissions Are Applied
      • 6.5.1. Communication Only Works in Domain 1
      • 6.5.2. Alice Is Only Allowed to Publish Data
    • 6.6. Further Exercises
      • 6.6.1. Define Different Permissions for Each Application in Your System
    • 6.7. Troubleshooting
  • 7. Hands-On 4: Generating Your Own Certificates Using OpenSSL
    • 7.1. Preliminary Steps
      • 7.1.1. Initialize the OpenSSL CA Database
      • 7.1.2. Limit the Access of the CA’s Private Key
    • 7.2. Generating a New Identity CA
      • 7.2.1. Specifying the New Identity CA Certificate in QoS Profiles
    • 7.3. Generating Identity Certificates
      • 7.3.1. Specifying the New Identity Certificates to Your QoS Profiles
    • 7.4. Updating Permissions Files with New Credentials
    • 7.5. Generating a New Permissions CA
      • 7.5.1. Specifying the New Permissions CA Certificate in QoS Profiles
    • 7.6. Signing the Governance and Permissions Files
      • 7.6.1. Specifying the New Governance and Permissions Files in Your QoS Profiles
    • 7.7. Further Exercises
    • 7.8. Troubleshooting
  • 8. Hands-On 5: Checking that Your DDS Traffic Is Protected
    • 8.1. Disabling Security and Preparing Your Project for Traffic Capturing
      • 8.1.1. Analyzing RTPS Packets in Wireshark
    • 8.2. Encrypting the Serialized Payload
      • 8.2.1. Analyzing RTPS Packets in Wireshark
    • 8.3. Troubleshooting
  • 9. Next Steps
  • 10. Copyrights
RTI Security Plugins Getting Started
  • Docs »
  • Getting Started with RTI Security Plugins
  • View page source

Getting Started with RTI Security Plugins¶

  • 1. Introduction to RTI Security Plugins
  • 2. DDS System Threats
  • 3. Securing a DDS Domain
  • 4. Hands-On 1: Securing Connext DDS Applications
  • 5. Hands-On 2: Defining Your System’s Security Requirements
  • 6. Hands-On 3: Defining the DomainParticipant Permissions
  • 7. Hands-On 4: Generating Your Own Certificates Using OpenSSL
  • 8. Hands-On 5: Checking that Your DDS Traffic Is Protected
  • 9. Next Steps
  • 10. Copyrights
Next

© Copyright 2021, Real-Time Innovations, Inc

Built with Sphinx using a theme provided by Read the Docs.

Send feedback about this document to documentation@rti.com.