OMEGA SECURITY PRO — THREE-LAYER SECURITY MODEL

Security Model & Protection Boundaries

1. Device / PWA layer

Runs within browser permissions: live browser/device telemetry, credential tools, local phishing heuristics, selected-file SHA-256 and malware/antivirus heuristics, browser-granted folder workflows, File/Malware/Virus PWA vaults, integrity baselines, privacy diagnostics, network/link protection, settings and local security history.

2. Online-assisted layer

When the user initiates a network-dependent function, Omega can use server-assisted selected-file scanning, ClamAV signatures when actually available, website/header analysis, DNS/email-domain checks, privacy-preserving breach queries and other configured remote services. Offline controls remain visible but cannot manufacture an online result.

3. Private server security core

The authenticated Omega Security Core protects the hosted service with rolling site-root integrity snapshots and eligible content backups, malware/virus-oriented web-code scan profiles, File/Malware/Virus server vaults, IP block/allow management, managed .htaccess hardening, logs, runtime/site audits and administrator-only recovery actions.

What the public PWA cannot do

A browser/PWA cannot silently scan every physical-drive file, inspect arbitrary operating-system processes or unrestricted RAM, intercept every packet from other applications, install a kernel driver or replace native antivirus/EDR/firewall software. Being online does not remove those browser security boundaries.

Scope-accurate status: ARMED, ACTIVE, CLEAN, BLOCKED and similar states describe the relevant Omega Security Pro function and its stated scope; they are not whole-device certifications.