Cloud9 Capture Integration

The Arctera Cloud9 connector is an API-based integration that captures, preserves, and supervises Cloud9 call data, including calls and call metadata, for regulatory compliance, audit, and eDiscovery. It is designed for compliance, legal, and IT teams that require a complete and reviewable record of voice communications.

Request a Demo

/content/eds-arctera/contact-us

style

py-0

What Is the Arctera Cloud9 Integration?

The Arctera Cloud9 capture integration uses Cloud9 Calls Data and Management APIs to retrieve and standardize call data from Cloud9 environments. It performs scheduled API-based collection, capturing call records and metadata, and transforms them into complete, archive-ready records for supervision, retention, and discovery.

Within the Arctera Unified Platform, these records preserve voice communication context and detail, enabling compliance, legal, and IT teams to maintain consistent, defensible records across voice workflows with optional access to original source payloads.

t-body

style

bg-grey

Technical Specifications

The following technical details summarize how the Arctera Cloud9 connector operates within regulated environments and how call data is collected, processed, and delivered for governance workflows.

t-b-s

Attribute
1. Integration Type
2. Data Ingestion Method
3. Authentication Method
4. Deployment Model
5. Archive Destination
6. Supported Editions
7. Captured Scope Summary
8. Policy Enforcement Stage
9. Regulatory Alignment
Detail
1. API-based integration using Cloud9 Calls Data and Management APIs
2. Scheduled API-based collection runs
3. App Key and Secret authentication with whitelisted IPs and read-only scopes
4. Private cloud or self-hosted Capture deployment
5. Configured archive target within Arctera Unified Platform
6. Requires Firm Admin-generated Cloud9 API credentials
7. Calls, call metadata, user context, optional original JSON attachment
8. Applied during Capture processing before archive delivery
9. Supports SEC, FINRA, CFTC, and regulated voice communication requirements

style

pt-0

What the Cloud9 Connector Captures

check-circle: Call Records: Captures Cloud9 voice call records retrieved through the Calls Data API.

check-circle: Call Metadata: Captures call-related metadata including timestamps, participants, and associated call details.

check-circle: User Context Data: Captures user information retrieved through the Management API for context and attribution.

check-circle: Monitored User Scope: Captures call data based on configured monitored users within the environment.

check-circle: Optional Original JSON Attachment: Captures and attaches original API response data for source-level validation and review.

style

pb-0, pt-md

How the Cloud9 Connector Works

The Cloud9 connector operates as a scheduled ingestion pipeline that retrieves call data from Cloud9 APIs, normalizes records, and delivers them into the Arctera Unified Platform archive for supervision, retention, and eDiscovery workflows.

t-b-s

Step 1: API Credential Configuration

A Firm Admin generates App Key and Secret pairs for both Calls Data and Management APIs. Configure read-only scopes and whitelist required IP addresses.

Step 2: Authentication and Connection Setup

Enter both API credential sets into the Capture collector. Establish secure API-based access to retrieve call data and user context.

Step 3: Scheduled API Data Collection

Capture executes scheduled API collection runs to retrieve Cloud9 call records and metadata without interacting with live call traffic.

Step 4: Normalization and Data Processing

Transform call data and metadata into standardized, archive-ready formats. Optionally attach the original JSON payload for detailed source reference.

Step 5: Policy Processing and Archive Delivery

Apply filters, routing, and policy identifiers, then deliver normalized records to the configured archive target within the Arctera Unified Platform.

style

pb-0

Supported Platforms

The Cloud9 integration operates across Cloud9 environments with API access and Capture deployments within private or self-hosted infrastructure.

t-b-s

small,bright,shadow

Cloud9 Environment with API Access

The integration connects to Cloud9 using API-based access with whitelisted IPs and read-only scopes. It retrieves call data and user context through the Calls Data and Management APIs.

Private Cloud and Self-Hosted Capture Deployment

Capture is deployed within a private cloud or self-hosted environment. It securely connects to Cloud9 APIs, performs scheduled ingestion, and processes call data before delivering it to the archive target.

style

pb-3xl, pt-3xl, bg-borange-005

Compliance & Regulatory Use Cases

t-b-s

event-one,no-badge,no-location,no-datetime

Retain voice trading communications for compliance

Compliance and Risk Teams

When traders or advisors communicate through Cloud9, the Arctera Cloud9 connector captures call records and metadata and preserves them in the Arctera Unified Platform. Teams can retain voice communications to meet SEC, FINRA, and CFTC recordkeeping requirements.

alt

Investigate call activity and trading interactions

Compliance, Legal, and Risk Teams

When investigating trading activity or misconduct, the Arctera Cloud9 connector captures call data and metadata. Teams can review call records and reconstruct interactions, resulting in more complete and defensible investigations.

alt

Apply legal hold and eDiscovery to call data

Legal and eDiscovery Teams

When legal matters require review of voice communications, the Arctera Cloud9 connector captures call records and metadata and preserves them in the archive. Legal teams can search, hold, and produce records for eDiscovery workflows.

alt

Provide audit trail of regulated voice communications

Compliance and Audit Teams

When auditors require visibility into voice communications, the Arctera Cloud9 connector captures call records and metadata. Teams can provide a structured and reviewable record of regulated communications for audit and supervisory workflows.

alt

Frequently Asked Questions

t-b-s

What Cloud9 content does the integration capture?

The integration captures Cloud9 call records and associated call metadata using the Calls Data and Management APIs. It can optionally attach the original JSON payload to provide source-level detail. This ensures both structured and raw data can be preserved for review and analysis.

Does the integration capture Cloud9 data in real time?

No. The integration uses scheduled API-based collection runs to retrieve call data after it is available through Cloud9 APIs. It does not intercept or monitor live call traffic, ensuring no impact to communication workflows.

How quickly is Cloud9 data available in the archive?

Cloud9 data is captured based on scheduled collection runs. Timing depends on the configured ingestion schedule and API availability. Once retrieved, data is normalized and delivered to the archive where it is immediately available for supervision and review.

How is access to Cloud9 data secured?

Access is configured using App Key and Secret credentials for both Calls Data and Management APIs. The integration requires whitelisted IP addresses and read-only scopes, ensuring controlled and limited access to call data.

How does this support regulatory compliance and audits?

The integration preserves call records and metadata as normalized archive-ready output. These records can be retained, reviewed, and produced for regulatory audits, investigations, and legal workflows, supporting compliance with financial regulations.

How is the connector deployed?

The connector is configured in Capture by entering API credentials, setting monitored users, and configuring filters and processing options. Scheduled collection runs retrieve and process call data for delivery to the archive.

How does this differ from native ShareFile retention?

Cloud9 retains call data within its platform. The Arctera integration retrieves call data through APIs, normalizes it, and delivers it to a centralized archive. This enables consistent supervision, retention, and eDiscovery across communication channels.

style

pb-0