Shield Connectors

UB Connector

Back To Connectors Page

Financial Messaging & Trading Communications | Connector for UB

Request a Demo

What Is the Shield Connector for UB?

UB is a financial messaging and trading communications platform used across regulated financial institutions to support real-time communication, order management workflow, and transaction-related messaging in connection with financial markets activity. Deployed within the trading and financial operations environment, UB provides a communications layer through which front-office staff, operations teams, and counterparties exchange messages and instructions in connection with the firm’s trading activity.

Shield’s connector for UB ingests messages and associated metadata directly from the UB platform into Shield’s compliance platform, making every captured communication immediately available for AI-powered surveillance, investigation, and eDiscovery alongside every other channel the firm uses. From the moment data enters Shield, it is available within a single unified platform — without manual exports, without siloed review workflows, and without the blind spots that arise when trading platform messaging is managed separately from other regulated communications.

UB data does not exist in isolation. Shield understands the full context of financial trading communications, enabling compliance teams to detect genuine risk rather than chasing false positives.

Why UB Compliance Is Complex

UB communications present compliance challenges that reflect both the specific characteristics of financial trading platform messaging and the regulatory sensitivity of transaction-adjacent communications. Several issues arise consistently across regulated firms:

  • Transaction-adjacent communications and trade reconstruction. UB messages are generated in the context of financial transactions — meaning they may directly accompany or constitute part of the communication record of a regulated trade. Messages about order placement, pricing, execution instructions, and trade confirmation within UB are potentially material to trade reconstruction obligations under MiFID II, Dodd-Frank, and CFTC requirements. Archiving UB data without the transactional context and metadata that makes it meaningful for trade reconstruction produces records that are incomplete for regulatory examination purposes.
  • Platform-specific data delivery and metadata. UB data is generated within its own platform architecture — with data delivery mechanisms, metadata structures, and export formats specific to the UB environment. Compliance connectors designed for general enterprise messaging platforms do not automatically extend to UB, and firms that have deployed comprehensive eComms archiving for Bloomberg IB, email, and Teams may nonetheless have a gap in their UB coverage if a dedicated UB connector is not in place.
  • The gap between capture and surveillance. UB may provide some data export or archiving capability. What it does not provide is AI-powered misconduct surveillance, cross-channel correlation, or the eDiscovery and investigation workflows required under financial services compliance frameworks. Data held in UB export infrastructure means the capture obligation may be met; it does not mean the surveillance obligation is met.
  • Financial platform language and trading context. UB communications are generated within a financial trading environment — carrying the compressed, instrument-specific, and context-dependent language of front-office trading operations. Generic keyword-based surveillance tools cannot accurately interpret this content without the financial services NLP context required to distinguish genuine misconduct signals from routine trading language.
  • Cross-channel continuity. UB communications rarely represent the complete picture of a trading interaction. Activity documented in UB may be accompanied by Bloomberg IB messages, voice calls, and email correspondence about the same transactions. Compliance architectures that hold UB data separately from these other channels produce fragmented trading communication records that cannot support complete trade reconstruction or cross-channel misconduct detection.

Key Features of the Shield UB Connector

Complete UB Communication Capture. Shield captures all UB messages and communications within scope — including transaction-related messages, order communications, counterparty instructions, and operational notifications — alongside the full metadata layer generated by the UB platform. All data is ingested in full, with zero data loss.

Full Metadata Preservation. Shield retains and enriches the complete UB metadata layer — including sender and recipient identifiers, transaction and order identifiers where available, timestamps, message IDs, and platform-specific context fields. This metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that investigations, regulatory examination responses, and eDiscovery productions are accurate and legally defensible.

Immutable, Audit-Ready Archive. All UB data captured by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations. Retention periods are fully configurable to meet jurisdiction-specific requirements — including the six-year standard under SEC Rules 17a-3 and 17a-4, the five-to-seven-year requirements under MiFID II and MAR, and the five-year requirements under CFTC Regulation 1.35.

Out-of-the-Box AI Surveillance Models. Shield ships with pre-configured AI surveillance models for UB communications, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, and personal misconduct — calibrated to the specific language patterns of financial trading platform communications. Models can be customised to reflect a firm’s specific risk appetite, restricted counterparty lists, and internal policy requirements.

Unified Cross-Channel Surveillance. UB data does not exist in isolation. The same traders and operations staff who communicate over UB are also using Bloomberg IB, email, Microsoft Teams, and other channels — often for the same transactions and counterparties. Shield ingests UB data into the same unified compliance platform as every other channel, enabling compliance teams to correlate UB communications with all other sources. This cross-channel context is essential for accurate detection of misconduct and complete trade reconstruction.

Data Governance and Chain of Custody. Shield’s UB connector preserves a complete, verifiable chain of custody from ingestion through archiving and retrieval. Every stage of data handling is logged, auditable, and reportable — giving compliance officers and legal teams the confidence that UB records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

UB communications are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield UB connector supports compliance with:

  • SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant, non-rewriteable format with an audit trail, for a minimum of six years — applicable to UB communications generated in connection with regulated activity.
  • FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their business as such — including financial platform messaging — with written supervisory procedures, supervision requirements, and full audit trail capability in place.
  • MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days, and to monitor communications for indicators of insider trading, front-running, and market manipulation — applicable to UB communications in connection with trading activity.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to retain records of all communications relating to commodity interests and swap transactions as part of a complete audit trail for trade reconstruction, including financial platform messaging communications.
  • FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to record and retain relevant electronic communications for a minimum of five years, and to implement effective surveillance arrangements to detect and prevent market abuse — applicable to UB communications by regulated trading desk and operations staff.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions, enabling firms to meet GDPR obligations alongside their financial services recordkeeping requirements.

Other Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform, so UB data is always reviewed in the context of every other channel your trading desks use.

Frequently Asked Questions

Which regulations does the Shield UB connector help firms comply with?

The Shield UB connector supports compliance with SEC Rules 17a-3 and 17a-4, FINRA Rules 4511 and 3110, MiFID II, Market Abuse Regulation (MAR), CFTC Regulation 1.35 and 17 CFR § 23.202, FCA SYSC 10A, and applicable data privacy regulations including GDPR.

How does Shield handle the transaction-specific language typical of UB communications?

Shield’s surveillance engine applies NLP models specifically trained on financial services language — including the transaction-specific shorthand, instrument references, and trading context language typical of financial platform communications. This contextual understanding reduces false positive alerts and ensures that genuine risk signals are identified accurately, even when expressed in abbreviated or context-dependent trading language.

Can UB data be reviewed alongside Bloomberg IB and other channels during an investigation?

Yes. Shield ingests UB into the same unified compliance archive as every other channel — Bloomberg IB, email, Teams, and voice. Trading misconduct and coordinated activity rarely stay within a single platform — communications about the same transaction may span UB, Bloomberg IB, and email. Shield enables compliance teams to reconstruct the complete trading communication sequence across all platforms in a single workflow.

How quickly can the Shield UB connector be deployed?

Shield’s out-of-the-box connectors are designed for rapid deployment. The UB connector can be configured and activated without extensive IT involvement, and Shield’s onboarding team supports firms through the full deployment and validation process to ensure data flows are complete and accurate from day one.

How should firms handle GDPR and privacy obligations for UB communications?

UB communications captured for compliance purposes are subject to GDPR obligations — including requirements around lawful basis for capture, employee notification, data subject access rights, and retention limitation. Shield’s architecture supports privacy-compliant handling of UB data, including configurable retention periods and data residency controls.

Related Terms