<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>security on Publishing House</title>
    <link>https://publishinghouse.org/tags/security/</link>
    <description>Recent content in security on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WordPress Security Hardening: A Publisher&#39;s Checklist</title>
      <link>https://publishinghouse.org/wordpress-security-hardening-a-publishers-checklist/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/wordpress-security-hardening-a-publishers-checklist/</guid>
      <description>WordPress is the most attacked CMS on the internet not because it is inherently insecure but because it is the most common. Its market share makes it the highest-return target for automated scanning and exploitation. A default WordPress installation is not a hardened one — but hardening it is straightforward, well-documented work that most publishers skip until something goes wrong.
This checklist covers the high-impact measures that materially reduce your attack surface.</description>
    </item>
    
  </channel>
</rss>
