SOS Universal App Shield
Generic protection for software, applications and games — including tools SOS has never seen before.
Known or unknown, SOS applies the same safety basics.
Use native operating-system trust, local file hashing, network visibility, permissions and your own connector definitions. Unknown does not automatically mean dangerous.
File & hash reputation
Check executable/file SHA-256 against the SOS Threat Graph without uploading the file.
Publisher/signature check
Use the operating system signature/trust mechanisms when available.
Connection visibility
Show local outbound connections and let endpoint firewalls enforce user-approved rules.
Permissions & privacy
Review camera, microphone, location, startup and other permissions where the OS exposes them.
Update watch
Flag outdated SOS agents and support connector-specific update reminders.
User connectors
Teach SOS about a new app, game, software or website with declarative rules — no code required.
Check an app or game on your computer
Desktop agents 0.16 add file-intel <path>. SOS calculates the file hash locally, checks the real file format and extension mismatch, verifies OS signature when applicable, and combines Magika, YARA-X and capa when those local engines are installed. The default command does not upload the file or its hash.
On iPhone/iPad, Apple does not expose Windows-style process/file inspection to ordinary third-party apps. SOS therefore uses network, URL, privacy and account protections instead.
Safety rules
- Unknown software is never automatically labelled malicious solely because it is unknown.
- SOS can hash a selected executable locally and query reputation by hash; the file itself is not uploaded by the generic check.
- Firewall/app blocking changes require an explicit user action and OS permission.
- A connector can add context, official domains and executable names, but cannot execute arbitrary code.
- Platform capabilities differ: iOS does not expose Windows-style process inspection to third-party apps.