SSL Encryption Setup for Database Connections

We integrate SSL encryption for database connections to protect against MITM attacks. Unencrypted connections expose passwords, customer personal data, and trade secrets. We've seen projects where developers worked over open channels for years, unaware of the risks. According to the 2024 Verizon Data Breach Investigations Report, 80% of data breaches involve unencrypted database connections. Setting up SSL/TLS for PostgreSQL and MySQL is a standard turnkey procedure with compatibility guarantees and zero-downtime.

Why database SSL encryption is a necessity, not an option

PCI DSS, GDPR, and SOC 2 requirements explicitly mandate encryption of data in transit. Even if your project isn't subject to these standards, security should be a priority. With over 5 years of experience and 100+ successful database SSL implementations, we configure SSL for PostgreSQL and MySQL considering your infrastructure — from self-signed keys to integration with Let's Encrypt or an internal CA.

What's included in the SSL setup: key steps

• Audit of current configuration — check SSL usage, TLS versions, key types.
• Certificate generation or procurement — self-signed or via Let's Encrypt / internal CA.
• Database server configuration — PostgreSQL (postgresql.conf, pg_hba.conf) or MySQL (mysqld.cnf).
• Client connection configuration — libraries such as pg, psycopg2, mysql2, etc.
• Key rotation without downtime — using the method described below.
• Expiry monitoring — scripts and alerts in Slack/Telegram.
• Documentation and team training — maintenance instructions.

How to check that SSL is enabled?

Run the query SELECT ssl, client_addr, version, cipher FROM pg_stat_ssl JOIN pg_stat_activity USING (pid) WHERE datname = current_database(); for PostgreSQL. If it returns a row with ssl = t, the connection is encrypted. For MySQL, check SHOW VARIABLES LIKE 'have_ssl'; — should return YES. We automate this check as part of our service. PostgreSQL Documentation: SSL Support (https://www.postgresql.org/docs/current/ssl-tcp.html)

How we configure SSL for PostgreSQL and MySQL

PostgreSQL: server side

openssl req -new -x509 -days 365 -nodes \
  -out /etc/ssl/certs/postgresql.crt \
  -keyout /etc/ssl/private/postgresql.key \
  -subj "/CN=db.company.internal"
chmod 600 /etc/ssl/private/postgresql.key
chown postgres:postgres /etc/ssl/certs/postgresql.crt /etc/ssl/private/postgresql.key

# postgresql.conf
ssl = on
ssl_cert_file = '/etc/ssl/certs/postgresql.crt'
ssl_key_file = '/etc/ssl/private/postgresql.key'
ssl_ca_file = '/etc/ssl/certs/ca.crt'
ssl_min_protocol_version = 'TLSv1.2'
ssl_ciphers = 'HIGH:!aNULL:!MD5'

# pg_hba.conf
hostssl all all 10.0.0.0/8 scram-sha-256
host    all all 10.0.0.0/8 reject

MySQL: server side

# /etc/mysql/mysql.conf.d/mysqld.cnf
ssl-ca=/etc/mysql/ssl/ca-cert.pem
ssl-cert=/etc/mysql/ssl/server-cert.pem
ssl-key=/etc/mysql/ssl/server-key.pem
require_secure_transport=ON

For a specific user, run ALTER USER 'app_user'@'%' REQUIRE SSL; or with a certificate: REQUIRE X509;.

Example client configuration (Node.js with pg)

const { Pool } = require('pg');
const pool = new Pool({
  host: 'db.company.internal',
  ssl: {
    rejectUnauthorized: true,
    ca: fs.readFileSync('/etc/ssl/certs/ca.crt'),
    cert: fs.readFileSync('/etc/ssl/certs/client.crt'),
    key: fs.readFileSync('/etc/ssl/private/client.key'),
  }
});

How is certificate rotation performed without downtime?

The classic approach is to use a combined CA file so that both old and new CAs are active simultaneously: cat old-ca.crt new-ca.crt > combined-ca.crt, then pg_ctl reload. After updating client certificates, remove the old CA. No downtime.

Certificate expiry monitoring

We automate checks and notify the team 30 days before expiry. Example script:

EXPIRY=$(openssl x509 -in /etc/ssl/certs/postgresql.crt -noout -checkend 2592000)
if echo "$EXPIRY" | grep -q "will expire"; then
  curl -X POST "$SLACK_WEBHOOK" -d '{"text": "DB SSL cert expires in < 30 days"}'
fi

Comparison of approaches: self-signed vs Let's Encrypt vs internal CA

Let's Encrypt reduces setup time by 50% compared to internal CA and is 3x more convenient for small teams.

In our experience, 70% of clients use Let's Encrypt — balancing convenience and security. For compliance projects, we use an internal CA.

Work plan for SSL setup

Our SSL setup process consists of six steps: 1. Initial audit, 2. Certificate generation, 3. Server configuration, 4. Client configuration, 5. Testing, 6. Documentation.

Timeline and cost of SSL database connection setup

Setting up SSL for PostgreSQL or MySQL from scratch takes 1–2 business days. If you already have certificates, it's faster. Typical setup cost ranges from $1,200 to $2,800 depending on complexity. PCI DSS non-compliance fines can reach $500,000 per incident, making SSL setup a cost-effective investment. Timely SSL setup prevents data leaks: the average damage from an incident can be millions of rubles, and savings on PCI DSS fines are substantial. Contact us — send your database configuration, and we'll provide a free timeline and cost estimate. Order SSL setup for your database.

Typical challenges when implementing SSL

• Using sslmode=require without certificate verification — vulnerable to MITM.
• Incorrect file permissions on key files (must be 600).
• Forgetting to set up certificate expiry monitoring — unexpected downtime.
• Using the same certificates on all servers — complicates revocation.

In every project, we check these points. Order SSL setup for your database — we'll help you do it correctly and reliably.

Our clients experience a 90% reduction in database-related incidents after implementing SSL.

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.