Introduction

OneSpan Threat View is a cutting-edge software solution designed to provide insights into the interaction of users and their devices with(in) mobile applications and to have visibility into mobile threats faced by the users. The solution integrates with digital banking apps (web or mobile) and greatly enhances security and performance monitoring. Using Threat View you can address security risks in modern applications while providing a convenient, effective, and value-oriented solution for your users.

Collecting threat event types from your integration of OneSpan Mobile Application Shielding, Threat View visualizes threat event types in widgets to provide insights into the threat event exposure. With Threat View you can check scenarios such as

• Is there an increase or decrease for injection attacks?

• Is there a difference during the time of the day?

• Are there more or less attacks on recent operating system versions?

Threat View has the following advantages:

• Easy integration and deployment

  Threat View is easily integrated and deployed to start monitoring for threats quickly and efficiently.

• Intuitive user experience

  The Threat View Administration Interface is designed to follow operating system best practices, ensuring an intuitive user experience that reduces friction and enhances user adoption.

• Industry best-practice standards

  Threat View adheres to industry best-practice standards to ensure scalability and maintainability.

• Multi-tenancy support

For more information about App Shielding, see the Mobile Application Shielding user documentation.

Product components

OneSpan Threat View has the following main components:

• Threat View server-side component with the Threat View Administration Administration Interface

• Threat View Client SDK

• Event Simulator

Threat View server-side component

The Threat View server-side component is an on-premise back end, based on different microservices. It collect the events captured by the Client SDK and integrates the system databases used to handling the following processes:

• Auditing

• User management

• Threat exposure analysis

• User authentication

The most notable microservices Threat View uses are:

• Audit logger, to audit the system

• Data collector, to aggregate data

• Data Processor, to process aggregated data received from the data collector service

• Identity Management, for user management

• Visual Renderer, for the data visualizations

• Tokens, for user authentication

Threat View Administration Administration Interface

The Threat View Administration Administration Interface, as part of the server-side component, allows user interaction with the system. It provides a dashboard with a quick view on threat events and access to the user management and detailed reports of threat event reports for authorized users.

It also provides access to the My Profile page, where the personal information of the currently logged-in user is displayed and can be edited.

For more information, see the following articles:

• Dashboard

• Threat event reports

• User management

Threat View Event Simulator

The Event Simulator is a service that generates test events at regular interval to provide realistic data. This can be used to quickly evaluate Threat View in a demo environment.

The Event Simulator is a separate package to be installed together with Docker Compose and is provided on an as-is basis for demonstration purposes only. OneSpan provides only minimal support to the extent required for use as a demonstration tool.

For more information, see Event Simulator.

Threat View Client SDK

The OneSpan Threat View Client SDK for Android and iOS captures threat events in mobile apps, collects these events based on triggers received from the integration of OneSpan Mobile Application Shielding in your mobile apps, and sends the collected information to the OneSpan Threat View server-side component. For the SDK to generate and communicate threat events, it must be integrated with OneSpan Mobile Application Shielding. For detailed information about App Shielding, see the Mobile Application Shielding user documentation.

For more information about the SDK, see Threat View Client SDK Integration Guide.