LogonTracer
v2.0.0 open-sourceThe section your link pointed to isn't on LogonTracer's page any more, so we've brought you to the top.
Investigate malicious Windows logon by visualizing and analyzing Windows event log - JPCERTCC/LogonTracer
Summary
LogonTracer is an open-source dfir tool that visualizes Windows Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. logon events as a graph, linking hostnames, IP addresses, and account names so an investigator can see where login attempts originate and which accounts and hosts are involved. It runs as a self-hosted web application backed by a Neo4j database, with logs imported from EVTXEVTXWindows XML-based binary log format used by the Event Log service to store system, application, and security events; cyber tools parse it to extract forensic artifacts from live systems or offline disk images. files, XML, or Elasticsearch via its command-line options, and it is built for DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. analysts and incident responders working through Windows event IDs like 4624, 4625, 4768, and 4769 rather than for general SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. monitoring. Version 2 adds Sigma rule scanning during import and an OpenAI-based analysis engine that maps findings to MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior. tactics, extending it beyond a purely rule-based graph tool. First committed in 2017 and now at 13 contributors, it remains active with 9 commits and 10 releases in the past year.
Investigate malicious Windows logon by visualizing and analyzing Windows event log - JPCERTCC/LogonTracer
How LogonTracer helps
Which accounts and hosts are actually involved in a suspicious logon attempt?
plots hostnames, IP addresses, and account names from imported logon events as a connected graph, so an investigator can see which host authenticated against which account
Which account was the actual target of a brute-force or password-spray attempt?
graphs successful and failed logon events together so repeated failures followed by a success against one account stand out from the surrounding traffic
Did an attacker escalate privileges or add themselves to a privileged group after the initial logon?
tracks account creation, deletion, and security-group membership change events alongside the logon graph so those actions appear tied to the account and host involved
Which hosts saw Kerberos ticket requests or NTLM authentication that don't fit the normal pattern?
renders Kerberos TGT and service ticket requests and NTLM authentication events on the same graph as ordinary logons, so unusual ticket or NTLM activity shows up next to the accounts and hosts it touched
Do these logon events match a known malicious pattern worth escalating?
scans imported events against Sigma rules during import and surfaces the matches in the interface, and can call an OpenAI-based engine to map the findings to MITRE ATT&CK tactics
Where did a directory service object get created or deleted around the time of the incident?
includes directory service object creation and deletion events in the graph, tying them to the account and host that performed the action
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for LogonTracer, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail LogonTracer puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
10 entries
No entries match these filters.
- April 20261
- December 20221
- October 20201
- August 20201
- July 20201
- February 20201
- October 20181
- August 20181
- January 20181
- December 20171
Project health
Issue, contributor and maintainer activity in JPCERTCC/LogonTracer, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 21 of 128 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 21
- Contributors / month 0
- Commits / month 0
- Stars 3,233
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →