FreelanceBo Group S.r.l.s

<p>FreelanceBo Sentra Control is a comprehensive WordPress security plugin that connects your site to the Sentra central console, providing enterprise-grade protection.</p>
<h4>Features</h4>
<ul>
<li><strong>Web Application Firewall (WAF)</strong> – Block malicious requests, SQL injection, XSS, and other common attacks</li>
<li><strong>Malware Scanner</strong> – Scan WordPress core files, themes, and plugins for known malware signatures</li>
<li><strong>Vulnerability Scanner</strong> – Check installed plugins and themes against known vulnerability databases</li>
<li><strong>Brute Force Protection</strong> – Limit login attempts and block attackers automatically</li>
<li><strong>File Integrity Monitoring</strong> – Detect unauthorized changes to WordPress core files</li>
<li><strong>IP Blocklist</strong> – Manage blocked IPs manually or automatically based on threat detection</li>
<li><strong>Security Events Log</strong> – Track all security events with detailed logging</li>
<li><strong>Central Console</strong> – Manage multiple WordPress sites from a single dashboard</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Install and activate the plugin on your WordPress site</li>
<li>Connect to your Sentra central console by entering the server URL and API key in Settings</li>
<li>The plugin automatically starts monitoring your site and reporting to the console</li>
<li>View scan results, manage firewall rules, and review security events from either the WordPress admin panel or the central console</li>
</ol>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8 or higher</li>
<li>PHP 7.4 or higher</li>
<li>A Sentra central console account (available at freelancebo.it)</li>
</ul>
<h3>External Services</h3>
<p>This plugin relies on the following external services:</p>
<h4>FreelanceBo Sentra Control Console</h4>
<p>This plugin connects to a self-hosted FreelanceBo Sentra Control central console for centralized security monitoring and management. This connection is essential for the plugin to function.</p>
<p><strong>What data is sent:</strong><br />
* Site URL, WordPress version, PHP version, and installed plugins/themes list (during heartbeat and scans)<br />
* Security events (firewall blocks, failed login attempts, malware detections, file integrity changes)<br />
* Scan results (malware scan, vulnerability scan, integrity scan findings)</p>
<p><strong>When data is sent:</strong><br />
* On plugin activation and periodically via heartbeat (every 5 minutes)<br />
* When security events occur (login attempts, firewall blocks)<br />
* When scans are triggered (manually or via scheduled cron)<br />
* When the admin manages firewall rules, blocklists, or settings</p>
<p><strong>Service provider:</strong> FreelanceBo Group S.r.l.s., Bologna, Italy<br />
* Service URL: <a href="https://sentra.freelancebo.it" rel="nofollow ugc">https://sentra.freelancebo.it</a><br />
* Terms of Service: <a href="https://sentra.freelancebo.it/terms" rel="nofollow ugc">https://sentra.freelancebo.it/terms</a><br />
* Privacy Policy: <a href="https://sentra.freelancebo.it/privacy" rel="nofollow ugc">https://sentra.freelancebo.it/privacy</a></p>
<p>The console server URL is configurable by the user in the plugin settings. All data is transmitted over HTTPS. Data is stored on EU-based servers in compliance with GDPR.</p>
<h4>WordPress.org API</h4>
<p>The vulnerability scanner module uses the official WordPress.org API to retrieve information about installed plugins, themes, and WordPress core version. This is necessary to check for known vulnerabilities and outdated software.</p>
<p><strong>What data is sent:</strong><br />
* Plugin slugs, theme slugs, and WordPress core version</p>
<p><strong>When data is sent:</strong><br />
* When a vulnerability scan is triggered (manually or via scheduled cron)</p>
<p><strong>Service provider:</strong> WordPress.org<br />
* API endpoint: <a href="https://api.wordpress.org" rel="nofollow ugc">https://api.wordpress.org</a><br />
* Terms of Service: <a href="https://wordpress.org/about/privacy/" rel="ugc">https://wordpress.org/about/privacy/</a><br />
* Privacy Policy: <a href="https://wordpress.org/about/privacy/" rel="ugc">https://wordpress.org/about/privacy/</a></p>


FreelanceBo Sentra Control

Security agent connecting to FreelanceBo Sentra Control console for WAF, malware scanning, brute force protection, and vulnerability scanning.

bean1352

<p>If you sell a WordPress plugin or theme to anyone in the EU, the EU Cyber Resilience Act (Regulation 2024/2847) applies to you. It does not matter where you are based or whether your product is free. Agencies distributing custom plugins or themes to EU clients are also in scope.</p>
<p>From September 11, 2026, you need a documented vulnerability reporting process, the required security documents, and a way to monitor your products for known vulnerabilities. ResilienceWP is built for WordPress developers — plugin developers, theme developers, and agencies — to cover all of that in one place.</p>
<p>Non-compliance carries fines up to EUR 15 million or 2.5% of global annual turnover. Authorities can also force non-compliant products off the EU market.</p>
<p>The free plan covers the paperwork side of compliance: checklist, five document templates, and the CRA education guide. Paid plans add automated vulnerability scanning, email alerts, the Incident Center for ENISA notification management, and downloadable compliance reports, all directly inside your WordPress admin. Pro plans also include webhook integrations for CI/CD pipelines and external tools — get real-time notifications when scans complete or vulnerabilities are found.</p>
<p>For pricing, documentation, and more details visit <a href="https://www.resiliencewp.com" rel="nofollow ugc">resiliencewp.com</a>.</p>
<h4>Compliance Checklist (Free)</h4>
<p>26 actionable items, each mapped to a specific CRA article. Five categories cover everything the regulation requires:</p>
<ul>
<li>Risk Assessment: documenting threats, attack surfaces, and mitigations</li>
<li>Secure Development: secure defaults, no known exploitable vulnerabilities at release</li>
<li>Vulnerability Handling: disclosure policy, coordinated reporting, user notification</li>
<li>Required Documentation: SBOM, Declaration of Conformity, technical file</li>
<li>Post-Market Obligations: ongoing monitoring, security updates, end-of-life policy</li>
</ul>
<p>Every item has a plain-English explanation of what it means and why it matters. Check items off as you complete them. Progress saves automatically.</p>
<h4>Document Generator (Free)</h4>
<p>Generate the five documents the CRA requires before you can legally place a product on the EU market:</p>
<ul>
<li>Vulnerability Disclosure Policy (Article 13(6)): your public process for receiving and handling security reports from researchers</li>
<li>Incident Response Plan: your internal procedure when a vulnerability is discovered or actively exploited</li>
<li>EU Declaration of Conformity: the formal self-declaration that your product meets CRA essential requirements</li>
<li>Software Bill of Materials (SBOM) (Article 13): a structured inventory of your plugin’s components, dependencies, and third-party libraries</li>
<li>security.txt: the machine-readable contact file security researchers use to reach you, placed at /.well-known/security.txt</li>
</ul>
<p>Fill in your plugin name, contact details, and a few specifics. Download in text or markdown format. No starting from scratch, no lawyer needed for the first draft.</p>
<h4>CRA Education Centre (Free)</h4>
<p>An article-by-article breakdown of Regulation (EU) 2024/2847, written for developers rather than legal teams. Understand what each obligation actually requires: what counts as “active exploitation,” what an SBOM needs to contain, what the 24-hour reporting window really means.</p>
<h4>Vulnerability Scanner (Basic and Pro)</h4>
<p>Connect your account to ResilienceWP and it monitors your plugins against the WPScan vulnerability database on a regular schedule. Weekly on Basic, daily on Pro.</p>
<p>You can monitor any plugin by its WordPress.org slug, not just the plugins currently installed on your site. If your plugin depends on WooCommerce, ACF, or any other third-party plugin, you can add those slugs directly and track vulnerabilities in your dependencies. Plugins can also be added directly from your installed plugins list.</p>
<p>The moment a new vulnerability is found, you get an email with the severity rating, CVE ID, affected version range, and fix version if one is available. Back in your WordPress admin, vulnerabilities are grouped by plugin and sorted by date discovered, so you can see at a glance which plugins have open issues and how old they are.</p>
<p>Each vulnerability card shows:</p>
<ul>
<li>Severity (Critical / High / Medium / Low / Info) with colour coding</li>
<li>CVE identifier linked directly to the NVD entry</li>
<li>The fix version (or “no fix available yet”)</li>
<li>An action hint: whether to update, acknowledge, or open an incident</li>
<li>A button to report the incident directly to the Incident Center</li>
</ul>
<p>Status tracking lets you mark vulnerabilities as Open, Acknowledged, In Progress, Resolved, or False Positive. Export the full vulnerability list as CSV for your compliance records.</p>
<h4>Incident Center (Basic and Pro)</h4>
<p>When a vulnerability in your plugin is being actively exploited, the CRA requires you to notify ENISA within 24 hours. The Incident Center tracks that deadline from the moment you log first awareness and guides you through the complete regulatory workflow.</p>
<p>Creating a new incident logs the discovery timestamp and starts all three countdown timers simultaneously:</p>
<ol>
<li>Early Warning: due within 24 hours of first awareness</li>
<li>Vulnerability Notification: due within 72 hours, with full technical details</li>
<li>Final Report: due within 14 days, including root cause and remediation steps</li>
</ol>
<p>The case view shows:</p>
<ul>
<li>Live countdown timers for each notification deadline, turning amber at 6 hours and red when overdue</li>
<li>A completeness score on your incident report so you know exactly what information is still missing</li>
<li>A “Where to Submit” section with direct links to ENISA’s reporting portal, the EU CSIRT network directory, and the CVE Programme at MITRE</li>
<li>A full audit log recording every action taken, every field updated, and every notification submitted</li>
</ul>
<p>On Pro, you can export the full incident case including all notifications and the complete audit log, formatted for submission to regulators or for your compliance archive.</p>
<h4>Dashboard and Compliance Score</h4>
<p>The dashboard gives you a live compliance score (0-100) with a transparent breakdown:</p>
<ul>
<li>-15 points per open critical vulnerability</li>
<li>-7 points per open high vulnerability</li>
<li>-3 points per open medium vulnerability</li>
<li>-20 points per overdue incident (past the 24-hour ENISA deadline)</li>
<li>-5 points per active open incident</li>
</ul>
<p>It is not a vanity metric. It is a working indicator of where you stand against your CRA obligations at any point in time, with the exact deductions shown so you know what to fix first.</p>
<h4>Compliance Reports and SBOM Export (Basic and Pro)</h4>
<p>Generate a PDF compliance report for auditors or regulators covering your vulnerability history, resolution timeline, and document status. Export your Software Bill of Materials in standard format, as required by CRA Article 13.</p>
<h4>Webhook Integrations (Pro)</h4>
<p>Connect ResilienceWP to your CI/CD pipeline, Slack, or any external tool with webhook callbacks. Configure webhook endpoints in Settings and receive real-time HTTP POST notifications with HMAC-SHA256 signed payloads when:</p>
<ul>
<li>A scheduled or manual scan completes</li>
<li>A new vulnerability is found in one of your monitored plugins</li>
</ul>
<p>Each webhook delivery is logged with status codes and response data, so you can debug integration issues directly from your WordPress admin. Manage up to 5 webhook endpoints per account, toggle them on and off, and filter by event type.</p>
<h4>Who needs to comply</h4>
<ul>
<li>Commercial plugin developers: selling to EU customers through any channel (your site, Envato, direct) makes you the manufacturer under the CRA</li>
<li>WordPress agencies: distributing custom-built plugins to EU clients, even for a single client, counts as placing a product on the market</li>
<li>Freemium developers: having a free version does not exempt you; any commercial activity tied to the product brings you in scope</li>
<li>Theme developers: themes with shortcodes, API integrations, or custom post types may qualify as “products with digital elements”</li>
</ul>
<h4>Key dates</h4>
<ul>
<li>10 December 2024: CRA entered into force. Transition period began.</li>
<li>11 September 2026: Vulnerability and incident reporting obligations apply.</li>
<li>11 December 2027: Full CRA application. All requirements in effect.</li>
</ul>
<h4>Source Code</h4>
<p>The admin dashboard is built with React and compiled using Vite. The uncompiled source is included in the plugin ZIP under admin/src/. To rebuild from source:</p>
<ol>
<li>Install Node.js 20+ and pnpm 10+</li>
<li>Run <code>pnpm install</code> in the plugin directory</li>
<li>Run <code>pnpm build</code> to recompile the admin dashboard</li>
</ol>
<h4>External Services</h4>
<p><strong>ResilienceWP API</strong> (https://api.resiliencewp.com)<br />
Used for API key verification, vulnerability scanning, incident management, and report generation. Data sent: API key, WordPress site URL, plugin slugs and versions.<br />
<a href="https://www.resiliencewp.com/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.resiliencewp.com/privacy" rel="nofollow ugc">Privacy Policy</a></p>
<p><strong>WPScan</strong> (via ResilienceWP API)<br />
Plugin vulnerability data is sourced from the WPScan database. Plugin slugs are sent through the ResilienceWP API. No personal data is sent from your WordPress installation directly to WPScan.<br />
<a href="https://wpscan.com/terms" rel="nofollow ugc">WPScan Terms</a> | <a href="https://wpscan.com/privacy" rel="nofollow ugc">WPScan Privacy Policy</a></p>
<p><strong>Paddle</strong> (payments)<br />
Subscription payments are processed by Paddle as merchant of record. Payment data is handled entirely by Paddle and never passes through our servers.<br />
<a href="https://www.paddle.com/legal/terms" rel="nofollow ugc">Paddle Terms</a> | <a href="https://www.paddle.com/legal/privacy" rel="nofollow ugc">Paddle Privacy</a></p>


Resilience Compliance Manager

CRA compliance for WordPress developers. Checklist, document generator, vulnerability scanner, and incident reporting for the 2026 EU deadline.

FreelanceBo Sentra Control vs Resilience Compliance Manager