Eric Mann

Unmask

manuelgalan

<p>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.</p>
<h4>Features</h4>
<ul>
<li>Real-time security event collection and forwarding to Vulnity SIEM.</li>
<li>Dashboard widgets that highlight critical findings and remediation steps.</li>
<li>Scheduled security scans for core files, plugins, and themes.</li>
<li>Centralized logging compatible with major SOC workflows.</li>
</ul>
<h4>Integration Requirements</h4>
<p>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 <strong>Vulnity > Settings</strong>.</p>
<h4>External Services</h4>
<p>This plugin connects to Vulnity’s external API hosted on Supabase Edge Functions (domain: <code>euxnoekqasvzwfcbybkg.supabase.co</code>, base URL <code>https://euxnoekqasvzwfcbybkg.supabase.co/functions/v1</code>) to power SIEM alerts, inventory sync, and mitigation updates.</p>
<ul>
<li><strong>What the service is and what it is used for:</strong>
<ul>
<li>Vulnity SIEM API for pairing/unpairing, heartbeat checks, sending alerts, testing connectivity, syncing inventory, and receiving mitigation policies.</li>
</ul>
</li>
<li><strong>Endpoints used:</strong>
<ul>
<li><code>/pair-plugin</code>, <code>/unpair-plugin</code> (pairing and disconnecting the site).</li>
<li><code>/heartbeat</code> (periodic health check).</li>
<li><code>/connection-test</code> (manual connection test).</li>
<li><code>/scan-site-info</code> (inventory sync).</li>
<li><code>/generic-alert</code>, <code>/brute-force-alert</code>, <code>/file-security-alert</code>, <code>/manage-user</code>, <code>/user-management-alert</code>, <code>/permission-change-alert</code>, <code>/file-editor-alert</code>, <code>/plugin-change-alert</code>, <code>/theme-change-alert</code>, <code>/core-update-alert</code>, <code>/suspicious-query-alert</code>, <code>/scanner-detected-alert</code> (security alerts).</li>
<li><code>/mitigation-config</code>, <code>/mitigation-update</code> (mitigation policy sync and block/unblock updates).</li>
</ul>
</li>
<li><strong>What data is sent and when:</strong>
<ul>
<li>Pairing/unpairing: site ID, pair code, plugin/WordPress/PHP versions, and timestamp when pairing or disconnecting occurs.</li>
<li>Heartbeat: site ID, URLs, site metadata (name, language, timezone, theme), and runtime info (plugin/WordPress/PHP versions, latency) on a scheduled interval.</li>
<li>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.</li>
<li>Inventory sync: site inventory details (installed plugins/themes/core metadata) when inventory sync runs.</li>
<li>Mitigation: site ID, block/unblock actions, IP address, reason, duration, and rule metadata when mitigation rules are synced or enforcement actions occur.</li>
</ul>
</li>
<li><strong>Why the data is sent:</strong>
<ul>
<li>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.</li>
</ul>
</li>
<li><strong>Policies:</strong> See the Vulnity <a href="https://vulnity.io/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://vulnity.io/privacy" rel="nofollow ugc">Privacy Policy</a> for details on how data is handled.</li>
</ul>
<h3>License</h3>
<p>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 <code>license.txt</code> file and is also available online at https://www.gnu.org/licenses/gpl-2.0.html.</p>


Vulnity Security

Security monitoring and SIEM integration that keeps your WordPress sites safe in real time.

Unmask vs Vulnity Security