↳ GitHub sourceConnector
SecurityScorecard Issues (via Codeless Connector Framework)
Description
The SecurityScorecard Issues (via Codeless Connector Framework) connector ingests issue history events from the companies in a SecurityScorecard portfolio into Microsoft Sentinel. Add one connection per portfolio you want to monitor — each connection is managed independently in the grid below. Replaces the Function App connector.
- Declared author / publisher
- SecurityScorecard
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
Read and Write permissions are required.
Workspace
Workspace
SecurityScorecard API token
A SecurityScorecard API token is required. See [SecurityScorecard docs](https://securityscorecard.readme.io/) for how to provision a bot user token.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
STEP 1 - Create a SecurityScorecard API token
As an administrator in SecurityScorecard, navigate to My Settings then Users, create a bot user with Read Only permission, and generate the API token.
STEP 2 - Add a portfolio connection
Add one connection per SecurityScorecard portfolio. Each connection ingests the issue-history events for the companies in a single portfolio and is listed, managed, and deleted independently below. To also ingest your own company's issue events (My Scorecard), enter your company domain in the optional field on one connection.
Add portfolio
Add a SecurityScorecard portfolio
Base URL
API Token
Portfolio ID
Portfolio Name
Your Company Domain (optional - My Scorecard)
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
629d1d3↗- Source identifier
SecurityScorecardIssueCCPDefinition
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC