33 documented capabilities
The Features reference below maps every meaningful customer-facing capability identified in the audited 2.0.0 product codebase.
OMEGA SECURITY ENGINE PRO DOCUMENTATION · WordPress Plugin 2.0.0
Omega Security Engine Pro documentation
Complete Omega Security Engine Pro WordPress Plugin 2.0.0 documentation covering all audited customer-facing capabilities, installation, setup, safety, troubleshooting and support.
PRODUCT OVERVIEW
What Omega Security Engine Pro does
A WordPress security plugin with application firewall, brute-force/login protection, IP controls, integrity monitoring, PHP malware scanning and optional hardening. Persistent security state is stored in protected wp-content storage rather than inside the plugin package.
Local-first operation
The core functions described on this page are designed to operate locally on the customer website/server rather than requiring an OmegaWebApps cloud processing subscription. This reduces dependency on remote processing services and keeps operational state under the website owner’s control, subject to the hosting/platform environment.
Platform-specific architecture
WordPress-native hooks, capabilities, nonces, media/admin APIs and bounded administrator workflows.
Documentation map
Use the section that matches the job you are performing.
Features
Complete audited capability reference with descriptions.
Open FeaturesInstallation
Requirements, preflight checks and installation procedure.
Open InstallationSetup
Recommended configuration order and safe production workflow.
Open SetupFAQ
Commercial and product-specific technical answers.
Open FAQTroubleshooting
Common failure modes and corrective actions based on the engine boundaries.
Open TroubleshootingSupport
What to check, what information to collect and where to get help.
Open SupportCore operating workflow
- Back up the WordPress site/database and install/activate the plugin.
- Open Omega Security and review settings before enabling high-impact hardening.
- Configure IP handling, login protection and optional firewall/hardening controls.
- Run a manual File Integrity scan/baseline.
- Run the malware scan and review indicators.
- Enable HSTS, CSP, REST restriction, HTTPS redirect or proxy headers only when the site environment has been tested for them.
- Review security logs and scheduled maintenance behavior.
Requirements
- WordPress 6.0+.
- PHP 7.4+.
- Write access to wp-content/omega-security-engine-data.
- Apache-compatible .htaccess behavior for managed file-based hardening rules where used.
Safety architecture
- HSTS and CSP are off by default.
- REST restriction is off by default.
- Proxy IP headers are ignored unless explicitly trusted.
- Malware findings do not trigger automatic deletion/healing.
- DISALLOW_FILE_MODS, FORCE_SSL_ADMIN and WP_DEBUG are not forced.
- Asset version query strings are preserved.
- Admin actions require capabilities and nonces.
Technical boundaries
No WordPress security plugin can guarantee prevention/detection of every attack. Server/WAF/CDN/hosting security remains part of the overall security model. CSP/HSTS/REST/proxy settings are environment-sensitive and must be tested before production use.
Product page and commercial specification
Review the complete public-facing capability specification, pricing and licence information for Omega Security Engine Pro.