Security and trust
What EndpointWorks checks, how your organization's data is kept apart, and the limits we know about. This page describes the product as it runs today.
Package checks
| Check | What it does | Result |
|---|---|---|
| Manifest policy | HTTPS installer URL, a valid SHA-256, a known installer type and a publisher. | Finding |
| Installer hash | Downloads the vendor installer and compares its SHA-256 with the manifest. Uploads are hashed while they stream, and re-hashed from storage before a scan. | A mismatch is a critical finding |
| Malware scan | Antivirus scans the installer bytes. Signatures update automatically, and catalog installers are rescanned at least every 7 days. | A detection is a critical finding for every organization |
| Static analysis | File type, architecture, whether a signature is present, known packers, entropy. | Packed: medium. Unsigned: low |
| Hash reputation | Looks up the SHA-256 at MalwareBazaar, when the platform has it configured. | Known-bad hash is critical |
| Vulnerabilities | Matches versions against NVD, CISA KEV and FIRST EPSS. Your rules decide what blocks approval and what is only highlighted. | Your policy |
| Your advisories | Known issues you record for a package and a version range. | Finding, your organization only |
"Checks passed" means these checks found nothing. It doesn't prove an installer is safe. A scan that couldn't finish is never shown as clean, and the version can't be approved until a scan succeeds.
Approval
Devices only see versions that someone approved, or that passed checks under an auto-approve policy you turned on. An open finding at or above your Block approval at severity blocks approval, and stops an approved version from being served.
Organization isolation
- Your organization comes from your sign-in session, never from a value a client sends.
- Every query on your data filters by your organization. Tenant-owned API routes are tested for cross-organization access.
- A private package is visible only to you, even if another organization uses the same identifier.
Source keys
Each source key is a random 256-bit value, stored only as a SHA-256 hash and shown once. Use one per deployment channel. Revoking a key stops every device using it from getting updates. An unknown or revoked key gets the same 404 answer.
Sign-in and roles
- People sign in through ZITADEL with OpenID Connect, with MFA or your own identity provider. The EndpointWorks API never handles passwords.
- Connect your identity provider with OIDC or SAML 2.0. On Business and up, you can require it for everyone.
- Eight roles, from Super admin to Service desk. Nobody can grant a role above their own.
API tokens
Tokens are hashed at rest and shown once. Each has explicit scopes, which can't exceed the owner's role, and an expiry of at most 365 days. A token can't create another token.
Audit log
Approvals and rejections with their reason, policy changes, uploads, catalog changes, keys, roles, identity providers and tokens. Secret values are never written to the log.
Support access
EndpointWorks staff can't see your organization by default. Support access is a time-limited grant. Your admins choose whether they are only notified or must approve it, can revoke it at any time, and can see every request made under it.
The agent
The optional Windows agent reports app names, versions, publishers and product codes, plus device facts. It never sends file paths, URLs or user names. Managed actions are signed by the server and bound to the installer's hash.
Known limits
- Installers over the verification size limit (300 MB by default) can't be hashed or scanned by EndpointWorks. They show Could not verify. winget still checks the hash on the device.
- The signed agent MSI is not published yet. The agent's Managed mode is in preview.
- No third-party audit report (SOC 2 or ISO 27001) is available yet.
Report a vulnerability
Email [email protected] with the steps to reproduce. Please don't test against other customers' data.