Posted in Security Operations
ITriage 0.9.0 is out. Quick recap: ITriage is an open source IT triage, repair and update tool for Windows…
jp101216 — Security Engineer | Offensive Security Research & Custom C2 Tooling
ITriage 0.9.0 is out.
Quick recap: ITriage is an open source IT triage, repair and update tool for Windows and Linux. Rust engine, Tauri desktop app, command line. It grew out of the scripts I used while on a healthcare IT service desk. It's MIT-licensed now.
WHAT I NEVER ANNOUNCED
• Security posture (pictured, with sample data): BitLocker on the system drive, antivirus and the age of its definitions, EDR sensors, the firewall (critical when it's off for the profile in use), Secure Boot, TPM, UAC, and who is an administrator of the PC. On Linux: LUKS, firewalld/ufw/nftables, and sudo and wheel members.
• Sign-in & account lockouts: is the account locked, disabled or about to expire, and what on this PC keeps locking it after a password change: saved credentials, a disconnected session, services and scheduled tasks running as that account, and failed sign-ins in the Security log. Saved credentials are listed by name only. The secrets are never read.
• BitLocker suspension: before a manufacturer's BIOS or firmware tool runs, BitLocker is suspended for one restart, so the PC doesn't come back asking for its recovery key. If protection is on and can't be suspended, nothing is installed.
• Hardening for when it runs elevated: Windows' own tools are started by full path, never by bare name. The manufacturer's update tool only runs from a folder standard users can't write to. A profile that a standard user dropped into ProgramData is ignored. On Linux, programs run as root come from the system's folders, not PATH.
• Likely cause: every report opens with what the evidence points to and why. Fixed rules, not a model, so the same findings always give the same answer.
BUGS WORTH ADMITTING
Two of these releases started as a review of the one before. Three things those reviews found:
• A one-click fix could start a real firmware run. After a fix, the tool re-checks the module the finding came from, and on the firmware module that re-check ran the install, even from a preview. A fix now never repeats a change.
• An opened report could write outside the history folder. The saved file's name used the report's own date untouched, so a crafted report could name another folder. Names are now built only from letters, digits and hyphens.
• The case bundle's privacy pass left Wi-Fi network names in: it looked for a field called "SSID", and the Wi-Fi check calls it "Network". It also shredded what wasn't private, such as system paths, version numbers and 8.8.8.8. Both directions are fixed in 0.9.0.
All three are in the release notes.
EVIDENCE FOR ESCALATION
• Change timeline: updates, installs, driver and service changes, restarts and Group Policy processing in plain sentences, placed against when the problem began. The report says a nearby change is a possible link, not proof.
• Recordings: CPU, memory, connection probes and Wi-Fi signal while the user reproduces the issue, with a marker for the moment it happens. No packet contents, screenshots or tokens.
• Entra & Microsoft 365 sign-in state (no tokens are read) and Wi-Fi/802.1X authentication history.
• Case bundles: a ZIP for the next tier with consistent pseudonyms, a preview of every file before export, opt-in logs and SHA-256 digests.
• New in 0.9.0: What's using the space, Startup & sign-in speed, and a guided "the whole PC is slow" workflow.
NOT TESTED YET
252 automated tests on Linux, 249 on Windows and 19 in a browser, and the checks run for real on CI runners. But nothing has run on a domain, as a standard user on Windows, or on a physical Windows workstation, and the fixes that change account state have never touched real state. The release notes list all of it. The Windows installers are still unsigned.
Try the interface in your browser (sample data, nothing to install): https://jp101216.github.io/ITriage/
Code, downloads and release notes: https://github.com/jp101216/ITriage

7 reactions · 2 comments
Comments
Liam R.: Are you planning on adding MAC support?
jp101216: Liam Romanis That is in fact on the docket!