IT services · PowerShell · network triage
SpinfoSecurity
Public Windows-focused tools: ranked diagnosis, DNS honesty, clock skew, reachability matrices, and one-page escalations. Built for IT services teams that expect initiative and clean handoffs.
Proof of work
Same pattern every time: measure, rank the cause, fix safely, prove it, escalate only when needed.
Six scripts for second-line style endpoint work: Why-Broken ranks clock/DNS/disk/path failures; Dns-Truth catches resolver lies; Auth-Clock finds SSO-breaking skew; Reach-Matrix separates path vs app; Stack-Reset heals DNS/DHCP with before/after proof; Escalate-Smart writes a one-page brief for senior IT.
Hypothesis #1 with evidence and a suggested fix—not a wall of ipconfig output.
Stack-Reset shows before/after metrics so reboot theater isn’t the default.
Impact, what you tried, evidence, one ask—so senior time isn’t wasted.
Highlight
The IT Triage Toolkit turns everyday L2 judgment into runnable PowerShell: find the real blocker, fix what is safe, and hand senior IT a brief they can act on. ICS OT Protector applies the same discipline to authorized network reachability checks.
Defensive reachability scanners for industrial networks. Same craft as the triage toolkit: scripting, networking, structured findings, and clear authorized-use limits.
Documentation
IT services scales when answers live in searchable docs—not in someone’s head.
Search current industrial advisories by vendor or product, filter by severity, open the official write-up. Model for internal KB tooling: refreshable, filterable, linked to source of truth.
Install steps, conservative timing, protocol command tables, and how to report findings. Written like an internal guide: clear steps, explicit “do not” list, no exploit payloads.
Skills in the repos
Skills you can verify by reading and running the public repos.
Also in the work: Windows · TCP/IP · DNS · DHCP · SSO/clock skew awareness · GitHub
Operating style
Signals that show up in the public repos—and in how the docs are written.
Ship working CLIs and demos, not decks. Prefer a runnable path over a slide.
Findings, limits, and next steps written so teammates can trust the handoff.
Severity labels and remediation notes first—so the urgent path is obvious.
Links
Start with the PowerShell triage toolkit, then the ICS/OT scanners if you want more networking examples.
.\powershell\Why-Broken.ps1 inside it-support-scripts
Accuracy
Public PowerShell IT triage tooling, network reachability checks, and operator documentation you can review in code.
An exploit toolkit. Not Active Directory or IdP account automation. No unauthorized scanning.
Authorized use only. Do not run network scanners against systems without explicit asset-owner permission.