Before approving an agency’s website handover, check what security work the contract includes. A working site may still need testing, configuration review, and an owner for maintenance after launch. Agree those responsibilities while the build team is still involved.
There's no default answer, because responsibility is split by design
The business, developer, host, and embedded-service vendors each handle part of the site. List who owns each control and how an issue moves between them. Resolve gaps before accepting the handover.
What the business owns
The business needs to manage the consequences of a website incident, even when another company built the affected code. Identify the relevant customer-data and reporting obligations with the people responsible for them.
Set security requirements in the statement of work and decide what evidence is needed for acceptance. Name the post-launch owners for patching, monitoring, backups, and reassessment. Check whether those services are included in the agency agreement.
What the development agency is on the hook for
Ask the agency how it reviews authentication, access control, and unsafe input handling during development. Require the agreed secure-coding checks and evidence as part of the deliverable.
Confirm the agency’s terms for post-handover maintenance, plugin issues, hosting configuration, and remediation. Do not rely on “finished” or “secure” without defining the acceptance checks and support period.
What the hosting provider covers, and what it doesn't
Ask the host which infrastructure and platform controls it provides. Application authentication, permissions, custom code, and plugin configuration may remain with the business or agency. Record the division for your hosting plan.
Where this gets murkier is with managed hosting plans that bundle in some patch management, typically limited to the underlying platform and core software versions, not custom code, themes, or the specific configuration choices made during your build. Knowing exactly where your hosting provider's responsibility ends is worth confirming directly, because "managed hosting" means different things across providers.
What third-party vendors are responsible for, and why that's not enough
Inventory plugins, payment integrations, analytics tags, and widgets. The vendor maintains its product, while your team decides whether it belongs on the site and what data it can reach. Review those choices when adding or replacing an integration.
Where vulnerabilities slip through
A gap can appear when each party assumes another tested the assembled site. Include an end-to-end review in the handover plan, with an owner who can route application, hosting, and vendor findings to the right team.
A website acceptance checklist before you sign off
Check HTTPS, headers, administrator authentication, and session-cookie settings. Inspect source and browser bundles for secrets. Document third-party access and test backup restoration. Agree which findings must be fixed and retested before acceptance, and record any exceptions.
An example contract clause to review with counsel
The agreement can define security testing and remediation as deliverables. Discuss wording such as the following with counsel and adapt it to the engagement:
"Developer warrants that the delivered website and all associated code will be free of critical and high-severity security vulnerabilities, as verified by an independent third-party vulnerability assessment conducted prior to final acceptance. Client reserves the right to commission such an assessment at Client's discretion. Any critical or high-severity findings identified within thirty (30) days of delivery shall be remediated by Developer at no additional cost as part of the original engagement, subject to retest verification."
This is a starting point for a conversation with an attorney, not a drop-in legal document, contract language needs to fit your specific engagement, jurisdiction, and risk tolerance, and should always be reviewed by legal counsel before it goes into a binding agreement.
A handoff testing procedure
Freeze the delivery version and test an agreed environment with production-relevant configuration. Cover the application, connected APIs, and hosting settings. Route findings under the agreed remediation terms, deploy the fixes, and retest. Keep the results with the acceptance record before scheduling go-live.
Why this belongs before acceptance, not after
Testing before acceptance gives both sides time to apply the agreed remediation terms. Confirm those terms before the final handover, including who fixes issues discovered later and what the support period covers.
Scope the review around the delivered site and its data. Payment flows, customer accounts, and complex roles may need authenticated testing beyond public checks. Schedule the work early enough to fix findings before launch.
After launch, keep an owner for plugin updates, new integrations, and recurring security review. The acceptance test describes one version of the site. Include relevant retests when later changes alter its controls.