<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hooks on WhizMe.ai Tech Blog</title><link>https://www.whizme.ai/tags/hooks/</link><description>Recent content in Hooks on WhizMe.ai Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.whizme.ai/tags/hooks/index.xml" rel="self" type="application/rss+xml"/><item><title>Locking Down Claude Code: A Practical Guide with Simple Examples</title><link>https://www.whizme.ai/blogs/locking-down-claude-code/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.whizme.ai/blogs/locking-down-claude-code/</guid><description>&lt;p>Claude Code can be made much safer, but only if you understand what each control is actually doing.&lt;/p>
&lt;p>A lot of teams get confused because the names sound similar:&lt;/p>
&lt;ul>
&lt;li>&lt;code>CLAUDE.md&lt;/code>&lt;/li>
&lt;li>permissions&lt;/li>
&lt;li>sandboxing&lt;/li>
&lt;li>hooks&lt;/li>
&lt;li>managed settings&lt;/li>
&lt;/ul>
&lt;p>They are &lt;strong>not&lt;/strong> the same thing.&lt;/p>
&lt;p>A simple way to think about them is this:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>CLAUDE.md&lt;/code>&lt;/strong> tells Claude what you want it to do&lt;/li>
&lt;li>&lt;strong>permissions&lt;/strong> decide which tools Claude is allowed to use&lt;/li>
&lt;li>&lt;strong>sandboxing&lt;/strong> limits what Bash can actually do on the machine&lt;/li>
&lt;li>&lt;strong>hooks&lt;/strong> inspect actions at runtime and can allow, deny, or modify them&lt;/li>
&lt;li>&lt;strong>managed settings&lt;/strong> stop users from weakening policy in an enterprise setup&lt;/li>
&lt;/ul>
&lt;p>If you only remember one thing from this article, remember this:&lt;/p></description></item></channel></rss>