Help stop malicious requests before WordPress loads

A firewall and a malware scanner solve different problems

A firewall examines incoming traffic. A WordPress malware scanner looks for signs that harmful code or an infection is already present. A vulnerability scan identifies known weaknesses in installed versions. None replaces the others.

Sentinel combines these views so you can respond to an attack and address its cause. Keep vulnerable plugins updated even when a firewall is enabled. A rule set cannot promise to stop every exploit, and a server or hosting-account compromise can happen outside the requests this firewall checks.

Understand watch mode before you rely on blocking

The Sentinel firewall begins with a watch period on each website. During that period, it records activity without blocking. Review the reported mode and investigate compatibility questions before relying on active protection.

Sentinel also stays in watch mode alongside recognized firewall plugins such as Wordfence. Existing firewall protection remains responsible for refusing requests. Read the website status instead of treating the workspace switch as proof that two firewalls are blocking together.

Review attacks across all your connected websites

The firewall view summarizes recent activity and attack categories across the workspace. You can review individual websites and turn the firewall off for a site that needs an exception, subject to your permissions.

Supported versions also refuse persistent attacking addresses and participate in WPCentrify network protection. Pair this with brute force protection for password guessing and vulnerability scanning to find the components you still need to patch.