Shield Connectors

MobileGuard SMS Connector

Back To Connectors Page

Mobile Communications | Connector for MobileGuard SMS

Request a Demo

What Is the Shield Connector for MobileGuard SMS?

MobileGuard — now part of Smarsh following its 2016 acquisition — is an enterprise mobile communication archiving platform purpose-built for regulated industries, providing SMS and mobile message capture, archiving, and supervision solutions for financial services firms, government agencies, and other compliance-sensitive organisations. MobileGuard’s product suite includes NetGuard (a network-level SMS capture solution requiring no on-device apps, available for AT&T and Verizon in the United States), MessageGuard (a device-based capture solution for Android and BlackBerry devices on any carrier), and SecureChat (a BYOD-compatible virtual number solution for iOS). Together, these solutions provide regulated firms with flexible, carrier-agnostic mobile SMS capture across corporate and personal devices.

For regulated financial services firms, MobileGuard SMS represents a compliance capture mechanism — and the records held within MobileGuard’s archiving infrastructure are business records subject to the same recordkeeping, supervision, and surveillance requirements as any other regulated electronic communication. Firms that deployed MobileGuard to address their mobile SMS compliance obligations hold communication records within MobileGuard’s archive that require integration into a unified compliance surveillance platform to meet active surveillance and eDiscovery requirements beyond what MobileGuard’s own archiving capability provides.

Shield’s connector for MobileGuard SMS ingests SMS message records and associated metadata from MobileGuard’s archiving infrastructure directly into Shield’s compliance platform, making captured SMS communications 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 — ensuring that MobileGuard-held SMS records are not siloed from the Bloomberg IB, email, Teams, and voice communications that may accompany the same business interactions.

MobileGuard SMS data does not exist in isolation. The same employees whose SMS communications are captured through MobileGuard are also communicating over Bloomberg IB, email, Microsoft Teams, and other channels. Shield ensures that MobileGuard SMS records are available alongside every other channel in a single unified investigation and examination workflow.

Why MobileGuard SMS Compliance Is Complex

SMS communications held within MobileGuard present compliance challenges that reflect both the characteristics of mobile text messaging and the specific architecture of MobileGuard’s platform. Several issues arise consistently across regulated firms:

  • The gap between archiving and surveillance — MobileGuard provides SMS capture and archiving — storing mobile communications within its infrastructure. What MobileGuard does not provide is AI-powered misconduct surveillance, cross-channel correlation, or the eDiscovery and investigation workflows required under financial services compliance frameworks. SMS records in MobileGuard mean messages are archived; they do not mean they are being actively surveilled for misconduct.
  • Multi-product architecture and data completeness — MobileGuard’s product suite spans NetGuard (network-level capture for AT&T and Verizon), MessageGuard (Android and BlackBerry device capture), and SecureChat (iOS BYOD). Firms that deployed multiple MobileGuard products across different device types and carriers may hold SMS records in separate data streams within the MobileGuard infrastructure. A unified compliance view requires ingesting all MobileGuard data sources into the same archive.
  • Carrier-specific coverage and gaps — MobileGuard’s NetGuard network-level capture solution operates on AT&T and Verizon in the United States. Firms with employees on other carriers — including Vodafone, T-Mobile, or international carriers — may require additional capture mechanisms to achieve complete mobile SMS coverage. Understanding the carrier coverage of the firm’s MobileGuard deployment is essential for identifying any gaps in the SMS compliance record.
  • Mobile-specific language and informality — SMS communications are characteristically brief, informal, and dense with abbreviations. Generic keyword-based surveillance tools cannot accurately interpret this content without financial services NLP context — missing genuine misconduct signals or generating excessive false positives.
  • Cross-channel continuity — MobileGuard-captured SMS conversations rarely represent the complete picture of a business interaction. The same employees communicating over SMS were also using Bloomberg IB, email, and voice. Compliance architectures that hold MobileGuard SMS separately from other channels cannot reconstruct the complete business interaction record.

Key Features of the Shield MobileGuard SMS Connector

Complete MobileGuard SMS Data Ingestion. Shield ingests SMS message records and associated metadata from MobileGuard’s archiving infrastructure — across all MobileGuard product streams (NetGuard, MessageGuard, and SecureChat) deployed within the firm — into Shield’s compliance platform. All captured message content and metadata are ingested in full, with zero data loss.

Full Metadata Preservation. Shield retains and enriches the complete MobileGuard SMS metadata layer — including sender and recipient identifiers, timestamps, message IDs, delivery status records, carrier identifiers, and device identifiers as preserved within the MobileGuard archive. This metadata is made fully searchable and stored as part of the immutable compliance record.

AI Surveillance Applied to MobileGuard-Held SMS Data. Shield applies AI-powered surveillance models to SMS records ingested from MobileGuard — enabling active surveillance of MobileGuard-held SMS archives with AI detection capability targeting market manipulation, information leakage, MNPI sharing, front-running, and personal misconduct, calibrated to the specific language patterns of mobile SMS in financial services contexts.

Immutable, Audit-Ready Archive. All SMS data ingested from MobileGuard is stored in Shield’s tamper-evident, WORM-compliant archive with a complete audit trail. Retention periods are fully configurable — 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.

Unified Cross-Channel Surveillance. Shield ingests MobileGuard SMS data into the same unified compliance platform as Bloomberg IB, email, Teams, and every other channel — enabling compliance teams to correlate SMS records with all other communication sources in a single investigation workflow.

Data Governance and Chain of Custody. Shield’s MobileGuard SMS connector preserves a complete, verifiable chain of custody from MobileGuard data ingestion through archiving and retrieval, ensuring that SMS records are admissible, complete, and unaltered within the Shield compliance archive.

Regulatory Coverage

MobileGuard SMS records are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield MobileGuard SMS 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 format, for a minimum of six years.
  • FINRA Rules 4511 and 3110 — requiring member firms to archive all business communications including mobile SMS, with written supervisory procedures and full audit trail capability in place.
  • MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers and futures commission merchants to retain records of communications relating to commodity interests and swap transactions.
  • FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to retain relevant electronic communications for a minimum of five years and implement effective surveillance.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions.

Other Related Connectors

Frequently Asked Questions

What is MobileGuard and what SMS archiving products does it provide?

MobileGuard, now part of Smarsh, is an enterprise mobile communication archiving platform providing SMS capture for regulated industries. Its products include NetGuard (network-level capture for AT&T and Verizon, no on-device app required), MessageGuard (device-based capture for Android and BlackBerry on any carrier), and SecureChat (iOS BYOD virtual number solution). Together these products enable firms to capture SMS across corporate and personal devices across multiple carriers.

Does MobileGuard provide AI-powered surveillance for the SMS records it archives?

MobileGuard provides SMS capture and archiving. It does not provide AI-powered misconduct surveillance, cross-channel correlation, or the eDiscovery workflows required under financial services compliance frameworks. Firms with SMS records in MobileGuard require a dedicated compliance surveillance solution — such as Shield — to apply active surveillance to those records.

How does the MobileGuard SMS connector relate to the carrier-specific MobileGuard connectors?

The MobileGuard SMS connector ingests SMS data from across all MobileGuard product streams in a firm’s deployment — NetGuard (AT&T and Verizon), MessageGuard, and SecureChat — providing a unified SMS archive regardless of which MobileGuard products are in use. The carrier-specific connectors (MobileGuard AT&T, MobileGuard Verizon, MobileGuard Vodafone) are specifically configured for firms whose MobileGuard deployment is concentrated on a single carrier’s infrastructure.

Which regulations does the Shield MobileGuard SMS connector help firms comply with?

The 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.

Can MobileGuard SMS data be reviewed alongside Bloomberg IB and other channels?

Yes. Shield ingests MobileGuard SMS into the same unified compliance archive as every other channel — Bloomberg IB, email, Teams, and voice — enabling compliance teams to reconstruct the complete business interaction record across all platforms in a single workflow.

Related Terms