Description
The CTM360 Cyber Blind Spot (CBS) connector provides integration with CTM360's CBS platform to ingest security data across 6 module types: incidents, malware logs, breached credentials, compromised cards, domain infringement, and subdomain infringement. This connector uses the Codeless Connector Framework (CCF) for serverless data collection.
**Data Types:**
- CBSLog_AzureV2_CL
- CBS_MalwareLogs_AzureV2_CL
- CBS_BreachedCredentials_AzureV2_CL
- CBS_CompromisedCards_AzureV2_CL
- CBS_DomainInfringement_AzureV2_CL
- CBS_SubdomainInfringement_AzureV2_CL
- Declared author / publisher
- CTM360
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
Read and Write permissions are required.
Workspace
Workspace
Read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
CTM360 CBS API Key
A valid CTM360 Cyber Blind Spot API key is required to connect to the CBS API endpoint.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
Connect CTM360 Cyber Blind Spot to Microsoft Sentinel
This connector uses the Codeless Connector Framework (CCF) to ingest data from CTM360 CBS into Microsoft Sentinel. Data is collected every 5 minutes across 6 different module types.
This connector creates 6 separate tables for different CBS module types: Incidents, Malware Logs, Breached Credentials, Compromised Cards, Domain Infringement, and Subdomain Infringement.
Step 1: Obtain CTM360 API Keys
To setup this integration, you will need CBS API Key. You can get these keys using the following links:
CBS API Key found from this link: https://platform.ctm360.com/start/integrations after logging with you account
Step 2: Configure Connection
Enter your CTM360 CBS API key and connect to start data ingestion.
CTM360 CBS API Key
Step 3: Verify Data Ingestion
After connecting, data should start flowing within 5-10 minutes. Use the sample queries above to verify data ingestion for each module type.
Note: Initial data ingestion may take up to 30 minutes. The connector polls every 5 minutes with a 5-minute rolling window.
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
9800e51↗- Source identifier
CTM360CBSConnectorDefinition
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC