Tag: ai-governance
Should AI skills follow the org chart or the process?
AI skills need both. A skill belongs to a role, which looks after it and may change it, and a step in a written process names it, which settles when it is used. Anthropic groups skills into role bundles. Filed by role alone, people hold tools with no order of work, and filed by process alone, nobody looks after them.
Is a consumer Claude plan safe for client data, and is it cheaper than Team?
Claude Max and Ultra run under the Consumer Terms, which carry no data processing addendum, so I keep client personal data on Team or Enterprise. On price, Max costs the same per five-hour session as a Team seat billed monthly. What Ultra buys is a higher ceiling for one heavy Claude Code user.
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.
Claude US-only inference costs 1.1x and that is the cheapest part
The Enterprise console offers one toggle that keeps all model inference in US regions for a 10 per cent surcharge. Underneath it are two independent settings, one of which is a one-way door you set when you create a workspace and can never change. The surcharge is the part everybody reads and the least expensive of the three costs.
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.
One line in your org-wide AI instructions cuts output by 24 percent
Adding an organization-wide instruction block does add tokens to every prompt, and that objection is correct. A controlled 180-call test on Claude Sonnet 5 shows one brevity line cutting output 23.9 percent and returning 14.2x its own cost, while the block carrying it fails to break even uncached.
Why a Claude share link will not open, and what actually works
A shared Claude conversation returns HTTP 200 whether or not you can read it, and the page carries six characters of visible text. Team and Enterprise chats are organization-only by design, attached files never travel with the snapshot, and the one programmatic route is a Compliance API that has no idea what a share link is.
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.
Your locked-down Claude sandbox is a holding pattern, not a destination
Giving everyone Claude inside an isolated VM, no sensitive data allowed, feels like the safe way to start. It is a fine way to start. The trouble is what happens when you leave people there: the leak it was built to stop walks out by copy-paste anyway, the friction recruits the shadow AI you were trying to prevent, and the value never compounds because nothing in an ephemeral box survives the session. A sandbox is a scaffold. Scaffolds come down.
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.
Your AI context layer is only half a brain
An AI context layer feeds every model one governed source of company truth, and DataHub and Atlan will sell you that read half today. The half that notices when a person did not get what they wanted, the re-ask nobody logged, is what turns a knowledge store into a brain.
Your AI has no whoami
Every enterprise AI platform resolves what you can access through SSO and SCIM. None of them load your team instructions from who you are. Claude gives admins one 3,000-character field for everyone. Microsoft Copilot reads your permissions but not your team playbook. Here is the gap and what works today.
The AI committee always arrives second
Companies form an AI committee after employees already use AI daily. University of Melbourne research covering 48,000 workers in 47 countries found 58% use AI at work and 57% hide it. The committee exists to catch up, and that changes who sits on it and what it does first.
How to export your Claude Projects data - three workarounds that actually work
No export-Project-as-package button exists in Claude.ai. Anthropic ships a GDPR-compliance ZIP of conversations as JSON, no API endpoint for Projects, and a closed-as-not-planned GitHub issue for file downloads. Three workarounds work today. One is a local-disk cousin nobody mentions.
SharePoint vs OneDrive for AI - where your files live decides what AI can see
When AI indexes your files, SharePoint and OneDrive expose data very differently. Here is how permission models, governance gaps, and the oversharing problem change everything about where you store documents for AI workflows.
Your employees are generating AI code nobody governs - here is what to build
45% of AI-generated code contains security flaws. Most of it lives on employee laptops with zero scanning, logging, or continuity planning. Here is a three-pillar blueprint that costs a fraction of the reactive support it replaces.
How to standardize on one AI vendor without your team going around you
Harmonic Security analysed 22.4 million AI prompts across enterprises and found 665 distinct tools in use. ChatGPT alone caused 71.2% of data exposures. Standardizing on one vendor is not about picking favorites. It is about making the approved option so good that nobody bothers looking elsewhere.
Your team is producing 500 documents a week with Claude and none of them look like yours
Claude Projects carry no published character limit on instructions. You can paste an entire 80-page brand guide. But most companies have not done this, so every AI-generated document goes out with default formatting and generic voice. The five-layer brand enforcement stack fixes this systematically without slowing anyone down.
Shadow AI is not a policy problem. It is a supply problem.
Banning unauthorized AI tools does not work. BlackFog research shows 60% of employees use unsanctioned AI tools anyway, outside your security perimeter. Companies actually preventing shadow AI are doing it by making approved tools faster to access, not by writing stricter policies nobody reads.
Your AI steering committee needs power, not just opinions
Most AI steering committees fail because they are designed to discuss, not decide. ISO/IEC 42001 requires clear decision-making authority over the AI lifecycle, and IAPP research finds 77% of organizations still building their AI governance. The difference between effective and ineffective committees is not expertise - it is authority.
AI governance that enables instead of restricts
Enterprise AI governance frameworks kill mid-size innovation through compliance theater that takes six months to approve any AI initiative. Here is how to build lightweight, NIST-aligned frameworks that accelerate safe AI adoption instead - starting with three core controls that prevent catastrophic failures while enabling teams to ship AI products weekly, not quarterly.
Claude for financial services - navigating compliance without slowing down
Most financial firms now use AI, but only about 28% formally test or validate its outputs, per a 2025 industry compliance survey. Mid-size firms need AI capabilities but lack compliance budgets. Here is how to use Claude safely within real regulatory constraints, building audit trails and data policies without expensive tools.
System prompts that scale across teams
System prompts are your AI constitution. Agentic AI projects keep getting cancelled over cost, complexity, and risk that trace back to ungoverned prompts. Build hierarchical prompt architectures with version control and tools like MLflow that enable team autonomy while maintaining organizational standards.
The AI governance framework template that enables instead of blocks
Stop choosing between innovation and business risk. Most governance frameworks create bureaucracy that kills progress, and IBM data shows 63 percent of breached organizations lack AI governance policies. Here is a practical template that enables AI teams while managing actual risks.