An online store processes customer personal data and payment card data. For attackers this is an attractive target. An attack does not always look dramatic – it is often invisible for weeks or months. A security audit is checking the state of the store before someone else does.
What a security audit checks
Magento version and installed module versions – every version has known vulnerabilities that are publicly documented. Attackers scan for stores with outdated versions. Server configuration: open ports, unnecessary services, file and directory permissions. Admin panel access: whether the URL has been changed, whether 2FA is active, whether there are old administrator accounts.
File integrity: whether the source code shows signs of compromise (modified core files, added scripts, unknown PHP files). SSL configuration and HTTP security headers. Access logs: patterns that may indicate scanning or past intrusion attempts.
Skimming – the silent thief
Magecart is a type of attack involving injecting malicious JavaScript into a store that silently captures payment card data and sends it to the attacker. The store works normally, customers see nothing, the owner knows nothing – for weeks or months. Detection requires regular audits of JavaScript code and Content Security Policy headers.
What to do after the audit
A security audit report contains a list of found issues with risk ratings (critical, high, medium, low) and remediation recommendations. Critical issues (e.g. known unpatched vulnerability, signs of compromise) require immediate action. Others can be addressed in stages. A good audit is not just a list of problems – it also includes process recommendations: how to maintain security after fixing.
If any of the signals described sound familiar, it is worth analysing before the problem grows. I offer a free initial consultation – write to biuro@tews.pl or visit tews.pl.
