What our people actually do
The team does this work. Tools help us watch and check. You get the result in plain English. What you get depends on the plan.
What's included
Fast security updates
The team watches for holes that affect your store. We try to catch relevant news early, including items that aren't on the big public lists yet. That's a goal. It isn't a promise we'll always be first.
Safe testing on a copy
Before anything touches the live store, we try the fix on a private copy. Tech folks call that staging. If it breaks, only the copy breaks.
Checkout checks
We test that a customer can still add to cart and pay. A locked-down shop that can't take an order hasn't been looked after.
Plain-English notes
After a fix, a person sends a short note. What was wrong, what we did, and whether you need to do anything. See an example. It isn't from a real customer.
Skimmer and backdoor check
After a fix we look for hidden card-stealing code (a skimmer) and for an unwanted way in (a backdoor). Standard and Priority include this. Essentials doesn't.
Rollback
A rollback is an undo back to the last good version. We prepare one before a live update, on every plan.
A person reviews the risky changes
On Essentials and Standard, routine updates go through standard checks. If a change is large, or it touches payment, a person reviews it before it goes live. On Priority, a person reviews every update. We'll say in writing, before you start, what counts as large.
The plan-by-plan list is on pricing.
How a store gets taken on
Four steps. After that, most of the work happens without you.
You write
A person replies and asks what the store runs on. Early access doesn't commit you.
Health check
We look at the site with you and agree access. We never ask you to email a password.
Copy and checkout test
We set those up before the first live change. If the host has to change PHP, we tell you what to ask them.
Then we keep watch
We watch, test, update, and write. Plans are month to month.
Stores we're built for
Small stores, and other sites that hold customer data, on WooCommerce, WordPress, Magento, and Shopware. All of them run on PHP. That's the software in the October 2026 PHP2Shell news. What that week means for a shop.
Not sure what you're on? Ask anyway. "Not sure" is a complete answer.
What we'll say straight
Nobody can promise a store will never be hacked. We won't either. Cheap tools mostly scan or block. Hands-on patching for bigger Magento shops already exists, and it usually costs more. CyberWall sits between those, for a small PHP store, with a person in the loop. We don't replace your host, your backups, or decent passwords.
The price ranges behind that are a rough estimate from us, not a quote. They're written out on pricing.
What we need from you
Enough access to make a test copy and apply updates. We agree that up front. We ask only for what the work needs, and we say why. We never ask you to email a password.
The private copy is meant to stay in a private, access-controlled place, and to come down when you leave. The exact spot isn't published yet. We'll confirm it in writing before we take a customer on. Privacy and terms aren't published yet.
Want a real person on your store's security?
We're opening early access to a small number of stores. Tell us about yours. It doesn't commit you to a plan.