Solution Overview

Solution Overview

Solution Overview

The Crosser Solution is entirely focused on streaming analytics, i.e. analyzing data in motion. It is optimized for collecting data close to the source and then analyze the data in real time. The results can be delivered to machines, storage systems or other local systems as well as to the cloud by using pre-built connectors for common systems and services.

The Crosser Solution consists of two parts:

The Crosser Node - A software platform that runs in a Docker container close to the sources of data. This is where data is collected, processed and results are delivered to different receivers, on-premise or in the cloud.

The Crosser Cloud - A web service that is used to design the processing flows to run in Edge Nodes, by using the Flow Studio visual designer. The Edge Director is then used to deploy and update flows running on Edge Nodes and to monitor the operation of all installed Edge Nodes.

To learn more about the Crosser Solution we recommend our introduction videos which can be found here

Security Overview

The Crosser Solution is designed with security as a top priority. Security comes into play in different places, who has access to what data, who has access to what systems?
The following security principles have been implemented in the Crosser solution:

  • All communication between Crosser nodes and the Cloud service is initiated at the Crosser nodes. This is to avoid having to open ports in firewalls for inbound internet traffic.
  • Crosser nodes must register with the cloud service using a unique ID and access key before any management operations can be performed.
  • All communication between Crosser nodes and the Cloud service is encrypted using HTTPS on standard ports.
  • Data outputs from flows running on Crosser nodes implement the security mechanisms supported by the receiving end.
  • Endpoints for receiving data into an Crosser node, such as MQTT and HTTP can be configured to require authentication and encryption.
  • Sensitive information, such as credentials, is stored securely in the Cloud service and the information is never exposed to end users, except when first entered into the system.

    • Related Articles

    • Analytics Modules Overview

      Analytics Modules Overview This section presents the analytics modules available in the Crosser Module library. Analytics modules are used to transform and harmonize message formats from different sources, as well as operate on the actual message ...
    • Creating Your First Flows

      Create Your First Flow In this guide we will start by creating a basic example Flow. It doesn't connect to any external system, the goal is just to get you familiarized with the concept of building and testing Flows. We will use an internal data ...
    • Monitoring the Crosser Node

      Introduction Once you have your first flows deployed, you might think about how to integrate the Crosser Node and Flows into your existing monitoring solution. In this article we describe what options you have and how to utilize provided interfaces ...
    • Authenticating users with OpenID Connect

      Authenticating users with OpenID Connect With the standard setup users are authenticated internally in Crosser Cloud. If you already have a directory server where your users are registered you can use this for authenticating users with Crosser Cloud ...
    • Microsoft Dynamics 365

      Modules - Microsoft Dynamics Create Record - Microsoft Dynamics Get Record How to register an App for Dynamics/Dataverse Introduction This guide will guide you through the process of registering an App for Dynamics/Dataverse and get the credentials ...