Forwarding is automatic for connected sites. If you had deliberately left the old\n"Enable forwarding" checkbox off while staying connected, press Disconnect\ninstead \u2014 that checkbox no longer exists.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[5590,1110,1184,5603,600],"plugin_category":[54],"plugin_contributors":[263741],"plugin_business_model":[],"class_list":["post-352362","plugin","type-plugin","status-publish","hentry","plugin_tags-agency","plugin_tags-alerts","plugin_tags-malware","plugin_tags-monitoring","plugin_tags-security","plugin_category-security-and-spam-protection","plugin_contributors-cmdgw","plugin_committers-cmdgw"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/wpsecureops-connector.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
If you look after more than a handful of WordPress sites, Wordfence findings\narrive as one email per site per scan, in as many inboxes as you have sites.\nThis connector sends each completed scan to a single WPSecureOps dashboard\ninstead, where findings from every site queue up in one place, keep their\nhistory, and can be acknowledged or ignored once rather than again on every\nre-scan.<\/p>\n\n
The plugin does not scan anything itself and does not change how Wordfence\nbehaves. It reads the results of scans Wordfence has already finished.<\/p>\n\n
Setup is one click.<\/strong> Activate the plugin, open Settings → WPSecureOps,\npress Connect now<\/strong>. The site registers itself, an operator approves it in the\ndashboard, and it collects its own key. There is nothing to copy or paste and no\nswitch to remember to turn on: once a site is connected, every completed scan is\nforwarded automatically. Pressing Disconnect<\/strong> is how you stop it.<\/p>\n\n Usernames, passwords, API credentials, file contents, database contents, visitor\ndata and the raw Wordfence issue structure never leave the site. Absolute server\npaths are rewritten to Reports go into a queue in your own database and are delivered by WP-Cron with\nexponential backoff, so a dashboard outage or a network blip cannot lose a scan.\nEvery report carries a deterministic id derived from the installation and the\nscan, so a retry can never create a duplicate entry in the dashboard. A report\nthat can never be delivered is dropped at the end of the retry ladder rather\nthan growing the queue forever.<\/p>\n\n This plugin connects to the WPSecureOps API at It sends data at these points, and no others:<\/p>\n\n Nothing is sent once you press Disconnect, and nothing is sent by a site that has\nnever been connected.<\/p>\n\n Privacy policy: https:\/\/wpsecureops.com\/privacy<\/p>\n\n Self-hosters can point the connector at their own install with the\n wpso_connector_endpoint filter or the advanced field on the settings screen.<\/p>\n\n Created by Guido Schad<\/a>, author of\nLockora Security Audit<\/a>\nand Who Changed It? \u2013 Activity Log & Audit Trail<\/a>.<\/p>\n\n\n WP-Cron must be able to run. On a low-traffic site, have your host call\n wp-cron.php on a schedule.<\/p>\n\n\n Yes. This plugin reports what Wordfence finds; on its own it has nothing to\nreport.<\/p><\/dd>\n No. It reads Wordfence's completed-scan timestamp and issue list after a scan\nhas finished, never while one is running.<\/p><\/dd>\n Press Disconnect<\/strong> on the settings screen, or deactivate the plugin. Both stop\ndelivery immediately; Disconnect also discards this site's key.<\/p><\/dd>\n The report waits in a queue in your database and retries with exponential\nbackoff. Nothing is lost and nothing is duplicated.<\/p><\/dd>\n No. The API binds a key to the first WordPress installation that uses it, and\nrefuses it everywhere else.<\/p><\/dd>\n It runs per site, and each site connects separately. It is not network-activated.<\/p><\/dd>\n Findings are stored in the WPSecureOps dashboard your site is connected to. The\nplugin itself stores only its queue table, its own options, and its key \u2014 all of\nwhich are removed when you uninstall it.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat is sent<\/h4>\n\n
\n
What is not sent<\/h4>\n\n
[site-root]\/<\/code> before a report is queued, so a finding\ncannot leak your directory layout.<\/p>\n\nReliability<\/h4>\n\n
External services<\/h3>\n\n
https:\/\/wpsecureops.com<\/code> \u2014 the\nservice the plugin exists to talk to, and the only external service it contacts.<\/p>\n\n\n
Credits<\/h3>\n\n
\n
\n
Do I need Wordfence?<\/h3><\/dt>\n
Does it modify or slow down Wordfence?<\/h3><\/dt>\n
How do I stop it sending?<\/h3><\/dt>\n
What happens if the dashboard is offline?<\/h3><\/dt>\n
Can one API key be used on several sites?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
Where is my data stored?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n
0.7.0<\/h4>\n\n
\n
0.6.0<\/h4>\n\n
\n
0.5.0<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n