Protection from brute force / SQL injection attacks
What it means
A firewall or equivalent filters brute-force logins and injection attempts, and the code uses safe database queries.
Why it matters
Injection and brute force are among the most common web attacks, and a breach caused by missing basics is hard to defend.
Legal and technical reference: GDPR Art. 32
How to pass this check
Quick fix: Put a web application firewall (Cloudflare, Wordfence, Sucuri) in front of the site to block brute force and injection attempts.
- Put a web application firewall (Cloudflare, Sucuri, Wordfence or similar) in front of the site.
- Use prepared statements and validate every input.
- Rate-limit login and form endpoints.
How Lawscan checks it
The scanner searches for “firewall”, “WAF”, “Wordfence”, “Sucuri” or “SQL injection”.
Does your website pass this check?
Scan it now: you get the result of all 55 checks in a few seconds.
Other checks in this category
- SSL certificate active (HTTPS) −3
- Passwords stored securely (hashed) −2
- User password policy (complexity, expiration) −1
- Two-factor authentication for admin access −2
- Admin access protected (custom URL, IP restrictions) −2
- CMS/plugins regularly updated −2
- Periodic and tested backups −2
- User role/permission management −2
- Monitoring of suspicious access logs −1
← Back to the full Compliance Index
Automated, indicative information. It is not legal advice.