Matt Coppinger (@Mcopping) header
Matt Coppinger (@Mcopping) profile picture

CTO (EMEA), @Omnissa. Opinions are my own.

London
Joined December 2009
Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)Photo by Matt Coppinger (@Mcopping)
Omnissa earned the highest scores in all four Use Cases in the 2026 Gartner® Critical Capabilities for Endpoint Management Tools, including a near perfect score for Autonomous Endpoint Management. omnissa.com/insights/blog/na… sprou.tt/16HmaEEdZRl
1
1
80
Matt Coppinger retweeted
I think the speed of attacks and the lower cost will produce some of the desired effect. A lot more collaboration between security and IT, Openness to agentic remediation, willingness to share data. Seeing that live in large F100 companies in last few months. The survival instinct is very powerful.
When you figure out why “just patch” is shitty advice to give to any significant sized company you’ll also know why AI will benefit attackers far more than defenders. In bigger orgs the problem is not usually a lack of tech, or models, or skills on the security team. It’s that there is a level of organizational friction at every company, like a friction coefficient, that stops security orgs from being able to do many things they want. We’ve needed asset management for decades. We’ve needed mappings between code and apps and servers and dev teams and developers forever. Very few have these. The tech exists. The problem is the org is not set up to build and maintain these types of systems continuously. The company’s structure itself, built around opaque silos, and divergent goals, and insanely lossy and inefficient communication across the company, it all creates a very high friction coefficient for basically any fast improvements. The way to fix security is to lower this friction coefficient inside companies. It sucks to hear, but we’re at the point of security’s biggest issue being the company itself. The org structure. The old way of managing teams and goals and work. An AI-native org is the only way to get organizational friction down to a level that can compete with these new attacks and attackers. The bad news is this is big. And it’ll be difficult for a lot of people to adjust to. And a lot of people currently working there won’t be needed in the new model. The good news is many still will, and even more could be needed once the efficiency of the new organization kicks in. This isn’t just going to help addition; it’ll help the entire business move faster. Going into 2027, I believe this model is about to move from ideal and experimental to … essential. Both for surviving cyber-wise, and as a company facing increased and up-leveled competition.
1
3
555
Matt Coppinger retweeted
Meet Mistral Large 4, aka Le Chonk. • 1T parameters, natively multimodal. 49B active. It is the best open weights model from US or Europe on aggregated benchmarks. • State-of-the-art on critical workloads, including cyber defense, manufacturing and finance and it surpasses closed frontier models on visual grounding. • Forged in Europe end-to-end and is deployable from Europe via our own Mistral Cloud infrastructure. • Available to all via API today. Working with cybersecurity partners privately. Open weights release end of October.
🤖 Made with AI
2,029
4,551
2,814
40,571
5,777,852
Matt Coppinger retweeted
It is. Yesterday @Apple announced that agents could/are mis-using full disk access permissions on Mac. This requires device admins to be thoughtful about granular access and for vendors to update the permissions structure for agents. It could get complicated if a user has multiple agents some more trustworthy than the others. Also the behavior of agents will change depending on user input and the prompt, so the environment will be a lot more dynamic and the policy and the guardrails need to follow. Article from Apple here developer.apple.com/news/?id…
"The era of agentic endpoints is here." 💡 Omnissa CEO @theamitaks explains why the endpoint, the one place fully in your control, is becoming the last mile of enterprise AI security. Watch and read his full take. bit.ly/4hAMZd5
2
20
1
50
1,539
Matt Coppinger retweeted
“Elara is the unified authority layer for AI governance and high impact actions. It’s designed to bring context, trust, and control to the agentic enterprise.”
1
4
129
Friends don’t let friends run agents on their laptops. 1. Close your laptop, your agent is asleep 2. Agents are getting erm more agentic, who knows what they do with your data or your laptop. Remember OpenClaw? 3. Despite laptop security, you don’t want your dev env left on them. Fact is, businesses should be deploying developer desktops and agent desktops/containers using Omnissa Horizon. Horizon is the most secure way to enable agentic engineering. Agents run 24/7 on desktops that never sleep. Only pixels land on your laptop, your code and data is safe in the datacenter. VMs can be strictly controlled to prevent agents running amok. OS can be locked down by Omnissa Workspace ONE UEM for specific agent use case.
2
103
Registration is live for Omnissa ONE EMEA! This event is all about sharing ideas, learning from peers, and exploring what's next for digital work. Looking forward to the conversations. Check it out: 👉 omnissa.one/emea?utm_source=…
47
AI is changing enterprise IT—from reactive support to autonomous workspaces. Here’s how AI-driven automation is reshaping IT operations and employee experience: 👉 omnissa.com/insights/blog/ai…
33
Programming, in one word: abstraction. 1945 - ENIAC. You arranged the bits yourself. 30 tons, 18,000 vacuum tubes, 3,000 switches, patch cables. Early 1950s - Assembly. ADD, MOV, JMP. Still one instruction per machine instruction, but readable. 1957 - FORTRAN on the IBM 704. You wrote algebra. The compiler arranged the bits. 1972 - C on the PDP-11. Same source, different machines. Software escapes the hardware. 1974 - SQL. You described the result. The database planned the steps. 1995 - JavaScript. Ten days of work becomes the language of the web. Mid-90s - IDEs. The write-compile-debug loop shrinks from minutes to seconds. 2022 - Chat-to-code. You describe intent in English. A model writes the code. 2026 - Agentic coding. You direct the agent. The agent writes the code that the compiler turns into bits. Every leap moved the human one layer further from the machine. Every leap was dismissed as a toy by the people doing it the old way. The layer they’re standing on was once that toy.
1
64
Matt Coppinger retweeted
🚨 WARNING: The self-spreading “Mini Shai-Hulud” worm compromised npm & PyPI packages tied to TanStack, Mistral AI, Guardrails AI, OpenSearch & more. The attack used GitHub OIDC token hijacking and cache poisoning to spread credential-stealing malware across 42 TanStack packages and 84 versions. Check your dependencies immediately → thehackernews.com/2026/05/mi…
27
193
25
596
97,970
Today @WeAreOmnissa unveiled how orgs introduce autonomy and AI into IT…
1
37
Start with having a platform that has up to date, correlated, accessible data > enables built in automation > enables powerful AI driven capabilities…
1
19