DROVNE Rocca Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
DROVNE Rocca protects a WordPress site with a few focused tools. Each one has its own switch, and the plugin never contacts an outside server.
Login protection
- Locks out an IP address after too many failed logins, counted on the login form, XML-RPC and application passwords.
- Lockouts grow: after repeated lockouts within a day, the next one lasts hours instead of minutes.
- An allowlist of addresses and ranges, IPv4 and IPv6, that are never locked out, with a button to add your own address.
- A list of the addresses locked out now, with an Unlock button.
- The same error for a wrong username and a wrong password, so the form does not reveal which accounts exist.
Two-factor authentication
- A code from an authenticator app at every login, such as Google Authenticator, Microsoft Authenticator, Aegis or 2FAS. Codes follow the TOTP standard (RFC 6238).
- Each user sets it up under Users > Two-factor by scanning a QR code. The QR code is drawn by the plugin itself, so the key never reaches an outside service.
- Ten single-use backup codes for a lost phone. Only their hashes are stored, and the app key is stored encrypted.
- Require it for chosen roles: those users set up their app at their next login, before they get in.
- The password alone never starts a session: the code is asked for before any login cookie is sent. Wrong codes count toward the login lockout.
- Programs that log in through XML-RPC use an application password, as core provides.
- Administrators can turn it off for a user who lost both the phone and the backup codes.
Firewall
- Checks every request before other plugins load, from a small must-use plugin that Rocca writes when you turn the firewall on and removes when you turn it off.
- Rules, each with its own switch: SQL injection, script injection, path traversal and file inclusion in the address; probes for .env, .git, configuration backups and database dumps; known vulnerability scanners; request methods WordPress does not use.
- Only the address, method, address bar and user agent are checked. Form data is not, so posts and comments about code are never blocked.
- Block mode, or log-only mode to try the rules on your site first.
- Blocked addresses and ranges, and an optional limit of requests per minute per address.
- A log of the latest matches. A blocked visitor sees a short reference that you can find in the log.
- An emergency switch in wp-config.php if a rule ever locks you out.
- The rules are written into the plugin and change only with plugin updates: no outside rule feed.
Activity log
- Records who did what and from which address: logins and logouts, lockouts, password resets, two-factor and application password changes.
- Users created, deleted, given another role, or with a new email address or password. Passwords are never stored.
- Plugins and themes installed, updated, activated, deactivated, switched or deleted, and WordPress updates.
- Changes to important settings, such as the site address, the admin email, registration and the default role, with the value before and after, and every change to Rocca’s own settings.
- Filter by kind of action and by user, page through older entries and download a CSV file.
- Written with one database query at the end of a request, and deleted after 90 days by default.
File checks
- Every day, a background check fingerprints the code files of WordPress, plugins, themes, must-use plugins and uploads: PHP, JavaScript, .htaccess and .user.ini.
- The first check becomes the baseline. Later checks list changed, new and missing files, and you accept the ones you recognize.
- PHP in the uploads folder is always listed until you accept it, even on the first check: uploads should hold no code.
- Updates made from the dashboard refresh the baseline of what they replaced, so a normal update raises no alarm.
- An email to the site administrator when a check finds something new.
- No outside data: the baseline is your own site, taken at a time you trust. Rocca never changes or deletes a file.
Hardening
- Turns off the plugin and theme file editors.
- XML-RPC: allowed, without logins and pingbacks, or off entirely.
- Hides usernames from visitors: author numbers, the REST user list, oEmbed and the users sitemap.
- Removes the WordPress version from the page head and feeds.
- Sends X-Content-Type-Options, X-Frame-Options and Referrer-Policy on public pages, unless they are already set.
Behind a proxy
By default Rocca uses the address of the direct connection. If your site sits behind Cloudflare or another proxy, choose the header it sets on the Settings page, which shows the value of each header for your own request.
Privacy
Rocca stores what it needs in your own database, and each kind of record is deleted after a period you choose:
- A failed login: the IP address, the name typed and the time. 30 days by default.
- A request stopped or logged by the firewall: the IP address, method, address requested, user agent and time. 30 days by default.
- The activity log: the username, IP address and time of each action. 90 days by default. An erasure request removes the person’s username and address from their entries and keeps the events.
- Two-factor: an encrypted app key and hashes of the backup codes, stored with the user’s account until two-factor is turned off.
Rocca adds a suggested paragraph to the privacy policy guide and supports the WordPress personal data export and erase tools.
DROVNE Rocca is an independent plugin. It is not affiliated with or endorsed by WordPress or Automattic.
Screenshots
The overview: what each module does now, and the figures of the last 24 hours.
Login protection: the attempt limit, the allowlist and the addresses locked out now.
Two-factor setup: scan the QR code, drawn by the plugin itself, or type the key.
The firewall: rules, log-only mode and the latest matches with their reference.
The activity log, filtered by kind of action, with the values before and after.
File checks: code in uploads and changed files, to accept or look at.

