Proactive Security Suite

Changelog

1.2

Added new functionalities to work with cloudflare including a table and an extra tab

1.2.1

New options on the blocked ips table

1.3

The user now can remove a blocked ip either from the local list or from both the Cloudflare and the plugin blocked list.

1.3.1

Freemius Integration

1.3.2

Minor fixes

1.3.3

AbuseIP Database Integration

1.3.4

Timezone fix

1.3.5

Timezone fix

1.3.6

Added ips blocked from WordFence wfBlockedIPLog too

1.3.7

Various fixes
Added Pro feature – Traffic inspection integration with whatsmybrowser.com API to identify malicious user agents.

1.3.8

Various fixes

1.3.9

Various fixes

1.4.0

Various fixes

1.5.0

Enhanced WhatIsMyBrowser API Integration:
– Dynamic handling of is_abusive values directly from the API without predefined mappings.
– Extracted and stored specific API response elements: is_abusive, software, operating_system.
– Optimized API usage by making calls only once per unique IP/User Agent combination.
– Improved error handling and logging for API requests.

Admin Interface Enhancements:
– Professional redesign of the “Captured Traffic” table with WordPress admin styling.
– Fixed layout issues with action buttons and ensured proper alignment.
– Integrated DataTables for advanced table features like search, pagination, and sorting.
– Focused data display by showing only relevant API response fields.

Database and Performance Optimizations:
– Updated database schema to include new columns for software and operating_system.
– Changed is_abusive column type to accommodate dynamic values.
– Enhanced data sanitization and security measures.

Code Refactoring and Security Enhancements:
– Improved code structure for better readability and maintenance.
– Ensured adherence to security best practices throughout the codebase.

Bug Fixes and Minor Improvements:
– Resolved button overflow issues in the admin table.
– Enhanced user experience with better messaging and error handling.

1.5.1

Bulk Selection and Deletion in Blocked IPs Tab:

Added a “Select All” checkbox in the Blocked IPs table header, allowing you to select all records across all pages, regardless of how many are displayed per page.
Implemented the ability to perform bulk actions, such as deleting multiple blocked IPs at once, enhancing efficiency in managing large numbers of records.
Improved the positioning and styling of the “Select All” checkbox to prevent overlap with sorting arrows, ensuring better usability.
Enhanced Actions in Captured Traffic Tab:

Introduced a new “Delete All Records” button within the “Actions” column of the Captured Traffic table. This feature enables you to delete all records associated with a specific IP address with a single click.
Adjusted the layout and styling of action buttons to prevent them from overflowing outside of their table columns. Buttons are now stacked vertically and styled consistently for a cleaner and more organized look.
User Interface Improvements:

Modified CSS and table configurations to ensure that all buttons and content fit neatly within their respective columns, enhancing the overall aesthetics and usability of the plugin interface.
Disabled sorting on checkbox columns and adjusted column widths to optimize the display of data and controls within the tables.

1.5.2

New Features:

Exclude User Roles from Captured Traffic Data (Premium Feature)

Description: Administrators can now select one or more WordPress user roles to exclude from traffic logging in the Captured Traffic Data. This feature enhances privacy and control by preventing the logging of traffic data for trusted users or specific roles, such as administrators or editors.
How to Use: Navigate to the plugin’s settings page under the “Exclude Roles from Captured Traffic” section (available for premium users). Select the roles you wish to exclude from logging and save the settings.
Improvements:

AbuseIPDB Data Display Enhancement

Resolved an issue where AbuseIPDB data (Country Code, Usage Type, ISP, Confidence Score) was not displayed on every row for IP addresses appearing multiple times in the Captured Traffic table.
Now, when AbuseIPDB data is fetched for an IP address, all existing entries with that IP in the Captured Traffic table are updated to reflect the latest data.
Code Compliance and Optimization

Ensured all new code follows WordPress coding standards and best practices.
Implemented proper sanitization, validation, and use of WordPress APIs for enhanced security and performance.
Important Notes:

Premium Access Required: The new feature to exclude user roles from traffic logging is available only in the premium version of the plugin. Free users will see a notice indicating that the feature is available upon upgrading.

Action Required: After upgrading to version 1.5.2, premium users should review the new settings:

Go to the plugin settings page.
Under the “Exclude Roles from Captured Traffic” section, select the user roles you wish to exclude.
Save the settings to apply the changes.
No Impact on Existing Settings: Existing configurations and data are not affected by this update. However, reviewing the new settings is recommended to take full advantage of the new features.

Compatibility: This update is fully compatible with WordPress versions up to the latest release as of [Current Date].

Upgrade Instructions:

Backup Your Site: It’s always good practice to back up your WordPress site before performing any updates.

Update the Plugin:

Navigate to your WordPress dashboard.
Go to Plugins > Installed Plugins.
Find “Wordfence to Cloudflare” in the list.
Click on “Update Now” to upgrade to version 1.5.2.
Review New Settings (Premium Users):

After the update, go to Settings > WTC Settings.
Navigate to the “Exclude Roles from Captured Traffic” section.
Select the roles to exclude and save your settings.

1.5.3

Added
Advanced Rule Builder and Evaluation System: Introduced a powerful rule evaluation engine that allows you to create custom security rules based on various criteria such as confidence score, whitelisted status, abusive status, and more. This enables automated decision-making and actions based on incoming traffic data.

Rule Priorities: Implemented a priority system for rules, allowing you to control the order in which rules are evaluated. Higher priority numbers are evaluated first, ensuring critical rules are applied before others.

Automatic Action Application: The plugin now automatically applies actions (e.g., block, challenge) to IP addresses that match your defined rules immediately after capturing traffic data.

Rule Details in Blocked IPs Table: Enhanced the Blocked IPs tab by adding a new column that displays detailed information about the rules that caused each IP address to be blocked, including criteria and actions taken.

Fixed
Database Schema Updates: Resolved issues with missing database columns (block_mode, rule_id, rule_details) by enhancing the table creation and update process. The plugin now correctly updates existing tables to include new columns without errors.

DataTables Initialization Issue: Fixed an issue where the DataTables plugin was being initialized multiple times, causing reinitialization errors. The plugin now ensures that DataTables are initialized correctly without conflicts.

Rule Evaluation Bug: Addressed a bug where rules were not being evaluated after capturing traffic data. The plugin now properly calls the rule evaluation function, ensuring that your rules are applied as expected.

1.5.4

Plugin re-branded to Proactive Security Suite!

1.5.5

This version introduces comprehensive integration with the IPData API, empowering you to incorporate detailed threat intelligence fields into your automatic mitigation rules. You can now combine conditions from IPData’s threat data alongside existing criteria from AbuseIPDB and WhatIsMyBrowser, all within a single, unified rule builder. This update ensures even finer-grained control and more robust security actions, helping you stop malicious traffic faster and more precisely than ever before. If you’ve previously set up rules or API keys, double-check your settings and take advantage of these new fields and conditions to enhance your protection.

1.5.6

New Feature: Added support for operating_system and software fields in the Rule Builder. Users can now create rules based on the operating system and browser software detected by WhatIsMyBrowser API.
Enhancement: Introduced flexible string matching operators (equals, not_equals, contains, not_contains) for operating_system and software fields to allow for more granular rule configurations.
UI Update: Updated the Rule Builder UI to display new dropdown menus and input fields for operating_system and software criteria.
Improvement: Ensured that unknown or unexpected values from the WhatIsMyBrowser API can still be handled using string-based matching.
Maintenance: Minor code refactoring and improved sanitization for input fields in the settings and rule builder sections.
Compatibility: Confirmed compatibility with the latest WordPress and tested against various common browser user agents.

1.5.7

Introducing Traffic Insights, our newest premium feature that provides a single-page overview of unique IP addresses in your captured traffic. Analyze threat intelligence fields from IPData (Tor, Proxy, Known Attacker/Abuser, etc.) alongside the latest OS, browser software, and user agent details from WhatIsMyBrowser. Gain valuable statistics like total unique IPs, top countries, average confidence scores, and more—all from one intuitive dashboard. Upgrade to unlock this powerful tool and enhance your site’s proactive security strategy today!

1.5.8

Code refactoring.

1.5.9

Minor fixes.

1.5.9.6

New feature: Added an export to CSV functionality on the Blocked IPs and Traffic Insights pages.

1.5.9.7

Fix: Fix an issue where a missing file caused fatal error

1.5.9.8

New: Added option to create and manage a Cloudflare custom IP list with an associated WAF rule. Users can view, add, or remove IPs from the list directly in the plugin, and are notified when Cloudflare returns errors such as list capacity being reached.

1.5.9.9

Fix: Automatically verify Cloudflare list credentials before performing list operations and retrieve existing list IDs if the list already exists to prevent credential errors.