Jetpack Protect and WordPress Multisite

If Jetpack is installed on the blogs in your network, Protect was automatically activated when you updated Jetpack, so your users shouldn’t have to do anything.

However, We’re thinking about adding a global security tab to WordPress.com to allow you to change whitelist settings on all your connected Jetpack sites at once:
https://github.com/Automattic/jetpack/issues/1842

Would that help?

what happens in case a blog is not connected to Jetpack (maybe because the user doesn’t care about it)? Would the Protection feature be active anyhow like with BruteProtect?

Protect wouldn’t be active, no. But you can connect any unconnected sites from your Multisite Network admin, under the Jetpack menu. That should help you take care of any outliers.

The most interesting feature would be transfer totally the Protection feature settings into the Jetpack Network menu (from <website URL>/wp-admin/network/admin.php?page=jetpack-settings), exactly like BruteProtect works now.

That seems like it could be useful indeed. I took note of your suggestion here, and we’ll consider it:
https://github.com/Automattic/jetpack/issues/1861

does the Protect feature provide a control against XMLRPC bruteforce attacks, insted of just the login-page attacks?

It’s just used on the login page so far, but extending the module to protect more areas of your site is on our radar!