Web security & server hardening

Most breaches don’t need a genius attacker. They need a forgotten plugin, a weak login or a server nobody updated. I close those doors in your application and on your server, and build security in from the start, where it’s cheapest.

  • cPanel and WHM certified
  • App and server, together
  • Fixes, not just findings
30%
fewer security vulnerabilities on a booking platform
2018
cPanel and WHM Administrator, certified by exam
10+
years running production applications
Day 1
security built in from the first commit

Measured on client work at Santandrea Top Properties, Shine Software.

01 / Why it matters

Most breaches walk through an open door

Security is cheapest before anyone needs it.

Most attacks aren’t clever. Automated bots scan millions of sites for the same things: outdated plugins, default passwords, login forms with no limits, servers nobody has patched.

A breach costs more than the fix. Downtime, cleanup, lost rankings if Google flags your site, and lost trust from customers who gave you their data. Under the GDPR, a breach involving personal data can also bring reporting duties.

I build security into the application and the server, where it’s cheap, instead of bolting it on after an incident, where it’s expensive.

And because I write the code too, the fixes fit your application instead of fighting it.

02 / Signs

You probably need this if…

06 symptoms
  • Plugins nobody updates

    Your site runs on themes and plugins that haven’t been updated in months, or years.

  • Logins from everywhere

    Your logs show thousands of login attempts from countries you’ve never sold to.

  • Nobody knows the server

    No one can say when it was last patched, or who still has access.

  • You handle personal data

    Accounts, bookings, payments or forms full of names, emails and addresses.

  • You’ve been hit before

    Spam pages, a blacklisted domain or a defaced homepage, and you’re not sure it’s really gone.

  • Backups are a hope

    There are backups, probably, but nobody has ever tried restoring one.

03 / What I secure

Every layer an attacker can reach

06 areas

Security is a chain, and attackers look for the weakest link. I work across the application, the server and the edge, so there’s no gap between the developer’s part and the hosting part.

  • 01Auth

    Authentication and access

    Make sure only the right people get in, with only the rights they need.

    • Multi-factor authentication
    • Secure sessions and password hashing
    • Roles, policies and permissions
    • Access review and cleanup
  • 02Abuse

    Rate limiting and bots

    Slow down brute force, scraping and form spam.

    • Login and API throttling
    • Form and signup protection
    • Cloudflare WAF and bot rules
    • Alerts on suspicious spikes
  • 03OWASP

    Application security

    Close the common holes in code before attackers find them.

    • Injection, XSS and CSRF
    • Input validation and safe uploads
    • Mass assignment and data exposure
    • Dependency vulnerability audits
  • 04Server

    Server hardening

    A server that offers attackers nothing to work with.

    • SSH keys and least privilege
    • Firewall and closed ports
    • Patched OS and software
    • WHM and cPanel security
  • 05Headers

    Transport and headers

    Encrypted everywhere, and browsers told how to protect visitors.

    • HTTPS and HSTS
    • Content Security Policy
    • Secure, HttpOnly cookies
    • Safe CORS configuration
  • 06Recovery

    Backups and recovery

    When something does go wrong, get back fast.

    • Automated, offsite backups
    • Restore tests, not just backups
    • Logging you can investigate
    • A short incident plan

04 / Process

Assess, harden, maintain

01 — 04
  1. 01

    Assess

    Code, configuration and server reviewed, with automated scans and manual checks for what scanners miss.

    You get A risk report in plain language.

  2. 02

    Prioritise by risk

    The issues that could hurt you most, and are easiest to exploit, go first.

    You get A ranked fix list.

  3. 03

    Harden

    Fixes shipped in small, reviewed changes, then verified, so protection never breaks the site.

    You get Doors actually closed.

  4. 04

    Maintain

    Updates, monitoring and periodic reviews, because security decays when nobody looks.

    You get Protection that lasts.

05 / Case study

Security, built into the platform

Santandrea Top Properties homepage, the booking platform whose login flow and server were hardenedPlatform

Santandrea Top Properties · Vue, Nuxt · 2022 to 2023

A booking platform handling customer data, hardened end to end

A property booking platform takes accounts, enquiries and personal details from visitors every day. Alongside the performance work, I hardened the login flow and the server configuration, so the platform stayed fast without leaving doors open.

30%
fewer security vulnerabilities
Hardened
login flow and server config
“Masih provided quick and thorough server management, improving my site’s security, and providing options for further site development.”
Regina Mc Guire, Cybersecurity Coach · Client

06 / Ways to work together

Pick the depth you need

Security review

For teams who want to know where they stand.

A review of your application, configuration and server, delivered as a risk-ranked list your developers can act on.

  • Code and configuration review
  • Server and hosting check
  • Dependency vulnerability scan
  • Risks ranked, critical first

Ongoing security care

For sites that must stay safe as they change.

Regular updates, monitoring and reviews, so new code and new threats don’t quietly reopen what was closed.

  • Monthly updates and patching
  • Dependency and log monitoring
  • Security review of new features
  • Priority response on incidents

07 / Toolkit

Where I work

Application

  • Laravel security
  • OWASP Top 10
  • Rate limiting
  • Dependency audits
  • Validation

Server

  • Linux
  • SSH hardening
  • Firewall
  • WHM / cPanel
  • Apache

Edge

  • Cloudflare WAF
  • HTTPS / TLS
  • Security headers
  • Bot protection

08 / FAQ

Questions clients ask first

How can I tell if my site has been hacked?

Common signs: pages or links you didn’t create, spam showing in Google results for your domain, redirects to other sites, unknown admin accounts, browser or Google warnings, and sudden spikes in server load. If you see any of these, write to me and don’t wait.

Do you offer penetration testing?

I do security reviews and hands-on hardening of your application and server. If you need a formal penetration test or a compliance certificate, I’ll recommend a specialised firm and fix what they find.

Is WordPress insecure?

WordPress core is well maintained. Most WordPress breaches come from outdated plugins and themes, weak admin logins and neglected servers. All of those can be fixed and kept fixed.

What about GDPR?

I put the technical measures in place: encryption in transit, access control, minimal data collection, secure backups and logging. For legal advice on your obligations, talk to a privacy lawyer or your DPO. I’m not a lawyer.

Can you help after an attack?

Yes. Contain the damage, clean the site, restore from a known-good state, find how they got in, and close that door so it doesn’t happen again.

Do you work remotely?

Yes. I’m based in Milano and work with teams in Italy and abroad, fully remotely, in English.

10 / Next step

Before it breaks,
not after.

Tell me what your site runs on and what worries you. If you think you’ve been hacked, say so in the subject and I’ll prioritise it.

Or write directly: masih@masihtak.dev