<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Browsers on wporter.org</title>
    <link>https://wporter.org/categories/browsers/</link>
    <description>Recent content in Browsers on wporter.org</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 13 Jul 2025 17:35:00 +0000</lastBuildDate>
    <atom:link href="https://wporter.org/categories/browsers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hardening and customizing Google Chrome via policy (registry)</title>
      <link>https://wporter.org/hardening-and-customizing-google-chrome-via-policy-registry/</link>
      <pubDate>Sun, 13 Jul 2025 17:35:00 +0000</pubDate>
      <guid>https://wporter.org/hardening-and-customizing-google-chrome-via-policy-registry/</guid>
      <description>&lt;p&gt;Quick one here. Just going to list some policies, discuss setting them, and link to the docs and a script for setting them.&lt;/p&gt;&#xA;&lt;p&gt;We can manage Chrome via MDM (like Intune), Group Policy (if the machine is joined to an Active Directory domain and you&amp;rsquo;ve imported the relevant ADMX), via &amp;lsquo;preferences&amp;rsquo; JSON config files (Mac or Linux), or via the Windows registry (my preferred option since it applies to any Windows PC, regardless of management infrastructure, and is easy to script).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
