Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Identities have become one of the most common ways modern threat actors gain a foothold in the cloud. From stolen credentials to overly permissive roles and privilege escalation, attackers use a range of tactics to exploit identities and use them to launch devastating breaches. Once inside your environment, they can move laterally, exploit resources, or steal sensitive data, leaving security teams scrambling to contain the damage.

Since the Sysdig Threat Research Team (TRT) discovered LLMjacking in May 2024, we have continued to observe new insights into and applications for these attacks. Large language models (LLMs) are rapidly evolving and we are all still learning how best to use them, but in the same vein, attackers continue to evolve and grow their use cases for misuse.

In the early 2000s, one of the hardest choices many of us faced online was selecting our MySpace “Top 8” — the ultimate public display of friendship. Choosing which friends to feature required serious thought, some strategic prioritization, and let’s be honest — risking a few hurt feelings. I wonder if Tom still thinks about the impossible position he created for a generation of young internet users.

In the world of cloud-native applications, microservices and Kubernetes have become the backbone of modern software architecture. The scalability, flexibility, and orchestration capabilities provided by Kubernetes have revolutionized how applications are built and managed. However, like any powerful tool, Kubernetes introduces complexity, and with complexity comes risk — particularly in the form of security vulnerabilities.

One of the primary goals of information security is to protect data, which of course entails protecting the resources that store and provide access to that data. According to the NIST Cybersecurity Framework, organizations need to develop and implement the necessary protections to restrict or mitigate the effect of a possible cybersecurity incident. Security should be integrated right from the source of the cloud architecture design process.

There is nothing more exciting (or nerve-wracking) than sharing something you’ve created with the world. Over 25 years ago, we started working on Wireshark. For us, it has always been more than just a piece of software — it’s how we met, how we began our careers, and how we learned to solve problems that once seemed insurmountable.