Ensuring Website Compliance with 152-FZ Requirements

Federal Law No. 152-FZ "On Personal Data" is not just a bureaucratic document. For a website owner collecting visitor contacts, it imposes concrete technical requirements: application architecture, encryption, access control, and data localization. Often websites collect IP addresses and cookies, but the privacy policy hasn't been updated, and consent is just a pre-checked checkbox. On the first inspection, Roskomnadzor can fine up to 300,000 rubles, and for a repeat violation — up to 500,000 rubles. Our certified engineers help you pass an audit and implement all measures without downtime. We have been working for over 10 years, completed more than 50 projects on 152-FZ, and guarantee passing inspections. We cut audit time by 2-3 times compared to self-service. Submit a request — we'll conduct an express analysis of your site in 2 days.

What technical measures are mandatory?

Our standard solutions speed up implementation by 3-5 times compared to in-house development.

Depending on the security level (UZ-4 or UZ-3), requirements differ. For a site with user registration, UZ-4 suffices. If you process special categories (health, religion), UZ-3 is required. Compare the two approaches.

Encryption in transit

HTTPS is mandatory on all pages where personal data is collected. TLS 1.2 minimum, TLS 1.3 recommended.

ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:...;
ssl_prefer_server_ciphers off;

Access control

Access to personal data only for employees who need it.

class PersonalDataController extends Controller
{
    public function show(User $user)
    {
        $this->authorize('view-personal-data');
        return response()->json($user->getPersonalData());
    }
}

class PersonalDataPolicy
{
    public function view(User $authUser, User $targetUser): bool
    {
        return $authUser->hasPermissionTo('view-personal-data')
            && $authUser->department === 'support';
    }
}

Consent to processing

Consent must be explicit, informed, and specific. A pre-checked checkbox is not allowed. You must store a record with IP, user-agent, document version, and timestamp.

ConsentRecord::create([
    'user_id'        => $user->id,
    'type'           => 'personal_data_processing',
    'ip_address'     => $request->ip(),
    'user_agent'     => $request->userAgent(),
    'document_version' => config('legal.privacy_policy_version'),
    'consent_text'   => ConsentType::current('data_processing')->text,
    'granted_at'     => now(),
]);

Comparison of security levels UZ-4 and UZ-3

Why is data localization critical?

Primary recording of personal data must occur on servers in Russia. Replication abroad is allowed, but the first record must be in Russia. Without a DPA (data processing agreement) with subcontractors, you risk fines. Our lawyers prepare DPA templates compliant with the latest requirements. In practice, this means choosing Russian hosting (Selectel, Yandex Cloud) or configuring Data Residency with foreign providers. Data processing agreements (DPA) with subcontractors are mandatory.

Processing registry and Roskomnadzor notification

Operators must maintain an internal registry of personal data processing and notify Roskomnadzor before starting processing via the portal pd.rkn.gov.ru (exceptions: employee personal data, one-time contracts, public data). Automating the registry reduces filling time by 5 times compared to manual maintenance — saving up to 70% of labor costs.

class ProcessingActivityRegistry
{
    private array $activities = [
        [
            'name'          => 'User registration',
            'purpose'       => 'Providing access to the service',
            'legal_basis'   => 'Consent of the subject (Article 6.1 of 152-FZ)',
            'data_types'    => ['Full name', 'email', 'phone number'],
            'storage_period'=> '5 years after account deletion',
            'third_parties' => ['Sendgrid (email newsletters, DPA signed)'],
            'server_location'=> 'Russia (Selectel, Moscow)',
        ],
    ];
}

In case of a personal data leak, notify Roskomnadzor within 24 hours, and the data subjects within 72 hours.

What you get as a result of implementation

• Privacy policy and consent form compliant with 152-FZ.
• Personal data processing registry with automatic Roskomnadzor notification.
• DPA (data processing agreements) with all subcontractors.
• Technical documentation for configuring encryption, access control, and logging.
• Integration of consent collection system with IP, user-agent, and document version log.
• Staff training on personal data handling and leak response instructions.
• Support during Roskomnadzor inspections and revisions on their requests.

152-FZ implementation process

1. Current state audit: identify gaps and risks.
2. Document development: privacy policy, consent form, processing registry.
3. Technical measures: configure encryption, access control, logging.
4. Notification integration: automate sending to Roskomnadzor in case of leak.
5. Prepare DPAs with subcontractors.
6. Testing: verify all mandatory elements are in place.
7. Support during inspections: consultations and revisions.

Order the full implementation cycle — from audit to support.

Implementation timelines

• Audit + gap analysis: 2-3 days.
• Privacy policy and consent: 3-5 days.
• Technical measures (encryption, logging, access): 5-10 days.
• Roskomnadzor notification and registry: 1-2 days.

Our approach saves up to 40% of budget compared to hiring a separate lawyer and system administrator. Get a consultation for your project — we'll estimate the scope and prepare a commercial proposal. Contact us for an audit of your current state.

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:

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.

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

1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
4. Testing — re-penetration test, load testing, false positive check.
5. 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

The budget is calculated individually — contact us for a project evaluation.