Analytics
Findings by severity
Top risks (one-line)
Findings by category
CWE distribution
Issues by severity (Critical → Info)
Scan trend & posture
Scan
Drop a binary here or click to browse
Supported: .exe .dll .elf .jar .war .zip .class .msi — analyzed on this deployment, results private to you.
Results
Groups & sharing
Create a group
How sharing works
On the Results page, open any of your scans and press Share. Add members by username or share with an entire group. Only the scan owner (or admin) can share; everyone else only sees what was shared with them.
Resources
OWASP & industry reference
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 tests for each control.
OWASP Threat Modeling — the methodology used to pick these 199 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): 8.0+ = F, higher is worse. Fix Critical/High first; Low/Info are hygiene.
Signed-in users only see their own scans. Admins can view the fleet.
Users
| Username | Name | Role | Created |
|---|