Tag: security
Claude inference hooks cannot see a screenshot
Anthropic now lets an Enterprise organisation put its own server in front of every prompt and return allow or deny before the model runs. It is the strongest inline control Claude has shipped. It also never receives raw image bytes, so a screenshot of the document you are trying to stop walks straight through, and the failure mode when your server goes down is a setting somebody has to choose.
The Claude Enterprise admin console has 25 sections and no map
Claude Enterprise puts 25 settings sections behind one nav, grouped into four blocks that do not match how anybody actually governs AI. Here is the whole tree, what each block controls, and the six settings worth opening on your first day as an Owner rather than the twenty-five you will otherwise scroll past.
Why your Claude Microsoft 365 connector is still read only
Anthropic shipped write tools for the Microsoft 365 connector on July 7, 2026, and left them switched off for every organization that had connected before that date. Nothing in the product says so. Here is how to check in ten seconds, the two admin gates in two different consoles, the scope that deserves a second look, and the write path already running in your building that will derail the diagnosis.
An MCP server is unreviewed code with your file system in scope
Treat every MCP server as untrusted code that runs with the access your agent has, because that is what it is. Anthropic docs say the directory lists connectors but does not security-audit them. A registry of approved servers with nothing enforcing it is a memo. The control that binds is a managed allowlist matched by URL or command, never by name.
Your Claude Code deny rules are not a security boundary
Before you hand Claude Code to hundreds of people you add deny rules for .env and credentials and feel locked down. You are not. Those rules govern Claude own tools, not a Python one-liner that opens the same file, and the control that actually holds, the OS sandbox, reads your whole machine by default and fails open when it cannot start. The baseline worth setting is real. Its dangerous gaps are the defaults you never changed.
Blocking the personal Claude account is an identity problem, not a network one
Your CISO trusts the control posture Microsoft gives Copilot. To get Claude to the same bar, do not reach for tenant restrictions: that header only fires on your network, so it is theater the moment a laptop goes off-VPN. The control that holds lives at identity. Enforce SSO, then claim your domain, and know that the claim is a one-way door.
Claude Code behind a TLS-inspecting proxy: configure the tool, not the proxy
Locked-down shops reach for a proxy exception to make Claude Code connect. Wrong move, and it fails anyway. Claude Code does not pin certificates, so it works through full TLS inspection once you teach it to trust your corporate root CA. The fix is a couple of environment variables and an egress allowlist, not a hole in the proxy.
You are at phase zero, and the deck you were sold starts at phase three
Every enterprise AI maturity model starts a rung above where most companies stand and skips the one that holds the rest up: getting the tool safely into people hands. Your team already has Claude. If IT cannot produce the tenant policy, the egress allowlist, the tool allowlist, and the audit log, you are at phase zero, whatever the deck says.
Claude Code enterprise security is a design problem
Most guides to running Claude Code in an enterprise stop at the install. That is the easy ten percent. The real work is the security design around an agentic tool that runs commands and reads files: the audit trail, prompt injection, permission modes, and a managed policy file.
Running your own SOC 2 pen tests with open-source tools
Most companies pay five figures annually for penetration testing they could run themselves. Open-source scanners like Nuclei, testssl.sh, and nmap cover the OWASP Top 10, generate auditor-ready reports, and run monthly on a cron job for zero cost.
SOC 2 vs ISO 27001 for startups and mid-size SaaS
US buyers want SOC 2 from the AICPA. European buyers want ISO 27001. The two frameworks share roughly 80% control overlap, but which one to pursue first depends on where your revenue comes from right now.
What SOC 2 actually is and why most explanations get it wrong
SOC 2 is not a certification. It is an AICPA attestation report issued by a licensed CPA firm expressing an opinion about your controls. Most vendor websites, sales decks, and even compliance platforms get this basic fact wrong, and the confusion costs companies real time and money.
How we replaced our SOC 2 compliance platform with AI and Google Drive
SOC 2 compliance platforms charge thousands annually for what is essentially organization software. We moved to a Git repository, Google Drive for auditor access, and AI for the tedious work. The only cheque we write now goes to our CPA firm for the actual audit.
Claude Code SOC 2 compliance - what your auditor needs to know
Your auditor does not care about Anthropic marketing promises or vendor certifications alone. They need evidence of YOUR controls around Claude Code, data handling documentation, and audit trails that prove your AI coding tool is not creating compliance gaps in your SOC 2 framework. IBM found 97% of AI-breached organizations lacked proper access controls.
RAG security: Why it amplifies your existing posture
RAG systems do not create new security risks - they amplify your existing data security posture. OWASP ranked sensitive data disclosure as the number two LLM risk in 2025. Weak access controls become glaringly obvious when your AI can retrieve everything you forgot you had.