Open Systems Data Connector for Microsoft Sentinel

Solution: Open Systems

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

Attribute	Value
Publisher	Open Systems
Support Tier	Partner
Support Link	https://www.open-systems.com/support
Categories	domains
First Published	2025-05-12
Solution Folder	Open Systems
Marketplace	Azure Marketplace · Popularity: ⚪ Very Low (0%)

The data connector ingests log data into Microsoft Sentinel using Open Systems Logs API.

Data Connectors
Tables Used
Content Items

Data Connectors

This solution has 1 discovered data connector(s)⚠️ (not in Solution definition):

Open Systems Data Connector ⚠️ 🔶

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

🔶 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 4 table(s):

Table	Used By Connectors	Used By Content
`OpenSystemsAuthenticationLogs_CL` 🔶	Open Systems Data Connector	-
`OpenSystemsFirewallLogs_CL` 🔶	Open Systems Data Connector	-
`OpenSystemsProxyLogs_CL` 🔶	Open Systems Data Connector	-
`OpenSystemsZtnaLogs_CL` 🔶	Open Systems Data Connector	-

🔶 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 5 content item(s) (0 in solution, 5 discovered 🔍):

Content Type	Total	In Solution	Discovered
Parsers	5	0	5

Parsers

Name	Description	Tables Used
AuthASIMParser ⚠️	-	-
FirewallASIMParser ⚠️	-	-
FirewallASIMParserFilter ⚠️	-	-
ProxyASIMParser ⚠️	-	-
ProxyASIMParserFilter ⚠️	-	-

⚠️ Items marked with ⚠️ are not listed in the Solution JSON file. They were discovered by scanning the solution folder and may be legacy items, under development, or excluded from the official solution package.

Release Notes

Version	Date Modified (DD-MM-YYYY)	Change History
3.0.0	12-05-2025	Initial Solution release.