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

+5 -2
View File
@@ -19,6 +19,7 @@ Redaction is enabled by default and operates on a cloned analysis object. It mas
- computer/host values;
- username/account/e-mail identity fields, including domain-qualified accounts, SIDs and machine accounts;
- domain-name fields (`SubjectDomainName`, `TargetDomainName`), DNS query names and fully qualified host names with three or more labels in free text (two-label names such as `app.exe` are left alone);
- e-mail addresses in free text;
- IPv4 and IPv6 addresses in free text or IP-address fields;
- Windows and UNC paths (including spaces/parentheses) and path-like fields;
@@ -26,12 +27,14 @@ Redaction is enabled by default and operates on a cloned analysis object. It mas
- known structured identities propagated into summaries, incident titles and reasons;
- the source filename in the exported report.
The UI previews replacement counts by type before export. The original in-memory analysis is never modified by the redaction function. The source name is replaced with `[REDACTED_SOURCE].evtx` when redaction is enabled. JSON and Markdown carry the same redacted normalized analysis and parse-completeness metadata.
Replacements are consistent pseudonyms: the same value always becomes the same numbered token (`[REDACTED_HOST_1]`, `[REDACTED_IDENTITY_3]`), so an exported report still shows which events share a host or account without revealing it. The UI previews replacement counts by type before export and lists the field names whose values were exported without masking, so a reviewer can check them explicitly.
Redaction runs in a Web Worker when Reports or an export needs it, never on load, so large analyses do not block the page. If the worker cannot run, the same function runs in the page; if redaction fails, export stays disabled rather than falling back to raw data. The original in-memory analysis is never modified by the redaction function. The source name is replaced with `[REDACTED_SOURCE].evtx` when redaction is enabled. JSON and Markdown carry the same redacted normalized analysis, campaigns and parse-completeness metadata. The source SHA-256 is kept in redacted exports: it identifies the file, not a person, and lets the recipient verify which evidence was analyzed.
Redaction can be disabled when a raw forensic export is explicitly required, but that is an explicit user choice and the warning remains visible.
## Limits
The API enforces a 50 MiB file limit, a bounded request body independent of `Content-Length`, parser event/time budgets, bounded normalized strings/fields/output and bounded parse concurrency. These controls reduce accidental resource exhaustion; they are not a guarantee against every parser implementation vulnerability.
The API admits an upload (up to the parse concurrency plus a small queue) before the multipart body is spooled to the in-memory `/tmp` tmpfs, so a burst of large uploads gets a fast `503` instead of exhausting it. The API enforces a 50 MiB file limit, a bounded request body independent of `Content-Length`, parser event/time budgets, bounded normalized strings/fields/output and bounded parse concurrency. These controls reduce accidental resource exhaustion; they are not a guarantee against every parser implementation vulnerability.
Redaction is a best-effort privacy layer, not a formal DLP engine. Application-specific free-form values may contain sensitive data that cannot be inferred safely. Review exports before sharing them outside the intended context.