=== Vulnity Security === Contributors: manuelgalan Requires at least: 5.8 Tested up to: 6.9 Requires PHP: 7.4 Stable tag: 1.0.5 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Tags: security, siem, monitoring, intrusion-detection Security monitoring and SIEM integration that keeps your WordPress sites safe in real time. == Description == Vulnity Security brings enterprise-grade threat detection to WordPress. It connects your site to Vulnity's SIEM platform, correlates events, and alerts you before issues become incidents. = Features = * Real-time security event collection and forwarding to Vulnity SIEM. * Dashboard widgets that highlight critical findings and remediation steps. * Scheduled security scans for core files, plugins, and themes. * Centralized logging compatible with major SOC workflows. = Integration Requirements = To receive alerts, configure an API token and endpoint URL provided by your Vulnity SIEM account. Detailed configuration instructions are displayed after activating the plugin under **Vulnity \> Settings**. = External Services = This plugin connects to Vulnity's external API hosted on Supabase Edge Functions (domain: `euxnoekqasvzwfcbybkg.supabase.co`, base URL `https://euxnoekqasvzwfcbybkg.supabase.co/functions/v1`) to power SIEM alerts, inventory sync, and mitigation updates. * **What the service is and what it is used for:** * Vulnity SIEM API for pairing/unpairing, heartbeat checks, sending alerts, testing connectivity, syncing inventory, and receiving mitigation policies. * **Endpoints used:** * `/pair-plugin`, `/unpair-plugin` (pairing and disconnecting the site). * `/heartbeat` (periodic health check). * `/connection-test` (manual connection test). * `/scan-site-info` (inventory sync). * `/generic-alert`, `/brute-force-alert`, `/file-security-alert`, `/manage-user`, `/user-management-alert`, `/permission-change-alert`, `/file-editor-alert`, `/plugin-change-alert`, `/theme-change-alert`, `/core-update-alert`, `/suspicious-query-alert`, `/scanner-detected-alert` (security alerts). * `/mitigation-config`, `/mitigation-update` (mitigation policy sync and block/unblock updates). * **What data is sent and when:** * Pairing/unpairing: site ID, pair code, plugin/WordPress/PHP versions, and timestamp when pairing or disconnecting occurs. * Heartbeat: site ID, URLs, site metadata (name, language, timezone, theme), and runtime info (plugin/WordPress/PHP versions, latency) on a scheduled interval. * Alerts: site ID, alert type/severity, timestamps, and event details (such as IP address, user/action metadata, or file change context) whenever a security event is detected. * Inventory sync: site inventory details (installed plugins/themes/core metadata) when inventory sync runs. * Mitigation: site ID, block/unblock actions, IP address, reason, duration, and rule metadata when mitigation rules are synced or enforcement actions occur. * **Why the data is sent:** * To associate the site with your Vulnity account, deliver security alerts to the SIEM, validate connectivity, synchronize inventory and mitigation policies, and keep firewall enforcement consistent. * **Policies:** See the Vulnity [Terms of Service](https://vulnity.io/terms) and [Privacy Policy](https://vulnity.io/privacy) for details on how data is handled. == Installation == 1. Upload the plugin files to the `/wp-content/plugins/vulnity` directory or install from the WordPress plugin repository. 2. Activate the plugin through the **Plugins** screen in WordPress. 3. Navigate to **Vulnity \> Settings**, enter your Vulnity SIEM credentials, and save. 4. (Optional) Enable scheduled scans on the **Monitoring** tab to receive weekly reports. == screenshot == 1. Dashboard 2. Alerts 3. Mitigation 4. Hardening == Frequently Asked Questions == = Do I need a Vulnity SIEM subscription? = Yes. The plugin requires an active Vulnity SIEM account to collect and analyze events. = Will the plugin slow down my site? = No. Event collection runs asynchronously and offloads processing to the Vulnity cloud platform. = Can I disable certain alerts? = Absolutely. Use the **Alert Policies** section within the plugin settings to mute or reclassify events. == Screenshots == 1. Dashboard overview with real-time threat summary. 2. Alert detail screen showing remediation steps. 3. Settings page for configuring API credentials and scan schedules. == Changelog == = 1.0.5 = * Version bump to 1.0.5. = 1.0.4 = * Version bump to 1.0.4. = 1.0.3 = * Standardized admin asset enqueues and AJAX URL localization for compliant loading. * Hardened nonce and capability checks across alerts and admin handlers. * Improved path resolution using WordPress APIs for non-default installs. * Documented external Supabase services used for alerts and mitigation updates. = 1.0.2 = * Initial release. == Upgrade Notice == = 1.0.5 = Version bump to 1.0.5. = 1.0.4 = Version bump to 1.0.4. = 1.0.3 = Compliance-focused update to align asset loading, documentation, and escaping with WordPress.org guidelines. = 1.0.2 = Initial public release featuring Vulnity SIEM integration and security monitoring dashboard. == License == This plugin is licensed under the GNU General Public License v2.0 or later. You are free to redistribute and/or modify it under the terms of the GPL as published by the Free Software Foundation. The complete license text is included in the bundled `license.txt` file and is also available online at https://www.gnu.org/licenses/gpl-2.0.html.