Unknown tenants and suspended tenants are now rejected as the very
first step in SecurityValidator before any certificate, rate-limit,
or hardware check is performed. Adds TryGetConfigurationAsync to
TenantConfigurationService (no auto-create, cache-aware) and inserts
the gate in ValidateRequestAsync — covering RegisterSession,
IngestEvents, GetAgentConfig, and GetDiagnosticsUploadUrl.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- ThemeContext: default to system preference (prefers-color-scheme) when no
manual preference is stored in localStorage; listen for OS-level changes
when user has not overridden; toggleTheme now explicitly persists to localStorage
- Navbar: add standalone sun/moon icon button to Tier 1 right-side icon row
(left of notification bell); remove dark mode entry from overflow menu
- Landing page: replace MSP Support (Planned) with Fleet Health, replace
Intelligent Alerts with Diagnostics Collection — both existing shipped features
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- publish totalSignedUpTenants in platform-stats blob JSON (was computed but not serialized)
- add totalEventsProcessed and lastUpdated timestamp to landing page stats bar
- replace plain welcome card with structured onboarding block: gradient accent, numbered steps with doc deep-links (/docs#setup, /docs#agent-setup), and polished quick-link cards with hover states
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Devices that continuously send data beyond a configurable window (default
24h) are now automatically blocked by the daily maintenance function,
regardless of session status. Introduces LastEventAt tracking on session
entities (written on every event batch ingest) to enable efficient
per-tenant queries without scanning the Events table.
- Add LastEventAt field to SessionSummary and session entity writes
- Add GetExcessiveDataSendersAsync query (StartedAt < cutoff AND LastEventAt > cutoff)
- Add BlockExcessiveDataSendersAsync maintenance step with idempotency check
- Add MaxSessionWindowHours and MaintenanceBlockDurationHours to AdminConfiguration
- Expose both settings in Device Block Management section of Admin Config UI
- Include HelloDetector agent changes
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Shows a prominent purple banner when galacticAdminMode is active,
clearly indicating that data is aggregated across all tenants.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Galactic Admins can block a device by serial number from the admin-configuration
page. The block is enforced at ingest time (after security validation, before
body decompression) and is configurable in duration (default 12h, max 30 days).
The agent receives a DeviceBlocked signal in the IngestEventsResponse and stops
all uploads for the session. Blocks persist across backend restarts via a new
BlockedDevices table in Azure Table Storage, with an in-memory cache for fast
ingest lookups.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The backend was refactored to run security checks before parsing the
request body, using X-Tenant-Id from the HTTP header. The agent was
not sending this header, causing every ingest call to fail immediately
with 400 BadRequest before any events were processed.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Agent/Backend: configurable MaxCollectorDurationHours (default 4h) stops interval-based collectors on stuck sessions; setting exposed in global admin config
- Backend: IngestEventsFunction now runs all security checks (cert, rate limit, hardware whitelist, Autopilot validation) before touching the request body, eliminating unnecessary gzip decompression and JSON parsing on rejected requests; added TenantId header/body cross-check
- Backend/Frontend: SignalR eventStream refactored from full event payload to signal-only (newEventCount); frontend fetches canonical event state from Table Storage on each signal, eliminating gap issues and phase-name race conditions
- Frontend: fetchEvents replaces (not merges) event list; phaseName computed at render time in eventsByPhase useMemo; 30s catch-up fetch added as safety net
- Frontend: session event export tool in admin-configuration (teal block) — fetch by sessionId+tenantId, download timeline export (.txt with UI phase grouping) and raw CSV export
- Frontend: changelog page (/changelog) with Private Preview context and first architecture entry; dashboard feedback banner updated to link changelog; Navbar overflow menu gains Preview Changelog link
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The primary download button uses /api/download/bootstrapper (Azure Function).
A secondary "Alternate download via GitHub" button now links directly to the
raw script in the repository, so users can always get the script even if the
Function API is unavailable.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
TenantContext no longer uses the legacy 'deadbeef' fake placeholder ID — it now
initializes to empty string and cleans up any stale value from localStorage.
This lets every page guard with the simple !tenantId check (consistent with
settings.tsx) instead of comparing against a magic string.
All 7 affected pages now wait for a real tenantId before making API calls, and
tenantId is included in useEffect deps so fetches retry automatically once auth
completes. The previously patched dashboard and sessions/[sessionId] pages are
cleaned up to use the same pattern.
All pages now use addNotification() for API errors instead of silent console.error
or local error state, giving users visible feedback when backend calls fail.
Fullscreen error pages in audit and usage-metrics are replaced by notifications,
keeping the page content visible so users can retry from the notification area.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
TenantContext starts with a 'deadbeef' placeholder ID and updates asynchronously
once AuthContext finishes loading. Dashboard and session detail pages were firing
their initial API fetches before the real tenantId was available, causing backend
calls with the wrong tenant ID and resulting in failures.
Added guard in both pages to skip the fetch until tenantId is no longer the
default placeholder. Also added tenantId and galacticAdminMode to the session
detail useEffect dependencies so the fetch retries automatically once the real
ID arrives.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Remove UploadBundleRequest, UploadBundleResponse classes (ApiModels.cs)
- Remove UploadBundle API endpoint constant (Constants.cs)
- Remove GetBundleUploadUrlAsync method (BackendApiClient.cs) — no callers anywhere
- Fix HardwareInfo: Lenovo devices report the marketing model name in
Win32_ComputerSystemProduct.Version, not Win32_ComputerSystem.Model;
add Lenovo-specific WMI fallback for correct model string
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add /api/diagnostics/upload-url to anonymous routes in AuthenticationMiddleware so the
new device-cert-authenticated endpoint is not blocked by the JWT middleware
- Add DiagnosticsUploadResult value object to DiagnosticsPackageService carrying BlobName,
SasUrlPrefix (truncated, safe to log), and ErrorCode
- Change CreateAndUploadAsync return type to DiagnosticsUploadResult for richer error context
- Add BuildSasUrlPrefix helper to produce a safe truncated URL for event data
- Change UploadToBlobStorageAsync to return (bool success, string errorCode) tuple
- Update MonitoringService to populate sasUrl and errorCode in diagnostics_upload_failed
event data dict for visible timeline diagnostics
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Instead of inline banners on the settings page, expired or near-expiry
SAS URLs now fire a persistent warning/error notification to the bell icon.
The notification includes a direct "View" link to /settings#diagnostics.
NotificationContext: added optional href field to Notification; addNotification
signature extended with href parameter for both keyed and unkeyed paths.
Navbar: notifications with href render a "View" link that marks the
notification as read and navigates to the target anchor.
Settings: removed inline SAS warning banners; addNotification called on
config load when expiry <= 7 days (warning) or expired (error); diagnostics
section gets id="diagnostics" anchor for deep-linking.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Instead of delivering the long-lived SAS URL in the agent config response
(where it was cached on disk for the full enrollment period), the agent now
requests a short-lived URL via POST /api/diagnostics/upload-url just before
uploading — the URL is held in memory only and never written to config.
Backend: new GetDiagnosticsUploadUrlFunction with same cert/hardware
security validation as all other agent endpoints; GetAgentConfigFunction
now sends DiagnosticsUploadEnabled (bool) instead of the SAS URL;
ConfigVersion bumped to 6.
Agent: BackendApiClient.GetDiagnosticsUploadUrlAsync added;
DiagnosticsPackageService fetches URL on-demand via the API client;
AgentConfiguration.DiagnosticsBlobSasUrl replaced by DiagnosticsUploadEnabled.
UI: settings page parses SAS URL expiry (se= param) and shows expiry date
inline with colour coding; expired or near-expiry URLs trigger
error/warning notifications at the top of the page on load.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add missing globals.css overrides: text-purple-900, text-sky-900,
text-emerald-900, text-rose-900, bg-rose-50, border-rose-200,
divide-gray-100 (row dividers)
- Refactor SettingsGroup: split color prop into color + borderColor so
the outer border renders with an explicit dark-aware color class
- Add bg-white to SettingsRow and Danger Zone body so they pick up the
global .dark .bg-white override correctly
- Change default text in SettingsRow to text-gray-500 (already has dark
override) instead of text-gray-400
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Informs users that rules are being actively validated and changed,
occasional redeploys and inconsistent analysis results are expected.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Remove ANALYZE-ESP-002 (Security Policy Application Failure): too many
false positives, the pattern matched unrelated EnforcementState events
- Disable ANALYZE-CORR-001 (Slow Network) by default: download_progress
events don't reliably indicate slow network, needs rethinking
- Disable ANALYZE-APP-009 (App Download Stalled) by default: relies on
download_progress.status=failed which doesn't reflect actual stall
- Rename ANALYZE-APP-002 from "MSI Installation Error" to "App Installation
Error": broadens scope, removes CCM/SCCM log reference (Intune-only),
points to IME logs instead
- Also include Enabled in auto-update comparison so Enabled=false changes
propagate to existing tenants on next seed check
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
GetRuleResultsFunction was ignoring the tenantId query parameter and
always using the tenant from the JWT token. As a result, a Galactic
Admin viewing another tenant's session would get 'No events found'
because the data was stored under the session's tenant, not the admin's.
Now follows the same pattern as GetSessionEventsFunction:
- Read tenantId from query parameter (sent by the frontend as effectiveTenantId)
- Fall back to JWT tenant if not provided
- Allow cross-tenant access only for Galactic Admins (403 otherwise)
- Use the effective tenant ID for all storage calls and rule engine runs
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Previously, AnalyzeSessionAsync always loaded existing results and
skipped rules already evaluated (deduplication check). The reanalyze
flag from the API endpoint was never passed through, so clicking
"Analyze Now" only returned cached results.
Fix:
- Add `reanalyze` parameter to `AnalyzeSessionAsync`; when true, skip
deduplication so all active rules evaluate against the full event stream
- In GetRuleResultsFunction, pass reanalyze=true and delete stale stored
results before writing the fresh evaluation output
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- RuleCondition interface gains 6 optional fields:
correlateEventType, joinField, timeWindowSeconds,
eventAFilterField, eventAFilterOperator, eventAFilterValue
- SOURCES constant adds event_correlation
- Condition editor renders extra fields when source=event_correlation:
Event B type, join field, time window, Event A filter row
(shown in indigo-tinted card with a correlation badge)
- Form/JSON tab toggle added to both create and edit forms:
Form view: the existing structured editor
JSON view: full rule JSON in a resizable monospace textarea,
with Apply JSON button to sync back to form and inline error display
- handleCreateRule/handleSaveEdit accept optional formOverride so
JSON-mode save bypasses React state async timing
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces the hardcoded app_state_regression source with a generic
event_correlation source that allows correlating any two event types
by a shared field (e.g. appId), with optional time windows and filters
on both events — all configurable via JSON without backend code changes.
RuleCondition gains 5 new nullable properties:
- CorrelateEventType: second event type (Event B)
- JoinField: field to match across both events (e.g. "appId")
- TimeWindowSeconds: max time between Event A and B
- EventAFilterField/Operator/Value: optional filter on Event A
ANALYZE-APP-010 migrated to use event_correlation source.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The previous rule incorrectly matched any app_install_completed event
against any app_install_failed event without correlating by appId.
Changes:
- RuleEngine: add app_state_regression source that finds apps where
app_install_completed is followed by app_install_failed for the same
appId, with optional DataField filter on the failed event; returns
appId, appName, both event details and errorDetail as evidence
- AnalyzeRule: document new app_state_regression source in comment
- ANALYZE-APP-010: rewrite to use single app_state_regression condition
(IME-ERROR-REPORT filter) + enrollment_complete check; evidence now
contains the exact app name and id that regressed
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
New built-in correlation rule that warns when an app transitions from
app_install_completed back to app_install_failed (IME-ERROR-REPORT)
while enrollment itself completes successfully. Includes remediation
steps for investigating EnforcementState changes and detection failures.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Oliver Kieselbach