{"id":29307,"date":"2025-07-09T00:16:08","date_gmt":"2025-07-08T22:16:08","guid":{"rendered":"https:\/\/tremhost.com\/blog\/?p=29307"},"modified":"2026-11-05T18:03:34","modified_gmt":"2026-11-05T16:03:34","slug":"anatomy-of-a-data-breach","status":"publish","type":"post","link":"https:\/\/tremhost.com\/blog\/anatomy-of-a-data-breach\/","title":{"rendered":"Anatomy of a Data Breach: How It Happens and What It Costs"},"content":{"rendered":"<p>A data breach usually unfolds in stages: an attacker gets in through a phishing email, stolen password, unpatched software or misconfigured service, stays hidden, moves to more valuable systems, and then steals or encrypts data. The cost comes from detecting and containing it, notifying people, responding afterwards and losing business. IBM&#8217;s 2025 Cost of a Data Breach report puts the global average at USD 4.44 million, and most of the steps that prevent a breach are affordable for a small business.<\/p>\n<h2>What the research says about cost<\/h2>\n<p>IBM publishes an annual study of breach costs. Its 2025 report found that average global costs dropped to USD 4.44 million, down 9% from USD 4.88 million the year before, and that organisations took a mean of 241 days to identify and contain a breach (<a href=\"https:\/\/www.ibm.com\/think\/x-force\/2025-cost-of-a-data-breach-navigating-ai\" rel=\"nofollow noopener\" target=\"_blank\">IBM, 2025<\/a>). IBM&#8217;s 2026 report page states that the global average has since reached USD 4.99 million (<a href=\"https:\/\/www.ibm.com\/reports\/data-breach\" rel=\"nofollow noopener\" target=\"_blank\">IBM, 2026<\/a>).<\/p>\n<p>These are averages across organisations of many sizes, mostly large ones. A small business will usually face smaller absolute figures, but the impact relative to its revenue can be much greater.<\/p>\n<h2>The stages of a breach<\/h2>\n<h3>1. Reconnaissance<\/h3>\n<p>Attackers look for an easy way in: staff email addresses on your website, an old WordPress plugin, an exposed remote desktop port or a login page without rate limiting. Much of this is automated and constant.<\/p>\n<h3>2. Initial access<\/h3>\n<p>Common entry points include:<\/p>\n<ul>\n<li><strong>Phishing:<\/strong> an email that tricks someone into entering a password or opening a malicious file.<\/li>\n<li><strong>Stolen or reused credentials:<\/strong> a password leaked from another service and reused for email or the website admin.<\/li>\n<li><strong>Unpatched software:<\/strong> a known vulnerability in a plugin, theme, control panel or server.<\/li>\n<li><strong>Misconfiguration:<\/strong> a public storage bucket, default password or database open to the internet.<\/li>\n<\/ul>\n<h3>3. Persistence and privilege escalation<\/h3>\n<p>Once inside, the attacker installs a backdoor, creates a hidden admin account or adds mail forwarding rules so access survives a password change. They then look for higher privileges.<\/p>\n<h3>4. Lateral movement<\/h3>\n<p>From the first foothold they move to other systems: from one mailbox to the finance mailbox, or from one website to the server and its backups.<\/p>\n<h3>5. Theft, fraud or encryption<\/h3>\n<p>The goal might be customer data, payment redirection through a fake invoice, injected spam pages that damage your search rankings, or ransomware that encrypts files and demands payment.<\/p>\n<h3>6. Discovery<\/h3>\n<p>Many breaches are found by someone outside: a customer reporting strange emails, Google flagging the site, or a bank querying a payment.<\/p>\n<h2>An illustrative example<\/h2>\n<p>This is a hypothetical sequence, not a real case, but it follows a common pattern. A bookkeeper receives an email that looks like a shared-document notice and enters her email password on a fake login page. The attacker logs in, adds a rule that forwards any message containing &#8220;invoice&#8221; to an outside address, and waits. Weeks later, they reply to a genuine supplier thread with new bank details. The business pays the fraudulent account, and the breach is discovered only when the real supplier chases payment. Two-factor authentication, a check on forwarding rules and a phone call to confirm changed bank details would each have stopped it.<\/p>\n<h2>Where the cost comes from<\/h2>\n<ul>\n<li><strong>Detection and escalation:<\/strong> investigating what happened and how far it spread.<\/li>\n<li><strong>Notification:<\/strong> informing affected people and, where the law requires, regulators.<\/li>\n<li><strong>Response:<\/strong> cleaning systems, resetting credentials, restoring data, legal and communication costs.<\/li>\n<li><strong>Lost business:<\/strong> downtime, lost customers and reputational damage.<\/li>\n<\/ul>\n<p>For a small business, the largest costs are often lost trading days, a blacklisted domain and staff time.<\/p>\n<h2>How to break the chain<\/h2>\n<p>Each stage is a chance to stop an attack. The most effective controls for a small business are:<\/p>\n<ol>\n<li><strong>Two-factor authentication<\/strong> on email, hosting, domain and banking accounts.<\/li>\n<li><strong>Unique passwords<\/strong> stored in a password manager.<\/li>\n<li><strong>Prompt patching<\/strong> of websites, plugins, servers and laptops.<\/li>\n<li><strong>Email security<\/strong> that filters phishing and checks SPF, DKIM and DMARC.<\/li>\n<li><strong>A web application firewall<\/strong> in front of your website.<\/li>\n<li><strong>Endpoint protection<\/strong> on staff devices.<\/li>\n<li><strong>Backups<\/strong> kept off the main server, with earlier versions, and tested restores.<\/li>\n<li><strong>Least privilege:<\/strong> staff get only the access they need.<\/li>\n<li><strong>Logging and alerts<\/strong> so unusual activity is noticed quickly.<\/li>\n<li><strong>An incident plan<\/strong> that says who to call and what to do first.<\/li>\n<\/ol>\n<h2>What to do in the first hours<\/h2>\n<ol>\n<li>Do not wipe anything yet; evidence helps you understand what happened.<\/li>\n<li>Change passwords from a clean device and turn on two-factor authentication.<\/li>\n<li>Check email forwarding rules and admin accounts for anything you did not create.<\/li>\n<li>Take affected systems offline or restrict access if data is still leaking.<\/li>\n<li>Contact your host or security provider.<\/li>\n<li>Check your notification obligations under the data protection law that applies to you, such as Zimbabwe&#8217;s Cyber and Data Protection Act.<\/li>\n<\/ol>\n<h2>How Tremhost can help<\/h2>\n<p>If your website is hacked, <a href=\"https:\/\/tremhost.com\/armorsos\">Armor SOS<\/a> provides free same-day triage on working days, then quotes the cleanup. To prevent attacks, Tremhost Armor puts websites behind Cloudflare with firewall rules set and monitored by Tremhost, from $9 a month for Armor Guard, and Armor Mail catches phishing and fake invoices from $12 a month for 10 mailboxes. Tremhost also supplies <a href=\"https:\/\/tremhost.com\/eset-security\">ESET endpoint security<\/a> for laptops and servers. Support is available Monday to Friday, 08:00 to 17:00 CAT.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Are small businesses really targeted?<\/h3>\n<p>Yes. Most attacks are automated and look for any weakness, regardless of company size.<\/p>\n<h3>Is a backup enough protection?<\/h3>\n<p>Backups help you recover, but they do not stop data being stolen. Combine them with prevention.<\/p>\n<h3>Can a firewall stop phishing?<\/h3>\n<p>No. A web firewall protects your website; phishing needs email security and staff awareness.<\/p>\n<h3>How quickly should we act?<\/h3>\n<p>Immediately. The longer an attacker stays, the more they can reach.<\/p>\n<h2>Next step<\/h2>\n<p>For one team covering websites, email, servers and laptops, see <a href=\"https:\/\/tremhost.com\/managedsecurity\">Tremhost managed security<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How a data breach unfolds from first access to discovery, where the cost comes from, and the practical steps that stop each stage.<\/p>\n","protected":false},"author":979,"featured_media":29305,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[212,208],"tags":[],"class_list":["post-29307","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-reports","category-whitepapers"],"_links":{"self":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/29307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/users\/979"}],"replies":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/comments?post=29307"}],"version-history":[{"count":4,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/29307\/revisions"}],"predecessor-version":[{"id":81157,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/29307\/revisions\/81157"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media\/29305"}],"wp:attachment":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media?parent=29307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/categories?post=29307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/tags?post=29307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}