SecurityScorecard Ratings for Microsoft Sentinel
Solution: SecurityScorecard Cybersecurity Ratings
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Publisher | SecurityScorecard |
| Support Tier | Partner |
| Support Link | https://support.securityscorecard.com/hc/en-us/requests/new |
| Categories | Security - Others,Security - Network,Security - Vulnerability Management |
| Version | 3.0.0 |
| Author | SecurityScorecard - integrations@securityscorecard.io |
| First Published | 2022-10-01 |
| Last Updated | 2022-10-01 |
| Solution Folder | SecurityScorecard Cybersecurity Ratings |
| Marketplace | Azure Marketplace · Popularity: ⚪ Very Low (0%) |
This package includes three Codeless Connector Framework (CCF) data connectors, three KQL parsers, and an associated workbook for the SecurityScorecard offering within Microsoft Sentinel. The CCF connectors ingest 11 company scores from SecurityScorecard (overall score and 10 factor scores) as well as new issue events without requiring an Azure Function deployment. The legacy Function App connectors are retained but marked Deprecated.
Contents
Data Connectors
This solution provides 6 data connector(s):
- [DEPRECATED] SecurityScorecard Factor 🔶
- SecurityScorecard Factors (via Codeless Connector Framework)
- [DEPRECATED] SecurityScorecard Issue 🔶
- SecurityScorecard Issues (via Codeless Connector Framework)
- [DEPRECATED] SecurityScorecard Cybersecurity Ratings 🔶
- SecurityScorecard Ratings (via Codeless Connector Framework)
🔶 CLv1: This connector ingests into a table that uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g.
_s,_d,_b,_t,_g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.
Tables Used
This solution uses 6 table(s):
🔶 CLv1: This table uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g.
_s,_d,_b,_t,_g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.
Content Items
This solution includes 4 content item(s):
| Content Type | Count |
|---|---|
| Parsers | 3 |
| Workbooks | 1 |
Workbooks
Parsers
| Name | Description | Tables Used |
|---|---|---|
| SecurityScorecardFactor | - | SecurityScorecardFactorHistory_CL (read)SecurityScorecardFactor_CL (read) |
| SecurityScorecardIssue | - | SecurityScorecardIssuesHistory_CL (read)SecurityScorecardIssues_CL (read) |
| SecurityScorecardRatings | - | SecurityScorecardRatingsHistory_CL (read)SecurityScorecardRatings_CL (read) |
Release Notes
| Version | Date Modified (DD-MM-YYYY) | Change History |
|---|---|---|
| 3.0.0 | 07-08-2026 | Migrated the Ratings, Factor, and Issue Data Connectors to the Codeless Connector Framework (CCF), removing the need for an Azure Function App deployment. Added multi-instance support: each connector uses a DataConnectorsGrid and ContextPane, so one independently-managed connection can be created per SecurityScorecard portfolio, scoped server-side by Portfolio ID. Added an optional own-company "My Scorecard" domain to ingest your own organization's scores alongside portfolio companies. Ingest real dated score, factor, and issue history, enriched with company industry. Marked the legacy Python Function App Data Connectors as deprecated. They are retained in the solution, not removed, so existing deployments continue to work. Added Parsers that unify legacy ( *_CL) and CCF (*History_CL) data for backward compatibility. Updated the Workbook to query through the new parsers. |
| 2.0.0 | 01-10-2022 | Solution release with three Azure Function App data connectors (Ratings, Factor, Issue) and the SecurityScorecard workbook. |
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊