Omega Security Pro combines a local-first browser/PWA security layer, online-assisted analysis engines, and a separate authenticated server-security core. Every function stays visible in the interface; the platform automatically distinguishes what can run locally, what requires an internet connection, and what is reserved for protected server administration.
Runs inside the user's browser or installed PWA using browser-permitted capabilities: live browser telemetry, credential tools, phishing heuristics, selected-file hashing and analysis, user-granted folder scanning where supported, local vaults, privacy checks, integrity baselines and performance diagnostics.
When online, eligible functions can call Omega Security Pro server endpoints for deeper analysis such as website and email-domain security checks, network-dependent intelligence, server-assisted selected-file analysis and other services that cannot operate without connectivity.
The authenticated private core protects the hosted Omega Security Pro environment itself with rolling site-root integrity snapshots and eligible content backups, malware/virus-oriented web-code scan profiles, server vaults, IP controls, managed .htaccess hardening, logs, runtime/site audits and administrator-only recovery actions.
The Security Command Center is the central view of the user's current Omega Security Pro session. It combines measured browser/PWA status with results produced by completed security modules. It does not invent a universal preset score: modules that have not been tested remain visibly untested or unavailable until a real measurement exists.
Online/offline state, browser security capabilities, privacy posture, performance measurements and PWA runtime state can update during the session.
The overall posture is based on measurements or completed checks that are actually available. Unsupported browser APIs remain identified as unavailable rather than being guessed.
Credential, phishing, file, malware, antivirus, privacy, website, integrity, vault and performance modules feed their own results back into the broader security experience.
The interface responds to connectivity changes and keeps online-only engines visible even when they cannot currently execute.
Credential Defence performs password-strength analysis locally, generates strong passwords using browser cryptographic capabilities where available, and supports local password-security workflows without requiring an account. A password score is produced only after the user submits a password for analysis.
The phishing engine combines local structural analysis with online-assisted checks where implemented and available. Within Omega Security Pro, the PWA can evaluate external links before navigation and warn or block high-risk destinations according to the application's own risk logic.
Checks can include suspicious URL structure, IP-address hosts, punycode, misleading credentials in URLs, excessive subdomains, insecure HTTP use, risky path terms and suspicious downloadable extensions.
User-supplied messages can be examined for social-engineering indicators, urgency language, credential bait, payment or wallet prompts and suspicious embedded links.
Links activated from within Omega Security Pro can be evaluated before the PWA allows navigation. This protects the Omega application workflow; it is not a system-wide browser extension or operating-system web filter.
The implemented online URL workflow can call Omega's bounded public website-security endpoint for HTTPS, redirects and response-security headers; DNS/email-domain checks use the separate domain-security endpoint. These network-dependent checks run only while connected. No general-purpose reputation feed is claimed by the current public code.
Omega Security Pro can analyse files that the user explicitly chooses or grants access to. The browser/PWA layer can calculate SHA-256 hashes, inspect file metadata and selected file content within browser limits, evaluate suspicious extensions and signatures, and apply heuristic classifications. When online, eligible selected-file workflows can also use server-assisted analysis.
The public PWA and the private server core use separate vault scopes so user-selected content is never confused with protected server-administration files.
Stores eligible user-selected files or records inside application-controlled browser storage when the vault workflow is used.
Stores quarantined copies or records classified by the PWA workflow as malware-risk, subject to browser storage limits and user action.
Stores quarantined copies or records associated with virus-oriented detections or classifications generated by supported scanning engines.
The authenticated server core maintains its own File, Malware and Virus vaults for website/server files. Those privileged vault operations are not exposed to anonymous visitors.
In the browser/PWA, “quarantine” means placing a controlled copy or vault record inside Omega Security Pro's permitted storage. A web application cannot silently delete an arbitrary original file from the user's operating system without explicit browser-granted capability.
For user-selected files, Omega Security Pro can create SHA-256 integrity baselines and later compare files against those saved values. This enables the user to detect whether a selected file has changed since a trusted baseline was recorded.
The private server core separately compares eligible site-root files with its previous integrity snapshot, stores content-addressed backups for eligible files and provides authenticated restore, mark-safe and accept-removal actions. Its server snapshot advances after an integrity scan, so it is a rolling comparison snapshot rather than the explicit persistent baseline model used by the public PWA.
Remote website and domain checks inherently require connectivity because Omega Security Pro must communicate with the target domain or server-side analysis endpoint. These engines remain present in the PWA while offline, but they do not manufacture results when the network is unavailable.
Privacy Defence evaluates security and privacy capabilities exposed to the current browser/PWA session. The result reflects what the browser actually reports; it is not an operating-system forensic scan.
Checks whether the application is running in the secure environment required for protected browser APIs.
Evaluates relevant browser-supported security/privacy features and reports unsupported capabilities accurately.
Omega can report its own application storage usage/quota and locally stored security state where browser APIs permit it.
The PWA cannot silently read arbitrary files, complete browsing history, unrelated application data or unrestricted operating-system memory.
Performance diagnostics are generated from the current browser/device session using measurements and browser APIs that are genuinely available. Values can differ between devices, browsers, power states, network conditions and browser privacy policies.
Device memory values exposed by browsers can be approximate and privacy-coarsened. Browser storage estimates refer to storage available to the web/PWA origin, not unrestricted total SSD/HDD capacity.
Omega Security Pro monitors the browser's connectivity state. Local-capable engines remain available offline after the necessary PWA resources have been cached. Network-dependent functions stay visible so users always see the complete Pro architecture.
| Function type | Online | Offline | Behaviour |
|---|---|---|---|
| Password strength / generation | Available | Available | Runs locally where supported. |
| Local phishing / URL heuristics | Available | Available | Uses local rules; online intelligence is added only while connected. |
| Selected-file hashing / local heuristics | Available | Available | Runs against files explicitly supplied by the user. |
| PWA vaults / local history | Available | Available | Uses application-controlled browser storage, subject to browser limits. |
| Performance telemetry | Available | Partly available | Local measurements continue; network RTT becomes offline/unavailable. |
| Website / DNS / email-domain checks | Available | Requires connection | Controls remain visible and show the styled Internet Connection Required message. |
| Server-assisted selected-file analysis | Available when configured | Requires connection | Local analysis can still run; remote analysis waits for connectivity. |
Some security questions cannot be answered from the local browser alone. Omega Security Pro therefore uses online-assisted engines only for the checks that require remote information. These may include breach checks, remote website analysis, DNS/email authentication checks, server-assisted file analysis and other configured security services.
If an online service, remote signature scanner or compatible server capability is not actually present, the interface should report that capability as unavailable rather than claiming it has run.
On compatible browsers, Omega Security Pro can request access to files or directories selected by the user. Where that permission remains valid, the PWA can rescan the granted content while the application is open and the relevant browser capability remains available.
The private server core is separate from the public user-device tools. It protects the hosted Omega Security Pro installation and contains privileged administrative capabilities inherited from the Omega Security Engine architecture.
Rolling file-integrity snapshots, content-addressed backups for eligible files and administrator-controlled restore/mark-safe/accept-removal workflows.
Authenticated quick, full and individual-file malware/virus-oriented scan profiles over eligible site-root web-code files within the configured file-type and size limits. These private-core profiles use the bundled heuristic scanner; optional ClamAV belongs to the separate public Online Deep Scan endpoint when available.
Separate File, Malware and Virus vaults for quarantined website/server files and associated administrator actions.
IP block/allow management, HTTPS/security-header controls, sensitive-file protection, directory protection, logs and runtime/site-delivery audits.
These controls are intentionally authenticated and private. Anonymous users must never be able to restore or delete server files, alter hardening rules, or manipulate server IP controls.
Omega Security Pro is designed so users can access the public security suite without creating an account. Local tools can operate inside the browser/PWA, and online-assisted functions use only the data necessary for the specific action initiated by the user, subject to the Privacy Policy and the implementation of the relevant endpoint.
Local vaults, reports, baselines, settings and history belong to the current browser/PWA profile unless the product explicitly states otherwise. Clearing browser/PWA storage or uninstalling the app can remove locally stored application data.
The service worker provides the installable application shell and offline-capable resources. Updated cache versions are used so new application releases can replace earlier cached assets. PWA installation telemetry is maintained separately from security-analysis content and is intended to count aggregate installation signals rather than identify individual users.
Online-only engines are never converted into fake offline engines. When disconnected, Omega Security Pro keeps their controls visible and communicates that connectivity is required.
The user selects a function, enters a URL/message/password, chooses a file, grants a folder, or requests a diagnostic.
Any browser-safe checks that can run locally execute first or alongside the relevant workflow.
If deeper analysis requires the network, Omega checks connection state before calling the online engine.
The real result is returned to the appropriate colour-coded console, meter, result panel, vault or security-history record.
Omega Security Pro is designed to use the strongest security capabilities legitimately available to a website/PWA and its configured server engines. Browser security boundaries remain in force even when the user is online.
Within its permitted scope, Omega Security Pro can still provide real local analysis, real user-authorised file and folder workflows, online-assisted scanning, phishing interception inside the application, server security controls for the hosted service, and real measured runtime diagnostics.
Omega Security Pro is intentionally built as a coordinated hybrid system rather than a collection of disconnected tools. The colour coding used in the navigation, function cards, 3D controls and live meters identifies the same functional families throughout the website and installed PWA.
| Colour family | Security function | Primary scope |
|---|---|---|
| Electric Blue | Security Command / Core Protection | Browser/PWA posture and central control |
| Gold | Credentials / Integrity | Password security and trusted-file baselines |
| Purple | Phishing / URL Intelligence | Messages, links and app-level navigation defence |
| Red / Crimson | Antivirus / Malware Defence | User-selected files and explicit server-assisted analysis |
| Orange-Red | File Defence | User-selected files and browser-granted folders |
| Violet | Secure Vaults | PWA File/Malware/Virus vaults and private server vaults |
| Cyan | Website / Network / Email Security | Remote-domain and connectivity-dependent analysis |
| Green | Privacy Defence | Browser/PWA privacy and security capabilities |
| Magenta | Breach Intelligence | Privacy-preserving password breach-range lookup |
| Teal | Performance | Real runtime device/browser measurements |
