BPS Pro 11.3:
BugFix 10-15-2015: Security Log: Fixed duplicate visual content displayed.
BPS Pro 11.2:Core Enhancement|Improvement: Quarantine Directory Structure MirrorQuarantine prior to BPS Pro 11.2 moved or copied all quarantined files to the protected base Quarantine folder and renamed duplicate filenames in Quarantine. Quarantine as of BPS Pro 11.2 creates a mirrored directory structure of the quarantine file source path in the protected Quarantine folder. Example: If a file is quarantined from this source path/origin folder: /wp-content/example-folder/hacker-file.php then the exact mirrored directory structure will be created in Quarantine: /quarantine/wp-content/example-folder/hacker-file.php. |
New Feature: UAEG Custom CodeCustom Code now includes a 3rd accordion tab: UAEG htaccess File Custom Code. Allows you to copy your entire Uploads Anti-Exploit Guard (UAEG) htaccess file from the htaccess File Editor tab page to customize it. You can add additional whitelist rules or other custom htaccess code to your UAEG htaccess code/file and save your customizations permanently. UAEG Custom Code has also been included/added in the Custom Code Export|Import tools. When you Export or Import Custom Code, the root, wp-admin and UAEG Custom Code is exported or imported. |
New Bonus Custom Code Dismiss Notice: POST Request Attack ProtectionLong|Extensive Help Info: POST Request Attack Protection Forum Topic |
New Option: Security Log Limit POST Request Body DataThe default Security Log Request Body Data capture/log limit is 250000 maximum characters, which is roughly about 250KB in size. The new Limit POST Request Body Data checkbox option limits the maximum number of Request Body Data characters captured/logged in the Request Body logging field to 500 characters, which is roughly 5KB in size. You can capture/log entire hacking scripts if you do not check the Limit POST Request Body Data checkbox (See Note below), but that means your log file size could increase dramatically and you could receive more automated Security Log zip file emails. Note: To capture/log all POST Request Attacks against your website you will need to add the POST Request Attack Protection Bonus Custom Code: POST Request Attack Protection Bonus Custom Code |
Enhancement: Security Log 403 Logging TemplateThe Security Log 403 Logging template has a new logging field: REQUEST BODY that captures/logs POST Request Body data/content if the POST Request Body is not empty. To maximize POST Request security protection for your website and capture/log entire hacker scripts use the new POST Request Attack Protection Bonus Custom Code: POST Request Attack Protection Bonus Custom Code |
BugFixes|Code Corrections|Enhancements|Misc|CSS|Visual|Other:• Security Enhancement: Security Log content is now filtered to display only ASCII printable characters. |