Website security

Website security services that cut the logins, plugins and scripts an attacker can reach

We review who can sign in, what is installed and which scripts load on your payment pages, make the changes you approve, and write down how the site is brought back if something goes wrong.

Get a security review of your website
Trusted by the world's fastest-growing brands

Portfolio · selected work

The work, not the deck.

Every site below is live and owned by the client. Each window is a capture of the real page, not a drawn mockup.

Categories we work across
HospitalityFinancial servicesManufacturing and exportConsulting and researchRecruitmentD2C
urjalifes.inUrjalife's Pravaah resort website: rooms, activities and dining across a photographic homepage.
UrjalifeHospitality
adventswealth.comAdvents Wealth website: a financial planning homepage covering wealth building, tax and retirement.
Advents WealthFinancial services
syounaa.inSyounaa website: a wellness apparel storefront built around smart-textile product ranges.
SyounaaWellness apparel
infokool.comInfokool website: a precision cooling manufacturer, with an outdoor cabinet product grid and capability sections.
InfokoolManufacturing
howardjohnsonhinton.caHoward Johnson Hinton website: a mountain-lodge hero over a room-booking bar, followed by renovated room types.
Howard Johnson HintonHotel
sycamoreconsultant.comSycamore Consultancy website: a recruitment agency, with separate paths for employers and candidates.
Sycamore ConsultancyRecruitment
stutiexports.comStuti Exports website: a technical fibers and specialty yarns exporter, with core markets and capability sections.
Stuti ExportsTechnical textiles
duhomespg.inDuhomes website: student housing, with walking distances to nearby colleges and a room rate table.
DuhomesStudent housing
vaspro-global.comVasPro Global website: a technical advisory and project consulting firm, with expertise and mission sections.
VasPro GlobalConsulting
pretor.aePretor website: a marketing research and promotion consultancy, opening on research, strategy and growth planning.
PretorMarketing research

What the work covers

Three records that show what an attacker could reach

Website security services are the work of limiting what a site exposes and preparing for the day something gets through: logins, software, scripts and recovery. Nobody can make a site unhackable, so the work is judged by what it removes and by what you can read afterward.

Exposure reviewRestore testedSample Wheelhouse Cycle PartsBeforeAfterAdmin accounts4 had left59Plugins5 unused1621Checkout scripts2 had no owner4601224

A list of who can get in

Administrator, editor, hosting and developer accounts go on one list, with the person it belongs to and whether a second sign-in step protects it. Accounts of people who left are the first thing to come off.

A list of what is exposed

Plugins, themes, the login page, file permissions and the scripts that load on checkout are each checked against what the site needs. Anything without a job is removed, and the change list says what and why.

A plan for the bad day

A written order of steps for a suspected break-in: who is called, which passwords change first, which backup is used and who decides to take the site offline. You can follow it without us.

How it’s run

Two ways to protect the same website

Both add protection. They differ in whether anyone has looked at what the site exposes, and in what you can keep on file.

A security plugin aloneInstalled and left to runA scoped security reviewSet in a written scope
Starting pointThe plugin is installed on the site as it standsA review of accounts, software, scripts and backups before anything changes
Sign-inLogin attempts are limited, and the account list is left as it wasEach account listed, former staff removed, a second step set for the administrators
Payment pagesScripts added over the years keep loading, with no list of themEach script on the page named, owned and approved, with a firewall rule set for the checkout
When something happensAn alert email arrives, and the steps are decided that dayA written plan, a restore you have seen work and a list of who is called
EvidenceA dashboard showing what the plugin blockedReview, change list and recovery record, dated and kept by you
Why we start with a review

A plugin can only filter what reaches a site. The review finds what the site hands out on its own: old accounts, forgotten code and scripts nobody owns.

The facts

Six facts behind the security scope

What OWASP, CISA, Google, the payment-card standards council, the FTC and the state legislatures say. Sources under each.

  1. Risk listOWASP

    OWASP ranks broken access control first and software supply chain failures third.

    OWASP’s 2025 Top 10 ranks ten categories of web application risk. Access control, meaning who may do what, sits first, and the third-party code a site depends on sits third. On a store, those are admin accounts and plugins, so each gets its own step.

  2. Sign-inCISA

    CISA ranks a security key as the strongest second step and a text code as the weakest.

    CISA lists multifactor options from most to least secure, with a security key first and text or email codes last, to be used only when stronger options are not available. It says to start with admin accounts and employees who handle sensitive data.

  3. Hacked sitesGoogle

    Google says fixing some pages of a hacked site does not earn a partial return to search.

    Google’s Security Issues report covers hacked content, malware and social engineering. Pages can carry a warning label in search results, and browsers can show a full-page warning. A review is requested only after all the issues are fixed on all pages.

  4. Payment pagesPCI SSC

    A card-industry criterion asks merchants with an embedded payment form to confirm their page is not open to script attacks.

    A PCI Security Standards Council FAQ says the SAQ A criterion applies to merchants whose page embeds a payment provider’s form, such as in an iframe, and not to merchants that redirect to the provider. The merchant can protect its own page with techniques such as requirements 6.4.3 and 11.6.1, or instead get confirmation from its PCI DSS compliant payment provider that the embedded form is protected from script attacks.

  5. Financial firmsFTC

    The FTC Safeguards Rule names tax preparers and mortgage brokers among the businesses it covers.

    Every covered firm needs multifactor authentication and encryption. Firms holding information on 5,000 or more consumers must also keep a written risk assessment and an incident response plan. The rule also requires telling the FTC within 30 days of discovering a breach involving unencrypted information on at least 500 consumers.

  6. Breach lawsNCSL

    All 50 states, the District of Columbia, Guam, Puerto Rico and the Virgin Islands have breach notification laws.

    The National Conference of State Legislatures summarizes laws requiring businesses to notify individuals after a breach of personal information. The laws differ by state, so a business that sells across state lines may answer to several of them at once.

The scope

What website security work produces

Each part ends in a document, a setting or an account of yours. Which parts apply to your site is set in the written scope.

AdministratorsSecond step 5 of 5OwnerStep onManagerStep addedFormer staffRemovedMarketingStep addedEx-developerRemovedSupportStep addedFormer staffRemovedWebzeniaStep onFormer staffRemoved

Access review

Each account that can change the site, the host, the domain or the payment dashboard is listed with its owner and the date it was last used. Accounts of people who left are removed, and the administrators get a second sign-in step. You receive: the account list, and a record of what was removed and what was added.

AdminsHostingRegistrar
Plugin cleanupTested on staging21−516InstalledUnusedKept2 abandonedreplacedFile editorOn → Off

Hardening

Unused plugins and themes are deleted, abandoned ones are replaced, file permissions are tightened and the dashboard file editor is turned off. Changes are tested on a staging copy and released with your approval. You receive: the change list, with a reason beside each line.

PluginsPermissionsLogin page
Firewall rules3 rules, was 0Login attemptsRate limitAdmin and checkoutBlockWhenPathis in/wp-admin, /checkoutandCountrynot inShipping listAutomated trafficChallenge

Firewall rules

Rules at the firewall in front of the site limit login attempts, block requests aimed at admin and checkout paths from places your customers are not, and challenge automated traffic. The rule set sits in an account in your name. You receive: the rule list, and what each rule is meant to stop.

wheelhousecycle.test/checkoutPaymentProvider’s frameCard numberMM/YYCVCPlace order6 scripts foundRemoved, no ownerHeatmap toolPop-up tool4 keptEach has an owner

Payment-page scripts

Each script that loads on a page where customers pay is named, tied to an owner and a purpose, and approved or removed. We ask your payment provider and acquirer which questionnaire applies to you. You receive: the script list, and the questions to bring to your acquirer.

CheckoutTag manager
Who is toldSet in the scopeOwnerManagerDeveloperChanged filesFile scanFlawed versionsVersion scanGoogle noticesSearch Console

Scans and alerts

The site is scanned for changed files and known flawed versions, and Search Console is connected so Google’s security notices reach a named person. Who is told, and how often each scan runs, is set in the written scope. You receive: the scan settings, and the names of the people alerted.

Incident stepsPrint copy1Call the store owner(816) 555-01432Decide on going offlineStore owner3Change passwords firstStore manager4Restore off-server copyMatched1,840products6,412accounts12,306orders

Recovery plan

A copy of the site is held off the server, restored to a clean location and checked, and the order of steps for a suspected break-in is written out with phone numbers and decision rights. You receive: the recovery record, and the incident steps in one document you can print.

How it runs

Review the exposure, make the changes, check the scripts, prove the recovery

Your approval opens the next stage, and the stage before it leaves you a document to keep.

exposure-review.csv

Exposure review

Sample · Sample Wheelhouse Cycle Parts, Kansas City, MO
ItemFoundFinding
Administrator accounts94 belong to people who no longer work with the store
Second sign-in step2 of 5 current adminsNeeded for the other 3
Plugins installed215 unused; 2 of the 16 in use no longer updated by their authors
Scripts on the checkout page62 have no named owner
Payment formEmbedded from the payment providerAsk the acquirer which questionnaire applies
BackupsDaily, on the same serverNo copy off the server
An online parts store on WordPress and WooCommerce. The 4 former-staff accounts and the 5 unused plugins are the first items on the change list.

Our stack

The tools and accounts behind the work

What we use to limit exposure and to show the result. Pick one for the detail.

Cloudflare
Why Cloudflare

Cloudflare sits in front of a site and can limit how often a visitor may try an address.

How we use it

We write rate limits for the login page and a rule for the admin and checkout paths, each with a line saying what it is meant to stop, in an account in your name.

Network reachSecurityTLS included
CloudflareYes
AkamaiPaid
FastlyPaid
AWS CloudFrontACM

Questions

Website security services, answered

Start here

Get a security review of your website

Give us your site address and say what it handles. We’ll list who can sign in, what is installed, which scripts load where customers pay and where the backups sit, then quote the work in a written scope.