{"id":15889,"date":"2018-10-15T16:00:38","date_gmt":"2018-10-15T16:00:38","guid":{"rendered":"https:\/\/cloudblogs.microsoft.com\/microsoftsecure\/?p=85981"},"modified":"2018-10-15T16:00:38","modified_gmt":"2018-10-15T16:00:38","slug":"making-it-real-harnessing-data-gravity-to-build-the-next-gen-soc","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/making-it-real-harnessing-data-gravity-to-build-the-next-gen-soc\/","title":{"rendered":"Making it real\u2014harnessing data gravity to build the next gen SOC"},"content":{"rendered":"

This post was coauthored by Diana Kelley<\/a>, Cybersecurity Field CTO, and\u00a0Si\u00e2n John<\/a>,\u00a0EMEA Chief Security Advisor, Cybersecurity Solutions Group.<\/em><\/p>\n

In our first blog<\/a>, Diana and I talked about the concept of data gravity and how it could, conceptually, help organizations take a more \u201ccloud-ready\u201d approach to security operations and monitoring. In this post we address the question: \u201cHow do we make this a reality in the security operations center (SOC) while we are under increased and constant pressure from motivated threat actors?\u201d<\/p>\n

The answer lies in a new approach to monitoring called Security Orchestration, Automation and Response (SOAR), which is founded upon addressing the challenge of connecting and investigating issues across multiple security platforms. SOAR addresses the challenges of evolving security operations beyond the traditional security information and event management (SIEM) model into one that allows correlation across all the data gravity wells. Core to this is being able to take an event from one system (for example an endpoint like a laptop) and in real-time correlate that across different systems\u2014such as a mail hygiene gateway\u2014in order to build evidence and apply context needed for a fast and efficient investigation. This is something that analysts have historically done manually to investigate an issue: look across multiple different evidence points to find the information behind an event to determine if it\u2019s a false positive or if needs further investigation. Historically deciding what incidents need investigation was left to the SIEM model, but as we discussed in the last blog both the difficulties with false positives and the rules of data gravity make this more difficult to achieve.<\/p>\n

Let\u2019s discuss how this can be achieved using Microsoft as an example.<\/p>\n

We have a number of significant areas of data gravity within the technology that Microsoft customers use. These are Office 365, Windows, and Azure, each with a different focus and level of protection, but is what we need bring to together to share insights and events across these technical areas. This is where the Intelligent Security Graph comes into play for us. This is a subset of the Microsoft Graph focused specifically on sharing security information and insights that we see across our infrastructure:<\/p>\n

\"\"<\/p>\n

Each of the areas of security products we have integrated with the graph allow us to share insights across different areas and build orchestration capability, context, and automation across systems without necessarily having to pull them all into one single aggregated log store. Analysis is done, as and when required, often driven by the machine learning and behavioral techniques that help to determine what information is needed.<\/p>\n

The next step is to make this information available to others and why we released the graph security API<\/a>. This is an open and free API that allows customers to interrogate Microsoft data in real-time for alerts and context that the Office 365, Windows, and Azure security systems hold. This allows organizations to integrate alerts into their own SOC or build automated playbooks and investigations built across the platform. This isn\u2019t just about orchestrating across Microsoft. The law of data gravity says that we must integrate with others and many leading security vendors have also integrated into the API to provide information into our platform for integration, and also to allow them to real-time query Microsoft to provide context in their own platforms.<\/p>\n

When insights across multiple data gravity wells can be accessed and correlated in near real-time, the SOC analyst can spend far less time writing SIEM rules and more time tuning orchestration and automation that is focused on improving insight, reducing false positives, and investigating the important information. The capability that SOC vendors should be focusing on is building a real-time investigation platform that enables analysts to investigate security event signal across multiple vendors and investigate in real-time, by respecting the laws of data gravity. Meaningful insights and reducing mean time to identify (MTTI) and mean time to remediate (MTTR) are far better measures of SOC effectiveness than how many events per second (EPS) are processed.<\/p>\n

To make the SOC of tomorrow a reality, the question you ask your security vendors needs to change. Instead of asking \u201cCan you send all your logs into my SIEM?\u201d ask these questions instead:<\/p>\n