<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>TrueCMS Drupal insights</title>
    <link>https://truecms.au/insights/</link>
    <description>Drupal insights and technical guides from TrueCMS.</description>
    <language>en-au</language>
    <atom:link href="https://truecms.au/drupal-planet.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is actually running on your Drupal websites?</title>
      <link>https://truecms.au/insights/what-is-running-on-your-drupal-websites/</link>
      <guid isPermaLink="true">https://truecms.au/insights/what-is-running-on-your-drupal-websites/</guid>
      <pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ivan Grynenko</dc:creator>
      <description>&lt;p&gt;&lt;img src=&quot;https://truecms.au/images/insights/what-is-running-on-your-drupal-websites.webp&quot; alt=&quot;Diagram connecting a UAT check to production sites and showing fresh inventory, pending assessment and missing data.&quot; /&gt;&lt;/p&gt;&lt;p&gt;A successful UAT check shows what was tested in that environment; it does not prove what production reports after a deployment or rollback. This article explains how recurring production inventory and assessment can support release assurance across a Drupal estate, and why teams should distinguish inventory freshness, assessment coverage and deployment evidence. It describes the capabilities and limitations of TrueCMS’s Sentinel Connector product, including why reporting does not replace functional testing or independently prove every file on a server. Missing or stale observations also need attention: they cannot establish the current state of a site.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GovCMS PaaS security patching: how to meet the 48-hour Essential Eight timeframe</title>
      <link>https://truecms.au/insights/govcms-paas-48-hour-patching/</link>
      <guid isPermaLink="true">https://truecms.au/insights/govcms-paas-48-hour-patching/</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ivan Grynenko</dc:creator>
      <description>&lt;p&gt;&lt;img src=&quot;https://truecms.au/images/insights/govcms-paas-48-hour-patching.webp&quot; alt=&quot;Illustration of Drupal updates moving through a timed security pipeline towards a verified shield.&quot; /&gt;&lt;/p&gt;&lt;p&gt;On GovCMS PaaS, the agency is responsible for Drupal application security updates. Meeting an applicable 48-hour patching timeframe depends on prepared testing, a working release pipeline and evidence of the production outcome. This practical runbook covers triage, vendor mitigations, controlled releases, testing and production verification. It also explains how to distinguish Drupal risk labels and operational recommendations from the applicable Essential Eight controls, and what evidence to retain when reporting a completed update or an exception. It recommends confirming the interpretation with an agency security adviser and retaining release records for each affected site.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>