Security & safety

Safe to run on a computer you're responsible for

A troubleshooting tool shouldn't leave you with a second problem. Here's what Muon Insight does, what it asks before doing, and what it never touches.

01Isolation

Every module starts from a clean session

Each module runs in a PowerShell session of its own, opened fresh and thrown away afterwards, so one module's variables, imported modules and preferences never reach the next. Modules that need PowerShell 7 run in a separate worker process, and remote work goes through a separate host process again. You can cancel a running task.

02Confirmation

Changes wait for you

Diagnostics only read. Actions that change anything ask for explicit confirmation before they start.

Muon Insight hosts Windows PowerShell inside itself and opens a fresh session for each module, discarding it afterwards, so one module's variables, imported modules and preferences never reach the next. Modules needing PowerShell 7 run in a separate worker process, and remote work goes through a separate host process. A session does not isolate anything process-wide, such as environment variables. MUON INSIGHT Hosts Windows PowerShell 5.1 and enforces each module's timeout. FRESH SESSION Windows Update Diagnostics Session opened, used, discarded FRESH SESSION Certificate Health Session opened, used, discarded FRESH SESSION DNS Consistency Running now in its own session Variables, imported modules and preferences do not carry from one module to the next. A session cannot isolate what is process-wide, such as environment variables. SEPARATE PROCESSES POWERSHELL 7 WORKER pwsh.exe Runs the modules that need PowerShell 7, when it is installed. REMOTE HOST powershell.exe Holds the WinRM sessions for work on remote computers. Any running task can be cancelled.

03Remote computers

Your identity, and nothing left behind

Remote runs use WinRM with your own signed-in Windows identity, so they can only do what your account is already allowed to do. Files staged on the remote computer are removed after each run.

Muon Insight never changes

  • WinRM TrustedHosts
  • Firewall rules
  • WinRM listeners
  • Credentials

04Controls

Built for managed environments

  • Credentials stay in Windows

    ServiceNow credentials are stored in Windows Credential Manager, never in configuration files.

  • Signed content

    Content repository snapshots can be signed, and computers accept content only from a pinned publisher certificate.

  • Admin features are gated

    The Administration page appears only for members of approved Active Directory groups or approved users.

  • Locked settings

    Configuration is layered, and administrators can lock the settings that matter.

  • Redaction in reports

    Report and support bundle exports support configurable redaction, so you decide what gets shared.

  • Clear about elevation

    Muon Insight runs as administrator and asks for elevation when it starts.

Reporting a security issue

If you think you've found a security problem in Muon Insight, please report it privately using GitHub's Report a vulnerability button on the repository's Security tab. Please don't post details in a public issue.

[TODO: enable private vulnerability reporting on the GitHub repository; add a security email and /.well-known/security.txt once email exists]

Your data stays with you

Muon Insight doesn't send data to Muonix Labs. It connects only to the computers and services you point it at: remote computers over WinRM, your own content repository, or your ServiceNow instance. The Chrome log collection module, when you run it, opens Google test pages in Chrome to capture network logs.

Muon Insight has no AI features. The websites set no cookies and use no analytics.

Free public beta

Try it on your next ticket

Muon Insight is free during the public beta. Download it from GitHub.