All insights

What ongoing website security should include

Security care works best when the work, owners, and response process are clear. Here is what to ask of an ongoing website partner.

Concentric metal rings protect a violet glass center.

The practical takeawayAsk for a named owner, an update process, monitored alerts, and a tested recovery path for the website your team depends on.

  1. Review access
  2. Maintain the site
  3. Practice recovery

Website security can become an abstract line on an invoice. A monitoring tool is enabled, updates are mentioned, and everyone hopes the important details are covered. The useful question is what work happens regularly, who is responsible, and what changes when an alert needs attention.

For a business or nonprofit that relies on its website, ongoing security should be an understandable service. You do not need to personally administer every system, but you should know where responsibility sits. This guide outlines a practical scope to discuss with your web partner. The exact work depends on your platform, integrations, and the information the website handles.

Start with the systems around the website

Your website depends on more than the page visitors see. Domain registration, DNS, hosting, the CMS, form delivery, email, and third-party integrations all matter. Build an inventory that identifies the purpose, account owner, renewal contact, and support route for each service.

Include connections that are easy to overlook. An old form endpoint may still receive inquiries. A former contractor may still have hosting access. A campaign microsite may use a separate installation that nobody includes in the main maintenance schedule.

Choose an owner who can keep this map current as work changes. NIST’s small-business cybersecurity guidance identifies asset inventories, appropriate account privileges, updated software, and protected backups as useful foundational practices. An inventory turns those ideas into a list your team can act on.

Give each person the access their work needs

Separate individual accounts from shared administrative access wherever the platform supports it. A content editor usually does not need the same permissions as the person managing hosting or billing. Make account removal part of the handoff when a staff member or vendor leaves.

Use multifactor authentication for accounts that offer it, especially the systems that control other accounts or the domain. Keep recovery methods available to the organization through an approved process. Access should not depend on one person’s personal email account or an undocumented device.

An illustrative quarterly review might compare the CMS and hosting user lists against the people currently doing the work. The useful output is a record of what changed and why. Do the same review after a significant staffing or agency change, rather than waiting for a calendar reminder.

Treat updates as a managed process

Updates need both an owner and a way to verify the site afterward. Decide which changes can happen automatically, which need testing, and how urgent security updates are handled. The appropriate approach can differ between a simple brochure site and a site with complex transaction flows.

For WordPress, the official hardening handbook explains that security involves multiple layers, including keeping software current and maintaining trustworthy backups. A maintenance agreement should translate those principles into concrete work on your particular installation.

After a meaningful update, check the business-critical paths: inquiry forms, account access, donations or checkout where relevant, and the integrations those actions trigger. Record the version or change, the result of the checks, and how to recover if a problem appears. A successful update message alone does not confirm the entire customer journey still works.

Connect monitoring to an actual response

An alert is useful when someone receives it, understands it, and can take the next step. Ask what is monitored, which events trigger review, and who receives notifications. Clarify the difference between checking whether a site responds and investigating an application security concern.

For an illustrative example, a page can load normally while its inquiry form fails to deliver leads. An availability check may stay green. That is why monitoring should be discussed alongside functional checks and the business processes behind the site.

Agree on support hours and escalation arrangements rather than assuming round-the-clock coverage. Keep emergency contacts somewhere the team can reach if the website or a primary account is unavailable. The agreement should describe what the provider handles directly and when specialist incident-response help is needed.

Make the ongoing work visible

A useful security-care report can be brief. It should explain completed updates, access changes, items investigated, recovery checks, and decisions that need your attention. Avoid relying on a single “secure” score to represent the whole website.

  • What changed since the previous review?
  • Which important journeys were checked?
  • Did any alerts require action?
  • Is the recovery process still workable?
  • What needs a business decision or additional scope?

Begin by asking your current provider to walk through these questions using your actual website. If ownership is unclear, make that the first improvement. TripleSkinny can help establish a practical maintenance and security routine, keep the work moving, and give your team a reliable person to call when something needs attention.

Sources & further reading