Home
Remote Collector
Learn how Remote Collectors let you deploy sensors in multiple isolated locations.
Installation Guide
Information and resources on how to install a Remote Collector, and the different options and settings available.
Deployment
Configure custom certificates
You can provision custom Remote Collector certificates on both the Guardian and the Remote Collector sensors to replace the automatically generated self-signed certificates.

Remote Collector
Learn how Remote Collectors let you deploy sensors in multiple isolated locations.
- Introduction
  An overview of the Remote Collector.
- Installation Guide
  Information and resources on how to install a Remote Collector, and the different options and settings available.
  - Introduction
  - Physical installation
  - Virtual installation
  - Container installation
  - Basic configuration
  - Additional settings
  - Deployment
    - Connect a Remote Collector to Guardian
      Once you have configured a remote Collector, you can connect it to a Guardian. You configure a Remote Collector through a terminal secure shell (SSH) or console.
    - Configure the Remote Collector
      To configure a Remote Collector, use the terminal (secure shell (SSH) or console).
    - Set the time zone
      To set the time zone of the sensor, edit the /data/cfg/n2os.conf.user file.
    - Enable bandwidth throttling
      You can specify the maximum amount of allowed traffic to limit the bandwidth that a sensor's management port has at its disposal (for access and updates).
    - Enable multiplexing
      In addition to a primary Guardian, Remote Collectors can multiplex traffic to a set of secondary Guardians. Each Guardian receives the same traffic information from the Remote Collector.
    - Configure the site name and description
      You can set a site name and description for a Remote Collector to help identify it.
    - Set the compression strategy from a shell console
      You can set a compression strategy to compress the traffic that the Remote Collector generates.
    - Set the compression strategy from Guardian or CMC
      Setting a compression strategy lets you compress traffic that the Remote Collector generates.
    - Enable traffic forwarding
      The previous steps enable the Remote Collector to communicate with the Guardian sensor, but traffic forwarding requires the two to exchange the certificates required for encrypting the sniffed traffic being forwarded.
    - Configure custom certificates
      You can provision custom Remote Collector certificates on both the Guardian and the Remote Collector sensors to replace the automatically generated self-signed certificates.
    - Disable a Remote Collector
      You can disable Remote Collectors that are not in-use to make your environment more secure.
  - Compatibility Reference
  - Federal Information Processing Standards
- Troubleshooting
  Troubleshooting procedures to help you solve problems that might occur with the Remote Collector.
- Print format documentation
  A list of all the print-format documentation that is available for the Remote Collector.

Configure custom certificates

You can provision custom Remote Collector certificates on both the Guardian and the Remote Collector sensors to replace the automatically generated self-signed certificates.

Before you begin

Make sure that you have:

Both the certificate and the key file in privacy-enhanced mail (PEM) format
A complete certificate chain

Important:

This feature is not supported in containerized environments.

About this task

To add a private certificate authority (CA) to the system's trust store, see Install a CA certificate.

You must perform this procedure on both the Guardian and the Remote Collector using their respective certificates.

Procedure

Change the name of the certificate file to rc_nozomi.crt
Change the name of the key file to rc_nozomi.key
Upload the certificate and key files to the sensor /data/tmp folder

To enable the certificate, enter this command:

n2os-addtlscert --rc rc_nozomi.crt rc_nozomi.key