{"id":130426,"date":"2023-06-13T09:00:00","date_gmt":"2023-06-13T16:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/?p=130426"},"modified":"2024-06-26T08:38:55","modified_gmt":"2024-06-26T15:38:55","slug":"how-microsoft-and-sonrai-integrate-to-eliminate-attack-paths","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2023\/06\/13\/how-microsoft-and-sonrai-integrate-to-eliminate-attack-paths\/","title":{"rendered":"How Microsoft and Sonrai integrate to eliminate attack paths"},"content":{"rendered":"\n
This blog post is part of the Microsoft Intelligent Security Association <\/em>guest blog series<\/em><\/a>. <\/em>Learn more about MISA<\/em><\/a>.<\/em> <\/p>\n\n\n\n Cloud development challenges conventional thinking about risk. A \u201cperimeter\u201d was always the abstraction that security teams could start from\u2014defining their perimeter and exposing the cracks in firewalls and network access. With more and more infrastructure represented as ephemeral code, protecting your perimeter is no longer a matter of software vulnerabilities and network checks. It\u2019s a complex web of interconnected risks that can exacerbate network gaps or workload vulnerabilities.<\/p>\n\n\n\n When it comes to remediating risks, context is always king, and siloed pillars of cloud security\u2014identity, data, platform, and workloads\u2014kill context. Protecting a broad Microsoft Azure footprint means having a deep understanding of how these risks can combine to create unintended access to your company\u2019s sensitive data, and then prioritizing threats based on potential business impact. This means understanding identity, workload, platform configuration, and data security through a single pane of glass providing visibility across the entire digital estate.<\/p>\n\n\n\n Sonrai integrates with Microsoft Sentinel<\/a> and Microsoft Defender for Cloud<\/a> to uncover and remediate sophisticated threats in a timely manner.<\/p>\n\n\n\n Microsoft released Defender for Cloud to protect across hybrid and multicloud environments. Sonrai works with Defender for Cloud\u2019s infrastructure and operational controls for powerful event logging to ingest all information and bring context into one place. Sonrai\u2019s patented analytics evaluate how identity and data risks compound with platform and workload risks to create access to sensitive data within Azure.<\/p>\n\n\n\n To help Azure customers understand the true blast radius of every vulnerability, Sonrai integrates with Microsoft Sentinel to monitor threats across vectors and automate responses by leveraging security orchestration, automation, and response (SOAR) playbooks, and Defender for Cloud to provide visibility across the entire digital estate by identifying possible attack paths and remediating vulnerabilities.<\/p>\n\n\n\n Backed by these insights, an organization can successfully operationalize a risk remediation practice. They are additionally able to enable DevOps and security teams to fully harness the digital transformation and time-to-delivery benefits that Azure can power, without worrying about sacrificing speed for security.<\/p>\n\n\n Secure multicloud and hybrid environments.<\/p>\n\t\t\t\t\t<\/div>\n\n\t\t\t\t\t\t\t\t\t\t\t A consistent research finding is that most cloud data breaches involve a compromised identity\u2014one study cites 81 percent of breaches1<\/sup> involve exploiting an overprivileged identity, while another claims that 74 percent of breaches2<\/sup> surveyed started with privileged credential abuse. It\u2019s clear that the way we use identity now in the cloud\u2014as a de facto \u201cperimeter\u201d and locus of privileges and access\u2014makes it imperative to put identity at the center of any enterprise security strategy.<\/p>\n\n\n\n The behavior and management of non-people identities (think: service principles) are conceptually much different than when we managed a list of users from Microsoft Azure Active Directory<\/a>. The main reason? The majority of identities in a given cloud represent services, devices, and applications\u2014not employees. For example, your cloud may have many identities representing Azure Serverless compute, which may only exist for a few minutes a day, rely on assuming access from a role, and being capable of cross-organization access. The privileges associated with this identity might be in a policy several degrees of separation away through a nested group. Using managed identities and, ideally, the enforcement of the Principle of Least Privilege, is a good place to start. The harder part is the hidden relationships that don\u2019t show in a traditional identity management tool.<\/p>\n\n\n\n Especially as DevOps gets more sophisticated with infrastructure as code (IaC) provisioning, these complex relationships become commonplace. Templatized infrastructure means further nested rights and inheritances through complex relationships.<\/p>\n\n\n\n Continuous monitoring and analytics of identity trust chains become imperative for understanding what privileges any identity truly has. The most important thing is: How do these identities tie back to sensitive data?<\/p>\n\n\n\n Data is the pot of gold at the end of an attacker\u2019s rainbow. In the cloud, identity is the stepping stone attackers can leverage to move laterally and find ways to your data. Exposed data and overprivileged identities are red flags organizations need to look for when considering vulnerabilities and posture misconfigurations. Sonrai Security\u2019s Workload Protection Platform refers to these red flags as \u201cRisk Amplifiers.\u201d In the next section, we\u2019ll address why understanding how threats tie back to identity and data risks matter.<\/p>\n\n\n\n Cloud development has changed how we look at vulnerabilities. Distributed, rapid, and open source-fueled continuous integration and continuous delivery (CI\/CD) pipelines can introduce more vulnerabilities to staging and production environments, lending enterprises to deal with thousands of common vulnerabilities and exposures (CVEs) regularly. If cloud innovation continues at such a rapid pace, and developers leverage public libraries and prioritize speed over security, CVEs will proliferate. The question is: which ones should we care about first?<\/p>\n\n\n\n Traditionally, information about the vulnerability itself would determine its priority for patching. A common vulnerability scoring system score, its age, and known exploits would give you a picture of how likely it was to lead to a breach. But this tells only half the story: the context of the workload that vulnerability is on tells you what the potential blast radius could be, and therefore gives you the true potential impact on the business.<\/p>\n\n\n\n A vulnerability on a deadened workload shouldn\u2019t be prioritized before one with a Service Principal on it that can self-escalate privileges and access sensitive data. This prioritization is critical, otherwise, your security operations center (SOC) team might be chasing alerts that would never impact the business, but meet the traditional definition of a risk. Fixing it will close a ticket, but \u201ctickets closed\u201d is a poor stand-in for real risk reduction.<\/p>\n\n\n\n Let\u2019s piece this story together by examining an example of a typical path that a bad actor might take to access data.<\/p>\n\n\n\n We\u2019ll start with a vulnerability, let\u2019s say one from Microsoft Defender for Cloud\u2019s agentless vulnerability scanner in Microsoft Defender Cloud Security Posture Management<\/a>.<\/p>\n\n\nMicrosoft Defender for Cloud<\/h2>\n\n\t\t\t\t\t
Identity as perimeter, data as prioritizer<\/h2>\n\n\n\n
Vulnerabilities: Which are relevant?<\/h2>\n\n\n\n
Connecting the dots: Analyzing an Azure attack path<\/h2>\n\n\n\n