Click any tag below to further narrow down your results
Links
Data lakehouses combine low-cost, flexible storage with warehouse-style governance to power enterprise AI. Companies like DocuSign and Lemongrass use them to feed and train AI agents, but impose strict security reviews, access controls and audit trails. Vendors are adding vector indexing, MCP connectivity and semantic layers to ensure agents grasp business context and operate safely.
- Lakehouses now bolt on vector indexing and MCP connectivity so AI agents can directly query and be trained on enterprise data, with Gartner citing 65% client adoption.
- DocuSign restricts agent access to low-risk data (product specs, web content) while locking down customer records, running every dataset through ingestion and egress security reviews.
- Lemongrass is ditching its four-year-old custom-governed AWS S3 setup for a standard lakehouse, drawn by native Claude integration and zero egress fees when data and models share a cloud.
- Autonomous agents pulling data on their own (vs. per-use-case RAG permissions) demand new audit trails, role-based access and semantic controls to avoid runaway costs and compliance risk.
A Jamf survey shows more than 20% of organizations running macOS networks have lost money or been breached due to AI tool use, and about 60% expect future incidents. Shadow AI, agentic AI, vendor sprawl and usage-based billing are creating governance blind spots. Jamf urges early governance measures: regular audits, strict data-access policies and use of built-in tools.
- Over 20% of orgs running macOS networks have lost money or been breached due to AI tool use, and ~60% expect an incident soon
- Shadow AI (unapproved employee tools) is the top governance blind spot, compounded by agentic AI permission risks, vendor sprawl, and surprise usage-based billing
- Despite these risks, governance ranks only third in priority behind automating IT tasks and boosting productivity, with security improvements fifth
- Jamf recommends regular audits, strict data-access policies, early governance integration, and using built-in tools to manage risk
This article points to a Notion guide showing how collapsing 300+ SaaS apps into one workspace cuts risk and simplifies audits. It highlights Toyota, OpenAI and Ramp using a single identity layer, permission model and unified audit logs.
- Companies use an average of 305 SaaS products, each adding its own login and audit surface
- Toyota, OpenAI, and Ramp each consolidated workflows into a single workspace and report faster reviews and fewer rogue accounts
- The pitch centers on one identity layer, one configurable permission model, and one unified audit log
- It's a promotional Notion guide (sponsored content) rather than independent reporting