Website Security Checklist: What Every Business Website Should Have
A practical, defensive security checklist — HTTPS, authentication, input validation, dependency security, backups and monitoring — for any business website.
Quick answer
A secure business website needs, at minimum: HTTPS everywhere, proper authentication and authorization, secure session handling, input validation on every user-submitted field, current and monitored dependencies, careful secrets management, API security and rate limiting, regular backups, and ongoing monitoring and logging. This is a defensive implementation checklist — the goal is closing common, well-understood gaps through good practice, not offensive security testing.
HTTPS
Every page of a website should be served over HTTPS, not just pages handling obviously sensitive data — browsers flag non-HTTPS sites as "not secure," and encrypted transport is a baseline expectation, not an optional upgrade.
Authentication
For any site with user accounts, authentication needs to verify identity reliably — strong password requirements or, where appropriate, multi-factor authentication, and secure password storage (properly hashed, never stored in plain text).
Authorization and Access Control
Authorization confirms what an authenticated user is actually allowed to do — a site can authenticate users correctly and still have serious gaps if it doesn't properly restrict actions and data access by role. Every sensitive action should verify authorization on the server, not just hide a button in the interface.
Secure Sessions
Session tokens should be generated securely, transmitted only over HTTPS, and expire appropriately — a session that never expires or that's vulnerable to being intercepted is a real, exploitable risk.
Input Validation
Every piece of user-submitted data — form fields, URL parameters, uploaded files — should be validated and sanitized before it's processed or stored. This is foundational defense against a wide range of common web vulnerabilities, and it belongs on both the client and the server, since client-side validation alone can be bypassed. For the full set of business rules beyond security, see 15 data validation rules for business applications.
Dependency Security
Websites rely on external libraries and packages, and vulnerabilities are regularly discovered in widely used ones. Keeping dependencies current and using automated vulnerability scanning is one of the most practical, high-value ongoing security practices — this should be a routine part of maintenance, not a one-time setup task.
Want your website's security posture reviewed?
ZSpace Labs can audit your site against this checklist and identify concrete, prioritized gaps to close.
Secrets Management
API keys, database credentials and other secrets should never live in front-end code or get committed to version control — use environment variables or a dedicated secrets manager, and rotate any credential that's ever been exposed.
API Security
Every API endpoint needs its own authentication and authorization checks — an API is a genuine attack surface, not an implicitly trusted internal channel just because it's not a public-facing page. See the API integration guide for the broader integration context this sits inside.
Rate Limiting
Limiting how many requests a single user or IP can make in a given time window protects against abuse — brute-force login attempts, scraping, or overwhelming a specific endpoint — and should be applied to sensitive endpoints like login and password reset in particular.
Backups
Both code and data (database, uploaded content) should be backed up regularly and stored securely, separate from the primary system. A backup that's never actually been tested for successful restoration isn't a reliable safety net — test the restore process periodically, not just the backup creation.
Monitoring and Logging
Logging access attempts, errors and unusual activity — paired with active monitoring — is what turns a security incident from something discovered weeks later into something caught and addressed quickly.
Ready to build security into your development process from the start?
See the website development process guide for how security fits alongside design, development and QA. Learn more about our Next.js and React development work.
Updates and Patch Management
Security patches for known vulnerabilities lose their value the longer they go unapplied — regular, disciplined updates to the CMS, framework, plugins and dependencies are a core ongoing responsibility, not a one-time launch task.
Deployment Security
Production credentials, environment configuration and deployment pipelines should be handled with the same care as the application itself — a secure application deployed through an insecure pipeline is still a real vulnerability.
Third-Party Services
Every third-party script or service integrated into the site — analytics, chat widgets, ad tech — is a piece of the site's security surface. Review what access and data each one actually has, and remove ones that are no longer genuinely needed.
The Practical Security Checklist
- HTTPS enforced across every page, not just checkout or login
- Passwords securely hashed; multi-factor authentication offered where appropriate
- Authorization checks enforced server-side for every sensitive action
- Session tokens generated securely and expire appropriately
- All user input validated and sanitized on the server, not just the client
- Dependencies kept current with automated vulnerability scanning in place
- Secrets stored in environment variables or a secrets manager, never in code
- Every API endpoint has its own authentication and authorization checks
- Rate limiting applied to sensitive endpoints like login and password reset
- Backups run regularly and restoration is tested periodically
- Access logging and monitoring in place for unusual activity
Pre-launch security sign-off
The checklist above describes controls. A launch needs something slightly different: proof that each control is actually in place on the production system, a person who owns each check, and a clear rule about which gaps stop the launch. Most launch-day problems are not exotic. Debug mode is left on, test keys reach production, an admin route is open to the internet, or nobody has ever restored a backup. The table below is a sign-off sheet you can copy into a ticket or spreadsheet a week or two before go-live. It applies equally to a brochure site with a contact form and a web application with user accounts; drop the rows that do not apply and write down why.
Two rows deserve a note. The cross-account access test comes from OWASP's API Security Top 10, whose first item is broken object level authorisation (BOLA). OWASP says the server should check that the logged-in user "has permissions to perform the requested action on the requested object", and recommends writing tests for exactly that. In practice: sign in as user A, copy the URL or API call for one of A's records, then repeat it signed in as user B. B should get an error, not the record. The security.txt file follows RFC 9116, which says the file must sit under the /.well-known/ path and must include a Contact field and exactly one Expires field. It tells anyone who finds a vulnerability how to reach you.
The "blocks launch?" column is our recommendation, not a standard. Adjust it to your risk, but decide it before launch week, when there is pressure to wave things through. Where a blocker is accepted rather than fixed, record who accepted it, why and by when it will be fixed.
| Check | Evidence to keep | Owner | Blocks launch? |
|---|---|---|---|
| Production configuration: debug off, generic error pages, test and demo accounts and seed data removed | Screenshot of an error page in production; list of accounts removed | Lead developer | Yes |
| Secrets: live keys only in a secrets manager or environment settings; no test keys in production | Secrets inventory with location and last rotation date | Lead developer | Yes |
| Admin access: admin routes behind SSO or MFA, or IP-restricted; least-privilege database and cloud roles | Access list showing who has admin and why | Technical owner | Yes |
| Cross-account access (BOLA) test on two accounts for every record type users can reach by ID | Test script or recorded result for each endpoint | Lead developer or tester | Yes, for any app with user accounts |
| HTTPS everywhere; cookies set Secure and HttpOnly with a SameSite setting; agreed security headers present | Header and certificate scan output | Lead developer | Yes for HTTPS; fix other gaps or accept in writing |
| Dependency and vulnerability scan with an agreed severity threshold | Scan report; each open critical or high finding fixed or accepted in writing | Lead developer | Yes, if critical or high findings are unexplained |
| Backups running, and one restore tested to a separate environment | Date of the restore test, what was restored and how long it took | Hosting or DevOps owner | Yes |
| Logging of sign-ins, permission changes and admin actions; alerts routed to a named person | Sample log entries; alert routing settings | Technical owner | Yes for apps with accounts or payments |
| Disclosure: /.well-known/security.txt with Contact and Expires; an internal incident contact list | The live file URL; the contact list and where it is kept | Site owner | No, but fix within the first week |
| Release safety: a rollback plan; a pen test or security review where the risk warrants it | Rollback steps; review report or a written decision not to test | Project lead | Depends on risk; decide in advance |
| Named sign-off | Name, role, date and the list of accepted risks with fix dates | Business owner of the site | Yes. No launch without it |
Pro tip
If you are commissioning a pen test or security review before launch, see how web application penetration testing works for what to prepare. For apps built quickly with AI coding tools, add the checks in AI-generated code security to this sheet.
How This Checklist Maps to the OWASP Top 10:2025
The OWASP Top 10 is the most widely used reference list of web application security risks. The current edition is the OWASP Top 10:2025. It keeps broken access control in first place and adds two categories: software supply chain failures and mishandling of exceptional conditions. If a supplier, auditor or questionnaire refers to 'the OWASP Top 10', check which edition they mean; older documents may still use the 2021 list.
The right-hand columns are our plain-language summary and our mapping to the sections above, not OWASP's own wording. For APIs, OWASP publishes a separate API Security Top 10 (2023 edition), whose first item is broken object level authorisation.
| OWASP Top 10:2025 category | In plain terms | Where it sits in this checklist |
|---|---|---|
| A01 Broken Access Control | Users reach data or actions they should not | Authorization and access control; API security |
| A02 Security Misconfiguration | Default settings, open admin panels, verbose errors, missing headers | Deployment security |
| A03 Software Supply Chain Failures | Vulnerable or compromised packages, plugins, build tools or services | Dependency security; third-party services |
| A04 Cryptographic Failures | Missing or weak encryption, poor password storage | HTTPS; authentication |
| A05 Injection | Untrusted input treated as code or a query | Input validation |
| A06 Insecure Design | Controls missing by design, such as no limit on password resets | Rate limiting; design review |
| A07 Authentication Failures | Weak login, credential stuffing, session flaws | Authentication; secure sessions |
| A08 Software or Data Integrity Failures | Unverified updates, data or pipeline steps | Deployment security; updates |
| A09 Security Logging and Alerting Failures | Attacks go unnoticed or unanswered | Monitoring and logging |
| A10 Mishandling of Exceptional Conditions | Errors that fail open or leak information | Input validation; error handling |
Mapping Website Security to NIST CSF 2.0
If your organisation uses a security framework, the most common general one is the NIST Cybersecurity Framework. Version 2.0 was released on 26 February 2024 and has six functions: Govern, Identify, Protect, Detect, Respond and Recover, with Govern newly added. The framework is voluntary. Mapping your website tasks to it shows gaps that a technical checklist alone tends to miss, especially ownership and recovery.
| NIST CSF 2.0 function | What it asks | Website practices |
|---|---|---|
| Govern | Who decides, who owns risk, how suppliers are managed | A named site owner; security expectations in agency and hosting contracts |
| Identify | What you have and what could go wrong | Inventory of domains, servers, plugins, third-party scripts and the data each form collects |
| Protect | Safeguards | HTTPS, MFA, validation, secrets management, patching, backups |
| Detect | Spotting problems quickly | Logging, uptime and file-change alerts, Search Console security issues |
| Respond | Acting on an incident | A short runbook: who to call, how to take the site offline, which credentials to rotate |
| Recover | Getting back to normal | Tested restores, clean redeploys, customer communication |
Monthly and Quarterly Security Tasks
Security is mostly routine. The cadence below is our recommendation for a typical business website; raise the frequency for ecommerce, portals and sites holding sensitive data. Many of these tasks overlap with the website maintenance checklist, so run them together.
| Task | Frequency | Notes |
|---|---|---|
| Apply CMS, plugin, framework and dependency security updates | Monthly at minimum; critical patches as soon as practical | Test on staging first where possible |
| Review dependency vulnerability alerts | Monthly | Remove packages you no longer use |
| Check the Google Search Console Security Issues report | Monthly | Flags hacked content, malware and social engineering that Google detects |
| Review admin and editor accounts; confirm MFA | Monthly | Remove leavers and agency accounts that are no longer needed |
| Review logs and alerts (failed logins, unusual traffic) | Monthly, with real-time alerts for critical events | |
| Check TLS certificate expiry and HTTPS redirects | Monthly | Automate renewal, but verify it worked |
| Test a restore from backup | Quarterly | Restore to a staging environment and check it works |
| Review third-party scripts, especially on payment pages | Quarterly | PCI DSS has its own requirements for payment-page scripts if they apply to you |
| Check runtime versions (PHP, Node.js) against supported releases | Quarterly | Plan upgrades before end of support |
| Rotate high-value secrets and API keys | Quarterly, or per your policy | Immediately if exposed |
| Run a configuration and security-header scan | Quarterly | |
| Walk through the incident runbook | Twice a year | Update contacts and access details |
UAE and GCC Considerations
General best practice vs legal obligation. Everything above is general good practice that applies anywhere. Some organisations in the UAE also have specific legal or contractual security obligations. Which ones apply depends on your sector, your free zone, whether you take card payments and whether you handle health data. The table summarises what we found; it is not legal advice, so confirm your position with the relevant authority or an adviser.
UAE facts: threat context. According to the UAE government's head of cyber security, the country faces more than 200,000 cyberattacks a day. The UAE Cyber Security Council has also announced a National Cybersecurity Strategy covering 2025 to 2031; we could not read the official text, so check the Council's own publications for its scope.
UAE facts: the IA Regulation is not for everyone. The UAE Information Assurance Regulation is often mentioned in vendor marketing as if every business must comply. AWS's compliance summary states that 'TDRA requires entities designated as critical to implement the IAR'. Government entities and designated critical entities are the core audience. If you supply such an organisation, expect its security requirements to reach you through contracts and audits.
- Write down which regimes apply to you, and which do not, with a date and who confirmed it
- For card payments, confirm your PCI DSS scope with your payment provider; a hosted payment page usually reduces it
- For health or other sensitive data, check hosting location, backup location and supplier access before launch; see cloud migration in the UAE for UAE hosting regions
- Secure every integration endpoint as its own attack surface; see API integration for UAE businesses
- Ask any agency you hire how they handle updates, access and incidents; choosing a web development company in Dubai lists the questions
| Regime | Who it applies to | What it means for a website |
|---|---|---|
| UAE IA Regulation | Entities TDRA designates as critical, and government entities | If in scope, formal controls and audits; if you supply them, contractual flow-down |
| PDPL (Federal Decree-Law 45/2021) | Processing of personal data in the UAE, outside free zones with their own data laws | In force since 2 January 2022; secure handling of form and account data; we could not find published executive regulations as of October 2026, so take advice on breach and handling duties rather than assume them |
| DIFC and ADGM data protection | Businesses established in those free zones | Separate regimes; both treat pre-ticked boxes as not valid consent, and DIFC treats analytics and advertising cookies as behavioural advertising |
| PCI DSS v4.0.1 | Businesses that accept card payments, depending on how payment pages are built | Requirements 6.4.3 (payment-page script management) and 11.6.1 (detecting unauthorised payment-page changes) have applied since 31 March 2025 where in scope |
| Health data rules | Clinics and other health providers | Federal Law 2/2019 Art. 13 restricts storing or processing health data outside the UAE; ADHICS V2 in Abu Dhabi requires UAE hosting, including backups and disaster recovery, for in-scope health information |
Worth noting
No checklist guarantees security. Following this one reduces the most common and well-understood risks; it does not replace a risk assessment, security testing for higher-risk sites or legal advice on your obligations.
Conclusion
Website security is a defensive discipline built from many individually manageable practices — HTTPS, validation, authentication, dependency hygiene, backups and monitoring — rather than one single fix. Treat it as an ongoing responsibility that continues well past launch, not a checkbox to clear once before going live. For how to design these protections in during development, see building a secure business website. For Australian small businesses, including the Essential Eight and data breach notification, see website security in Australia.
For related guides, see ecommerce security and ecommerce security audit.
Common questions.
Yes — HTTPS encrypts data in transit, is expected by browsers (which flag non-HTTPS sites as "not secure"), and is a baseline requirement regardless of whether the site handles sensitive data directly.
Authentication confirms who a user is (login); authorization confirms what that authenticated user is allowed to do. A site can have solid authentication and still have a serious authorization flaw if it doesn't properly restrict actions by role.
Websites rely on external libraries and packages, and vulnerabilities are regularly discovered in widely used ones — keeping dependencies current and monitored is one of the most common, practical ways real breaches are prevented.
Checking and sanitizing any data a user submits before it's processed or stored — this prevents a wide range of attacks that rely on malicious or unexpected input, including some of the most common web vulnerabilities.
Never in front-end code or committed to version control — use environment variables or a dedicated secrets manager, and rotate credentials if they're ever exposed.
Yes — smaller, less-monitored sites are frequently targeted precisely because they're assumed to have weaker defenses, not because attackers only target large companies.
Regularly, as part of ongoing maintenance — not just at launch. Security patches for known vulnerabilities lose their value the longer they go unapplied.
Both the site's code and its data (database, uploaded content), stored securely and tested periodically — a backup that's never been tested for successful restoration isn't a reliable one.
No — this is a defensive implementation checklist for building and maintaining a secure site. Formal security testing is a separate, specialized practice worth engaging directly for higher-risk applications.
Production settings are locked down, admin access is restricted, one user cannot open another account's records, dependency scans show nothing critical or high left unexplained, a backup has actually been restored, alerts reach a named person, a security.txt file gives researchers a contact, and a named owner has signed off with any accepted risks written down. The sign-off table on this page lists the evidence to keep for each.
Use the current edition, the OWASP Top 10:2025. It keeps broken access control as the top risk and adds software supply chain failures and mishandling of exceptional conditions. Older supplier questionnaires and policies may still refer to the 2021 list, so check which edition a document means and update internal references to the 2025 names.