Publish EventLens v1.1.0 (#1)

This commit was merged in pull request #1.
This commit is contained in:
Jens committed 2026-11-20 12:20:18 +00:00
1 parent c0ade21029
commit 87432f3283
63 files changed
+7381 -1420

No files matched your search

+8 -6
View File
@@ -18,17 +18,19 @@ It preserves source evidence, makes every grouping explainable, and keeps the an
EventLens is deliberately not a SIEM, a full Windows Event Viewer replacement, a cloud platform or an AI product. It has no database, authentication, telemetry, background worker, cloud account or LLM requirement. It focuses on one compact job: reconstructing a bounded incident story from Windows event records.
## v1.0.6 capabilities
## v1.1.0 capabilities
- Parses real EVTX in memory with the Rust-backed `evtx` engine.
- Enforces a 50 MiB file cap plus a receive-level request cap, 100,000-event cap, cooperative 8-second parse budget and bounded normalized output.
- Reports `complete`, `partial` or `failed` parser status with stable issue codes, retained/skipped metrics and export metadata.
- Normalizes System, EventData and UserData into a stable evidence contract; unreliable timestamps remain explicit and are never converted to epoch evidence.
- Correlates provider/channel-scoped startup, shutdown, service, DNS, authentication and crash patterns using stable rule IDs, incident IDs and evidence event IDs.
- Correlates provider/channel-scoped startup, shutdown, service failure and installation, DNS, failed sign-in, password-spray, lockout, account-change, log-clearing and crash patterns using stable rule IDs, incident IDs and evidence event IDs.
- Keeps unmatched warning/error evidence visible and compresses repeated signatures without deleting source events.
- Summarizes sustained activity in campaigns that link adjacent incident windows for the same rule and key.
- Shows the uploaded file’s SHA-256 and size in Reports and exports.
- Supports drag/drop, search, category/level/provider filters, informational-noise suppression, incident focus and ±1/5/15/60-minute evidence windows.
- Shows the rule, reason, time window and exact evidence IDs behind each incident.
- Exports semantically equivalent JSON and Markdown in the browser. Redaction is enabled by default and previews host, identity, e-mail, IP, path and source-name replacement counts before export.
- Exports semantically equivalent JSON and Markdown in the browser. Redaction runs in a Web Worker, uses consistent pseudonyms, and previews replacement counts and unmasked field names before export.
- Uses `no-store` responses, security headers, bounded parse concurrency, sanitized source names and no intentional upload persistence.
- Virtualizes large timelines so a 100,000-event analysis does not create 100,000 DOM rows.
- Includes a deterministic demo fixture plus a pinned-hash public real-EVTX qualification fixture in CI and Playwright.
@@ -56,7 +58,7 @@ Redaction is a privacy aid, not a formal DLP engine. Review an export before sha
## Portfolio walkthrough
1. Open the deployed instance or start EventLens locally.
2. Select **Load demo** for a deterministic six-event walkthrough.
2. Select **Load demo** for a deterministic walkthrough that includes a sign-in campaign and account and service changes.
3. Review the source/completeness summary in **Analysis** and select an incident.
4. Investigate the linked evidence in **Timeline** with search, facets, focus and time windows.
5. Use **Hunting** for combined event-ID, provider, category, level, host and incident-membership searches.
@@ -130,7 +132,7 @@ The private canonical repository maintains its own validation and deployment wor
## Deployment and access
Compose publishes port 1252 on all host interfaces. For local use, change the mapping to `127.0.0.1:1252:8000`. There is no built-in authentication; use network isolation and an authenticated HTTPS reverse proxy before allowing other users to upload sensitive evidence. Configure the build revision via `GITEA_COMMIT_SHA` when reproducible deployment identity is needed.
Compose binds port 1252 to loopback by default. Configure network isolation and an authenticated HTTPS reverse proxy before exposing it to other users. Set `EVENTLENS_REVISION` at build time when reproducible deployment identity is needed.
The screenshots show the deterministic bundled demo, not a real incident or an uploaded customer log.
@@ -148,4 +150,4 @@ No project-wide license file is included in this repository. Publishing the sour
## Public source distribution
The private canonical repository remains the development source. Reviewed snapshots are synchronized automatically to `EventLens-Public` after changes reach its default branch. The public export contains application source, dependency locks, generic deployment examples and selected demo visuals; private Git history, infrastructure workflows and operational records are excluded. `PUBLIC_SOURCE_MANIFEST.json` identifies the exact source revision and file hashes.
The private canonical repository remains the development source. Reviewed snapshots are published to `EventLens-Public` from the canonical default branch. The public export contains application source, dependency locks, generic deployment examples and selected demo visuals; private Git history, infrastructure workflows and operational records are excluded. `PUBLIC_SOURCE_MANIFEST.json` identifies the exact source revision and file hashes.