Description
The Strider Shield connector allows the user to ingest Strider Shield EmailAddresses, EmailDomains, RiskSignals, RiskSignalsDefinitions and Terms events into Microsoft Sentinel.
- Declared author / publisher
- NVISO
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
Read and Write permissions are required.
Workspace
Workspace
Strider Shield API token
A Strider Shield API Token is required. See the Strider Shield documentation on how to create an API token.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
STEP 1 - Use an Authentication Strider Shield API endpoint
Follow the Strider Shield documentation for guidance on this step.
STEP 2 - Choose the correct base URL
There are multiple Strider Shield servers which might host your events. The correct server depends on your license and region.Input the base URL as displayed by the documentation (including 'https://' and without a trailing '/').
STEP 3 - Enter your Strider Shield Details
Enter the Strider Shield Authentication API endpoint, Base URL, Client ID & Client Secret below:
Authentication API endpoint
Base Url
Client ID
Client Secret
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.
- File
- Solutions/Strider Shield/Data Connectors/StriderShieldCCF/StriderShield_ConnectorDefinition.json ↗
- Commit
629d1d3↗- Source identifier
StriderShieldCCF
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC