Home / Services / Managed services / Website security
Website security
Find the weak spots before someone else does
We audit your website or web application, explain what we find in plain language, and close the gaps in the code, the server and the way people log in.
- Audit report with findings rated by risk
- Prioritised fix list with plain-language explanations
- Hardening changes applied and documented
- Admin account review and access register
- Firewall and security header configuration
- Recommendations for ongoing monitoring
Proof you can check
Our own products, numbers and community record, linked wherever you can check them.
(opens in a new tab)
(opens in a new tab)
(opens in a new tab)- 300,000+sites run Divi Extended (opens in a new tab)
- Platinumsponsor, WordCamp Rajasthan 2026 (opens in a new tab)
- 6 + 1free plugins and a theme on WordPress.org (opens in a new tab)
- 4.7 / 5on Trustpilot, 116 reviews of Divi Extended (opens in a new tab)
What is included
The work, piece by piece.
Security audit
A review of the application, plugins and themes, server configuration, file permissions and exposed services, with each finding rated by risk.
Code and plugin review
Custom code checked for injection, broken access control and unsafe file uploads. Plugins for WordPress checked against known vulnerabilities and abandoned projects.
Server and header hardening
TLS settings, security headers, firewall rules and disabled services that should never have been reachable from the internet.
Access and login control
Two-factor login for admins, removal of old accounts, least-privilege roles and limits on repeated login attempts.
Web application firewall
A firewall configured in front of the site, through Cloudflare or your host, with rules adjusted so real customers are not blocked.
Payment and data handling
A check that card payments stay on the payment provider's side, and that personal data is stored and logged appropriately.
Signs you need this
When teams usually call us.
01
The site collects personal data or payments
Contact forms, customer accounts and checkouts all hold data worth protecting. An audit shows how well they do it.
02
Former staff or agencies may still have access
Old admin accounts and shared passwords are among the most common ways in. We find and remove them.
03
A client or partner sent a security questionnaire
An audit and hardening report give you documented answers instead of guesses.
How we work
No surprises, start to finish.
Talk to the developers doing the work, by email or call, whenever you need.
01
Talk
Tell us what you need. We ask questions until the scope is clear.
02
Plan and quote
A clear scope with an hourly, fixed or monthly-hours price.
03
Build on staging
Every change is built on a staging site first, never on your live site.
04
Sign off and launch
You review and approve. Then we go live with zero downtime.
05
Care
We stay on for updates, fixes and new features, if you want us to.
Related
Often part of the same project.
- Malware removalHacked site cleaned and the entry point closed
- Care plansUpdates on staging, monitoring and hours
- Managed hostingServers sized, patched and watched for you
- Finance and fintechOnboarding, KYC, payments and fintech apps
- HealthcarePatient booking, reminders and clinic operations
- Retail and e-commerceStores, marketplaces and order support
For agencies
Your development team for WordPress, under your name.
Agencies around the world send us their builds on WordPress. We do the work, you keep the client, and our name appears nowhere.
White-label
Your brand on everything. No Elicus credit, ever.
NDA-friendly
Happy to sign yours before we see a brief.
Scale on demand
We grow the team to fit the project.
Your terms
Something specific in mind? We'll talk it through.
Questions
Before you ask.
Is this a penetration test?
It is a configuration and code audit with hardening. If you need a formal penetration test from an independent firm, we can prepare the site for it and fix what it finds.
Will hardening break anything?
Changes are tested on a staging copy first. Where a setting could affect customers, such as firewall rules, we watch the live site closely after release.
Do you audit sites you did not build?
Yes. Most audits are for sites built by other teams. We need admin and server access, which we remove at the end if you ask.
How often should a site be audited?
After major changes, and at least once a year for sites that take payments or hold customer data. Monitoring between audits catches most new issues.
Start a project
Tell us what you’re building.
A few lines is enough. The developers who will do the work read every message.
