Export data from Red Canary

1. In Red Canary, click your profile icon, and then click Canary Exporter.

2. Select which type of data you’d like to export: native, standardized, or cf-flattened (Linux EDR only).

3. Click Generate Credentials.

   1. Credentials are organization-wide for the demo subdomain, not bound to your specific user account. You will receive one AWS key pair for your organization, which should be documented and kept as safe as you would any other password. If you lose your key material, generate a new set of credentials immediately.

Note: Generating new credentials will destroy any previously created credentials.

1. Create a file named config.yaml with the following details, starting with the template below, and customize it to your needs.

---
customer_identifier: demo

input:
  # You can export either 'native', 'standardized', or 'cf-flattened' (Linux EDR only) data from Red Canary.
  #
  # Native is data formatted as it was received by the EDR/EPP platform. This format is ideal when using
  # third-party applications that expect data from a specific product, such as VMware Carbon Black EDR or
  # CrowdStrike Falcon.
  #
  # Standardized is data formatted according to Red Canary's standardized format. This format tends to
  # be easier to read and parse, and is product-agnostic.
  #
  # CF-flattened is data formatted similarly to Red Canary's standardized format but with
  # additional context fields available in the the top-level record of different event types.
  # This format is only available for Linux EDR customers.
  # Learn more about the available fields at https://rc-customer-tools.s3.us-east-2.amazonaws.com/forwarder/canary_forwarder_flat.schema.json.
  #
  stream_name: <<<<< Enter one of 'native', 'standardized', or 'cf-flattened' (Linux EDR only) >>>>>

  aws_region: us-east-2
  aws_access_key_id: <<<<< Enter the access key ID from the previous step >>>>>
  aws_secret_access_key: <<<<< Enter the access key from the previous step >>>>>

  #
  # This is optional and filters data in S3 before it is returned to the exporter.
  # Learn more about S3 SELECT syntax at https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-glacier-select-sql-reference.html.
  #
  # s3_select_where: "S3Object.data.data.entries[0].event_type_full IN ('process_event', 'image_load_event')"

#
# Optional injection of endpoint metadata into exported records
#
# The max number of endpoint metadata records to store in in-memory cache (default: 1000)
# endpoint_cache_size: 1000
#
# Your Red Canary API key used to retrieve endpoint metadata for each exported record
# red_canary_authentication_token: <<<<< Enter your Red Canary API key >>>>>

outputs:
#  - file:
#      directory: output/procstarts
#      max_size_bytes: 10000000
#      max_files: 2
#      export_only_where:
#        event_type_cd:
#          - process_start
#        sensor_id:
#          - 529

#  - kinesis:
#      stream_name: <<<<>>>>
#      max_records_to_buffer_before_sending: 500
#      aws_access_key_id: <<<<>>>>
#      aws_secret_access_key: <<<<>>>>
#      aws_region: <<<<>>>>
#      export_only_where:
#        event_type_cd:
#          - network_connection
#        sensor_id:
#          - 529

#  - s3:
#      bucket_name: <<<<>>>>
#      object_key_prefix: <<<<>>>>
#      aws_access_key_id: <<<<>>>>
#      aws_secret_access_key: <<<<>>>>
#      aws_region: <<<<>>>>
#      max_size_bytes: 10000000
#      compression_format: either 'none' or 'gzip'
#      export_only_where:
#        event_type_cd:
#          - network_connection
#        sensor_id:
#          - 529

#  - azure_blob:
#      storage_account_name: <<<<>>>>
#      container_name: <<<<>>>>
#      blob_name_prefix: <<<<>>>>
#      storage_access_key: <<<<>>>>
#      max_size_bytes: 10000000
#      compression_format: either 'none' or 'gzip'
#      export_only_where:
#        event_type_cd:
#          - network_connection
#        sensor_id:
#          - 529

#  THIS EXPORTER IS ONLY SUPPORTED WHEN USING THE MRI DOCKERFILE (docker pull redcanary/canary-exporter-ruby-mri)
#  - google_cloud_storage:
#      bucket_name: <<<<>>>>
#      object_key_prefix: <<<<>>>>
#      credentials_json: |
#        {
#          "type": "service_account",
#          "project_id": "project-id",
#          "private_key_id": "key-id",
#          "private_key": "-----BEGIN PRIVATE KEY-----\nprivate-key\n-----END PRIVATE KEY-----\n",
#          "client_email": "service-account-email",
#          "client_id": "client-id",
#          "auth_uri": "https://accounts.google.com/o/oauth2/auth",
#          "token_uri": "https://accounts.google.com/o/oauth2/token",
#          "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
#          "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/service-account-email"
#        }
#      max_size_bytes: 10000000
#      compression_format: either 'none' or 'gzip'
#      export_only_where:
#        event_type_cd:
#          - network_connection
#        sensor_id:
#          - 529

#  THIS EXPORTER IS ONLY SUPPORTED WHEN USING THE MRI DOCKERFILE (docker pull redcanary/canary-exporter-ruby-mri)
#  - google_cloud_pubsub:
#      topic_name: <<<<>>>>
#      credentials_json: |
#        {
#          "type": "service_account",
#          "project_id": "project-id",
#          "private_key_id": "key-id",
#          "private_key": "-----BEGIN PRIVATE KEY-----\nprivate-key\n-----END PRIVATE KEY-----\n",
#          "client_email": "service-account-email",
#          "client_id": "client-id",
#          "auth_uri": "https://accounts.google.com/o/oauth2/auth",
#          "token_uri": "https://accounts.google.com/o/oauth2/token",
#          "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
#          "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/service-account-email"
#        }
#      compression_format: either 'none' or 'gzip'
#      export_only_where:
#        event_type_cd:
#          - network_connection
#        sensor_id:
#          - 529

Run the Exporter on a system that has high reliability and availability. Use this command as your starting point with an init script that will restart the docker container if it fails.

Ensure the system running the exporter has network connectivity to Amazon’s SQS and S3 services. S3 could be used for long-term storage for compliance. S3 is a common ingest source for getting data into a SIEM or any sort of login platform.

docker run -t \
--volume $HOME/canary-exporter/config.yaml:/config.yaml \
--volume $HOME/canary-exporter/output:/output \
redcanary/canary-exporter-ruby 

Replace redcanary/canary-exporter-ruby with redcanary/canary-exporter-ruby-mri if you are using the google_cloud_pubsub or google_cloud_storage output configurations.

The following variables can be modified based on your requirements:

• $HOME/canary-exporter/output defines the local path where data will be downloaded, parsed, and output if a file output is configured. Note that everything after the : on this line is required by the exporter and should not be changed.

• $HOME/canary-exporter/config.yaml is the path to the configuration file you customized earlier. The data after the : on this line is required by the exporter and should not be changed.

You can modify the way the container is executed in several ways:

• Use docker run -it to send standard out to the screen and tie the process to the logged in session.

• Use docker run -dit to run the container and output in the background and not tied to a session.

• Use Docker’s —volume /dir:/output:Z option if you find that files are not being written to the host’s output directory as expected. The Docker documentation has a description of these options and how to use them with selinx-enabled host systems.

Additional Notes

• You cannot run multiple exporters with different configurations on the same queue. This will lead to inconsistent results.

• For high data volume environments, run multiple exporters with the same configuration to handle the load.

• The exporter expects to be restarted by a supervising system (supervisor, upstart, init) in case of errors.

• Tools like jq can be used to explore exported JSON data.

Can we use the Canary Exporter credentials to create our own script to collect the data from our subdomain?

The customer is allowed to use their own code to pull the data from their subdomain and not use Canary Exporter. The only caveat is that the customer is responsible for the code and Red Canary’s  support will be limited as you will be using a customized solution for the data transfer.

Can Canary Exporter be hosted by EKS, Fargate, ECS or others?

Canary Exporter supports output to S3 and more output options than just writing local files. Canary Exporter does not yet support loading credentials from a secret store using IAM roles or keys.

Can Canary Exporter Input Location be Changed to another AWS region?  

No, we will not change the input location to another region in AWS. However, you can set up a bucket in us-east-2 and mirror the data to us-east-1 in your account, which may alleviate the need to use the NAT gateway.

Note: Do not confuse this with the output section of the config.yaml file, where the customer can use AWS and configure a region of their choosing.

Canary Exporter deployment concerns

• Each exporter deployment can only read from one queue so if a customer wants native and standardized files, they need to have at least 2 exporters.

• As telemetry volume increases, customers should increase the number of exporters to keep up with  the queue.

• A customer can leverage S3Select to filter out unwanted files.

Why is an external service missing from the exporter for a subdomain with multiple external services?

There are two possible scenarios:

• The external service was likely created before May 31, 2022 and will need to be manually provisioned. This can be done through the production console by executing Subdomains::TerraformCanaryExporter.call(subdomain: Subdomain.current.id)

A number of tools exist that are designed for exploring large amounts of JSON formatted data. jq is especially helpful:

Counting the types of events in exported standardized data

jq .event_type_cd *.json | sort | uniq -c

Listing the sensor ids with data present in standardized data

jq .sensor_id *.json | uniq

The configuration of this section depends on whether you are using “standardized” or “native” format.

• If you choose native format you may want to filter for specific Event Types. To do this, use the EDR products (i.e., Carbon Black, CrowdStrike, etc.) Event Type filters schema.  

• The “native” events stream can be classified as:  Raw Endpoint Events (i.e., Sensor generated event telemetry)

• The Carbon Black EDR Event Types filters can be found here. See the article section “Raw endpoint events” for all Event Types filters. The level of filtering is limited to these broader categories listed above.

• If you choose standardized format you will need to use the Canary Exporter Event Types filters. These are:

  • binary

  • child_process

  • endpoint

  • file_creation

  • file_deletion

  • file_modification

  • model_attributes

  • network_connection

  • process_handle_open

  • process_thread_open

  • registry_key_deletion

  • registry_value_deletion

  • registry_value_write

  • registry_key_creation

  • remote_thread_creation

  • module_load

  • process_end

  • process_start

• If you use native format, the outputs and event type section should look similar to the block below.

Note: If you use Linux EDR, the available event type filters can be found here: Filtering Telemetry for Linux EDR.

Notice the “/” in front of the “output” directory name below. This ensures log data is saved to your local log directory. If the "/" is placed after the output directory name, this will cause Canary Exporter to save logs to the /apps/output directory inside the Docker image).

outputs:
   - file: 
       directory: /output
       max_size_bytes: 10000000
       max_files: 4
       export_only_where:
         type:
           - ingress.event.regmod
           - ingress.event.filemod
           - ingress.event.netconn
           - ingress.event.procstart
           - ingress.event.module
           - ingress.event.childproc
           - ingress.event.crossprocopen

Note: If you comment out the “export_only_where” and below sections or you do not specify a “type,” Canary Exporter will send all Event Types.

If you use the standardized format, the outputs and event type section should look similar to this:  

outputs:
   - file:
       directory: /output
       max_size_bytes: 10000000
       max_files: 2
       export_only_where:
         event_type_cd:
          - process_start
          - child_process
          - binary

Note: If you comment out the “export_only_where” and below sections or you do not specify a “type,” Canary Exporter will send all Event Types.