Omega Security Engine Pro documentation

1. Extract at public_html and open /omega-security-engine/.
2. Create the dedicated Omega administrator.
3. Review Hardening and apply/refresh protection rules appropriate to the server.
4. Run File Integrity once to establish the trusted baseline.
5. Run Quick scans first, then Full or single-file scans as needed.
6. Review every finding before quarantine.
7. Use File/Malware/Virus Vault controls for restore, mark-safe or deletion decisions.
8. Manage IP allow/block lists where required.
9. Review security logs and the runtime, URL, message/browser and DNS audits.

Requirements

• PHP 8.1+ recommended.
• Write access to protected engine data, logs, vault and backup areas.
• Apache/LiteSpeed for included .htaccess request/header protections.
• Nginx requires equivalent server configuration for request blocking/header rules.

• Scanner findings are indicators requiring administrator review.
• No automatic scanner deletion/overwrite.
• Quarantine is explicit.
• Vaulted files are stored non-executably with SHA-256 evidence.
• Root .htaccess changes are managed and backed up.
• Dedicated authentication, CSRF validation and throttling protect dashboard actions.

Technical boundaries

No security scanner can guarantee detection of every threat or prove a finding is malicious without review. Nginx ignores .htaccess; equivalent hardening rules require server configuration. Email DNS audits depend on publicly resolvable DNS records and correct domain/selector configuration.