✨ New Connector - Network Security

Synqly has released a new Network Security Connector for reaching cloud network traffic logs through a single normalized API. Two operations are available: query_traffic_log_configurations discovers the traffic log configurations an integration can read, and query_traffic_events returns traffic from those configurations as OCSF Network Activity. To scope an integration to specific configurations, discover them first and then set traffic_log_configuration_ids on the integration. This connector is in development, so stay tuned for expansion of both providers and capabilities in the coming weeks. Please let us know your network security use cases and we will consider adding support for them in an upcoming release.

✨ New Provider

• Add AWS Network Security Provider, discovering VPC Flow Logs and reading traffic events from both CloudWatch Logs and S3 destinations.

• Add Azure Network Security Provider, discovering Network Watcher flow log configurations and reading traffic events from Azure Blob Storage destinations. Configuration IDs accept either a short flow log name or a full ARM ID.

• Add Google Cloud Network Security Provider, discovering both Network Management VPC flow log configurations and Compute subnetworks with flow logging enabled, and reading traffic events from Cloud Logging.

✨ Enhancement

• Publish AWS, Azure, and Google Cloud provider configuration guides for the Network Security Connector.

✨ Enhancement

• Accept inclusive gte and lte bounds on Jamf device.last_seen_time, in addition to the exclusive gt and lt already supported. Scheduled operations against a Jamf integration inject an inclusive bound, so a schedule pointed at Jamf previously failed on every run.

🐛 Bug Fix

• Fix Jamf device.last_seen_time upper bounds losing records in the boundary second. Jamf requires whole-second bounds, and rounding an lte bound down excluded devices last seen within that second.

✨ Enhancement

• Improve ServiceNow Vulnerability Response Create Findings. Findings now map OCSF asset and finding fields — source, source ID, IP, hostname, MAC, and related CI identifiers — into the vulnerability staging table, and are submitted in batches of up to 200 with per-item validation errors.

• Rewrite ServiceNow Vulnerability Response Query Assets to query the CMDB directly for configuration items with vulnerable items, reusing the shared asset query pipeline, filters, and transform for consistent results with other asset queries.

✨ Enhancement

• Add the Query Application Scans operation to the Application Security API. GET /v1/app-sec/applications/{applicationId}/scans returns the scan runs recorded for an application as OCSF Scan Activity. The operation is in development.

• Add Tenable Web Application Scanning support for query_application_scans. Note that Tenable does not support server-side filtering by asset, so scans that run under a multi-target scan configuration will not appear in an application's results.

✨ New Provider

• Add GitHub Identity Provider, with query_audit_log, query_users, get_user, query_groups, get_group, and get_group_members support for GitHub Cloud and GitHub Enterprise Server. The provider is in development.

✨ Enhancement

• Add the OCSF 1.3.0 Entity Management event to the event union, so identity providers can emit entity lifecycle activity.

• Support class_uid[ne] and class_uid[not_in] on Microsoft Entra query_audit_log. Excluding sign-in event classes lets you skip the sign-in log scan entirely, which is the slowest of the three Entra log sources.

🐛 Bug Fix

• Fix Microsoft Entra audit log queries timing out when a single log source is slow. Entra reads three log sources — interactive sign-ins, non-interactive sign-ins, and directory audits — and one slow source previously failed the whole request. Queries now apply a time budget per source, retry a stalled source up to twice across pages, and then skip it with an advisory message so the remaining sources stay available.

• Fix Microsoft Entra class_uid[in] filtering on query_audit_log. The operator was advertised but did not take effect, and it now follows the same partial-match behavior as other providers.

• Fix incorrect naming on the OCSF Application Lifecycle event in the default OCSF mapping.

🐛 Bug Fix

• Fix Exchange Online message trace queries skipping or double-counting records at page boundaries. Time bounds are now sent with millisecond precision to match Exchange's native precision, instead of being truncated to whole seconds.

✨ New Provider

• Add Xurrent (formerly 4me) Ticketing Provider, with full ticket, comment, note, attachment, and project support, plus server-side filtering on priority, status, and issue_type.

• Add BMC Helix ITSM Ticketing Provider, with ticket create, update, get, and query support, including comments, notes, and attachments.

✨ Enhancement

• Add first-class parent support to tickets for Jira and Jira Service Management. parent can now be set on Create Ticket, changed with Patch Ticket, and is returned by Get Ticket, accepting either a ticket key or an internal ID. Synqly uses Jira's native parent field rather than the deprecated Epic Link and Parent Link custom fields.

• Document the Jira ticket hierarchy, covering the supported Epic → Story/Task/Bug and Task/Story → Sub-task relationships, invalid-parent behavior, and the Task → Sub-task hierarchy typical of Jira Service Management projects, which often have no Epics.

🐛 Bug Fix

• Fix patching a Jira ticket's parent or Epic relationship failing or silently doing nothing. The parent value was stripped before reaching Jira, so no change was ever sent.

✨ Enhancement

• Return a clear error instead of EOF when Create Integration Token is called with an empty request body.

🐛 Bug Fix

• Fix transient network failures during OAuth token fetch being reported as 401 invalid token endpoint errors. Retryable transport failures are now retried when safe, and genuine failures are reported as connectivity problems rather than credential or configuration problems.

Latest Versions

• Released Synqly SDK versions: 2.0.31, 2.0.32, 2.0.33, 2.0.34, 2.0.35, 2.0.36, 2.0.37, 2.0.38

🐛 Bug Fix

• Fix Go SDK 2.x releases not being importable. The published module path now carries the required /vX suffix, so github.com/synqly/go-sdk/v2 is fetchable from v2.0.31 onward.

Latest Release: v0.1.151

• Service Image Tag: embedded-2026.08.21
• Service Image Tag (NO FIPS): embedded-2026.08.21-no-fips
• Release Date: August 21, 2026