Analytics

Fleet posture across all scans

📁

–

Scans analyzed

🐞

–

Findings detected

🎯

–

Rules triggered

⚠️

–

Fleet risk /10

Findings by severity

Top risks (one-line)

Findings by category

CWE distribution

Scan trend & posture

Scan

Upload an EXE, DLL, JAR or ZIP and run all static checks

⬆️

Drop a binary here or click to browse

Supported: .exe .dll .elf .jar .war .zip .class .msi — analyzed instantly, nothing leaves this deployment.

Results

Every scan ever run on this deployment

Loading…

Resources

Full catalog of static checks the analyzer runs

OWASP & industry reference

Standards this analyzer maps findings to

OWASP Top 10 & ASVS

OWASP Top 10 (2021) — the ten most critical app risks; A02:Crypto Failures, A08:Software & Data Integrity map directly to several checks here.

OWASP ASVS — a framework of security requirements and controls for building secure web apps.

OWASP MASVS — the Mobile Application Security Verification Standard for mobile & thick clients.

Testing, tools & CWE

WSTG — the OWASP Testing Guide with step-by-step hands-on tests for each control.

OWASP Threat Modeling — the threat-modeling methodology used to pick these 79 static checks.

CWE — MITRE — Common Weakness Enumeration; every finding carries its CWE-xxxx identifier.

Hardening & secure coding

CWE-693 · Protection Mechanism Failure — why weak crypto, missing safe APIs, and unverified loaders are flagged.

Hardened Windows Applications — Microsoft guidance for ASLR/DEP/safe linkers (PE hardening checks).

Threat Modeling — model assets, trust boundaries, and attack surfaces before testing binaries.

Interpret a report

Each finding = severity (Critical→Info) + one-line description + exact byte that matched (file @ 0x…, section where available).

Grade is a weighted risk score (0–10): 9.0+ = F, higher is worse. Fix Critical/High first, then Medium; Low/Info are hygiene.

Trip to the scanner's /api/meta resp /api/analytics to inspect the machine-readable report.