Skip to content

set scanType to socket_tier1 when creating reachability full scans#1014

Merged
John-David Dalton (jdalton) merged 2 commits intov1.xfrom
tier1-scan-type
Jan 6, 2026
Merged

set scanType to socket_tier1 when creating reachability full scans#1014
John-David Dalton (jdalton) merged 2 commits intov1.xfrom
tier1-scan-type

Conversation

@mtorp
Copy link
Copy Markdown
Contributor

@mtorp Martin Torp (mtorp) commented Jan 5, 2026

The scan_type is set to 'socket_tier'. This change allows us to distinguish Tier 1 scans from regular full scans, and is a requirement for proper ingestion of Tier 1 alerts into organization-wide alerts.


Note

  • Plumbs scan_type into fetchCreateOrgFullScan and sets it in handle-create-new-scan to constants.SCAN_TYPE_SOCKET_TIER1 when reachability is enabled, otherwise constants.SCAN_TYPE_SOCKET.
  • Adds SCAN_TYPE_SOCKET and SCAN_TYPE_SOCKET_TIER1 constants in constants.mts and exports them.
  • Version bump to 1.1.53 with CHANGELOG entry documenting the new scan_type behavior.

Written by Cursor Bugbot for commit 45b7d05. Configure here.

@mtorp Martin Torp (mtorp) marked this pull request as ready for review January 6, 2026 07:25
@jdalton John-David Dalton (jdalton) merged commit d0e383b into v1.x Jan 6, 2026
8 checks passed
@jdalton John-David Dalton (jdalton) deleted the tier1-scan-type branch January 6, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants