Web & Cloud Security
Lock it down.
A hacked website or an open storage bucket costs far more than preventing it. Whether your site sits on shared hosting like Hostinger or you run your own infrastructure on AWS, I check what is exposed, fix it, and set up the safety nets so you find out early when something is wrong.
Websites and hosting
Hostinger and similar shared, VPS and WordPress hosting.
- HTTPS everywhere: SSL/TLS, redirects and security headers
- Firewall, bot and brute-force protection (Cloudflare or the host's WAF)
- Malware scan and cleanup, then hardening so it stays clean
- Updates for the core, plugins and themes, and removal of what you don't use
- Two-factor sign-in, least-privilege accounts, safe file permissions
- Automatic off-site backups, and a restore that has actually been tested
AWS infrastructure
EC2, S3, Lambda and the rest of your account.
- IAM: MFA, no root keys, least-privilege roles and policies
- S3: Block Public Access, bucket policies, encryption, versioning, safe sharing links
- EC2: tight security groups, key-only SSH or Session Manager, patching, private networking
- Lambda: minimal execution roles, secrets kept out of code, input validation, limits
- CloudTrail, GuardDuty and CloudWatch alarms so odd activity is flagged
- Billing alerts, so a leaked key can't quietly run up a bill
How a security review goes
- 01
Audit
I look at what is exposed: your site, hosting account and AWS settings.
- 02
Report
A plain-language list of the risks, ranked by how much they matter.
- 03
Fix
I close the gaps, or hand your team exact steps if you prefer to do it yourselves.
- 04
Watch
Backups, alerts and a short checklist so it stays secure.