Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | ValenceSecurityCcfPush |
| Publisher | Valence Security |
| Used in Solutions | Valence Security |
| Collection Method | CCF Push |
| Connector Definition Files | ValenceSecurity_connectorDefinition.json |
| DCR Definition Files | ValenceSecurity_DCR.json |
| CCF Configuration | ValenceSecurity_PollerConfig.json |
| CCF Capabilities | Push |
| Ingestion API | Log Ingestion API — CCF Push connectors use DCR-based Log Ingestion API |
The Valence Security connector enables ingestion of Valence SaaS security alerts and audit logs into Microsoft Sentinel using the Codeless Connector Framework (CCF) Push pattern. Valence's unified SSPM platform detects SaaS misconfigurations, identity risks, and data exposure across Microsoft 365, Google Workspace, Salesforce, GitHub, Slack, and more. This connector streams ValenceAlerts_CL (security alerts) and ValenceAuditLogs_CL (platform audit trail) into Microsoft Sentinel for analysis, alerting, and visualization.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
ValenceAlerts_CL |
? | ✓ | ? |
ValenceAuditLogs_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Create ARM Resources and Provide the Required Permissions
Clicking Deploy push connector resources will create the Data Collection Endpoint (DCE), Data Collection Rule (DCR), and the custom log tables (ValenceAlerts_CL and ValenceAuditLogs_CL). It will also create a Microsoft Entra app registration with a client secret and grant it the Monitoring Metrics Publisher role on the DCR, enabling Valence to push data securely via the Azure Monitor Logs Ingestion API.
This replaces the legacy Workspace ID and Primary Key configuration — no shared keys are used.
Clicking Deploy push connector resources creates the DCE, DCR, and custom log tables. An Entra app registration with a client secret is also created and granted the Monitoring Metrics Publisher role on the DCR. Deploy push connector resources
2. Configure the Valence Platform
Provide the values below to your Valence Security administrator. In the Valence Platform, navigate to Settings → Configuration → SIEM Integration → Microsoft Sentinel and enter these values to enable the CCF Push integration.
TenantIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationSecretNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionEndpointNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionRuleIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Custom-ValenceAlertsCustom-ValenceAuditLogsBrowse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊