10 ms·
> while leveraging a mixture of golang for userspace and eBPF for kernelspace This severely limits your market share. Most on-Prem customers are still using pr
by alephnerd 3y ago
> while leveraging a mixture of golang for userspace and eBPF for kernelspace
This severely limits your market share. Most on-Prem customers are still using pre 5.0 Linux kernels, and most cloud first customers are already using Lacework, Aqua, Orca, or Wiz for cloud based asset inventory, monitoring, and even enforcement. Plus SentinelOne and other existing security companies are entering the market (not necessarily a bad thing, but would be difficult to compete without a compelling vision and GTM).
In my experience, the asset inventory problem is mostly seen in large Hybrid environments where asset ownership is split across multiple teams (a CMDB team, cloud platform team, application team, security team, networking team). This along with an SBOM story is very hot right now, but you will need to find a way to differentiate yourself from the list of competitors above, along with the hesitancy to manage yet another agent.
The bigger issue is that while this does sound like a cool feature, it would be a massive lift to make it defensible against companies with an existing Rolodex and also to manage the sales motion.
Also, customers hate installing and managing agents.
- cookiengineer 3y agoCurrently we have a map of discovered nodes inside the network, and an auto-install and auto-penetrate feature, which is meant for batch installing a lot of nodes with the agent. The agent itself is also able to spread itself to different architectures and operating systems once a single system is installed, depending on the selected aggressiveness after the discovery phase for the surrounding network. There's also a prototype that's trying to use a bunch of RCEs to "conquer back" lost nodes, and to reinstall the tholian guard on those systems even when the hacker got (temporary) administrative rights and locked the "old agent" out or managed to delete it. From a legal standpoint this has to be separate product, where companies and their assets/systems/networks have to be manually vetted before they're able to use that feature, but I think you know where I'm getting at with the idea.
- alephnerd 3y agoDon't get me wrong. Your architecture is solid, but managing agents becomes a very political issue internally due to conflicting responsibilities between teams