What the Security Audit Covers
We look at the site through the eyes of both a developer and an attacker: where someone could get in without permission, what data could leak and what would break first.
- Software: versions of your CMS, framework, modules, themes, libraries, PHP and database.
- Access: accounts in the admin panel, on the server, with your hosting provider, in the database and in third-party services.
- Code: handling of forms and user data, file uploads, and protection against the most common attacks, including OWASP-listed ones.
- Server: HTTPS, open ports, file permissions, and system files and pages exposed to the outside.
- Backups: whether they exist, where they are stored and whether you can actually restore from them.
- Signs of compromise: unknown files, hidden links, suspicious admin accounts and code changes.
It helps to know the limits. A technical audit is not a certification or a legal opinion on compliance with standards, and it doesn't replace full penetration testing for banks or large platforms. For most business websites and online stores, it covers the main real-world risks.
What You Get
A report that makes sense to non-technical people too. For every issue we describe what exactly is wrong and where we found it, what it puts at risk for your business (customer data leaks, lost sales, lower search rankings), how urgently it needs to be fixed, and how to fix it, including whether that can be done without taking the site down. The report is yours to keep. We can make the fixes ourselves or hand the recommendations to your developers.
Safe Updates
Once a fix for a vulnerability is published, details become public and bots start scanning for sites that haven't updated. At the same time, updating everything blindly is risky: a new module version can conflict with custom code and break checkout. So we run updates on a staging copy, test the key user flows and only then push them to the live site. If a module is no longer supported by its author, we suggest a replacement.
Who Needs an Audit, and Who Might Not
- You inherited the site from another contractor and don't know what is under the hood.
- The site hasn't been updated in a long time.
- You've noticed warning signs: unfamiliar ads, redirects to other sites, warnings in search results or the browser, a sudden spike in server load.
- The site stores customers' personal data, accepts payments or has user accounts.
- You are preparing for a major ad campaign or investor due diligence.
If a team already maintains your site and watches security, a standalone audit is needed less often, for example after major changes.
One-Time Audit or Ongoing Updates
A one-time audit gives you a snapshot of where things stand today and a plan of fixes. It makes sense when you need to understand your risks quickly, or when an in-house team wants an outside perspective. Ongoing maintenance means scheduled updates, access reviews and re-checks after changes. It is usually part of website support, and on the server side we handle updates as part of server administration.
What to Prepare on Your Side
- Access to the admin panel, server or hosting account, and, if possible, the code.
- A list of people and companies who currently have or previously had access to the site.
- Details of any suspicious incidents, if there were any.
- A list of third-party services connected to the site: payments, CRM, email marketing, analytics.
What Affects the Cost of an Audit
- Site size and type: a site on a popular CMS is easier to review than a system with a lot of custom code.
- Audit depth: versions and settings only, or manual code review as well.
- The number of servers and services included in the scope.
- Amount of remediation: whether it is just module updates, or rewriting unsafe code and cleaning up after a breach.
Frequently asked questions
Will the audit affect how the site works? Usually not. We run checks carefully, and anything that could affect the site is done on a staging copy.
My site has already been hacked. What should I do? Don't delete anything yourself, and change the passwords for the admin panel and hosting. We'll help you find out how the breach happened, remove the malicious code, close the vulnerability, and restore the site from a clean backup.
How often should a site be updated? Critical security updates should be installed as soon as possible after release; the rest can follow a schedule. The exact cadence depends on your CMS and the number of modules.
Can you audit a site you didn't build? Yes, audits are often ordered precisely for sites inherited from other contractors.
Do you fix the problems you find? Yes, if you want us to. Critical issues go first, and every update is tested on a staging copy. You can also take the report to your own developers.
Does the audit include a compliance certificate? No. It is a technical review with a prioritized report, not a certification or a legal opinion.
Why Promodex
Promodex has built websites on a range of CMSs and frameworks since 2015, so we check security with an understanding of how the code works from the inside, not against someone else's template. One in-house team does both the audit and the fixes, with no outsourcing, and you know in advance what we are doing and why. After the audit, we can stay on and keep your site updated.