Q1. What are some of the biggest challenges facing SOCs these days? Why has a big data analytics capability become such a key requirement?
Today, even mid-sized organizations may generate petabytes of security telemetry. Most security operations teams, however, are not skilled in managing big data and the underlying hyperscale infrastructure required to keep up with these volumes. On top of this, budgets have largely shifted from capex to opex which means budgets won't be spent on more hardware to support the ever-growing security telemetry.
CISOs want their security operations staff to perform security operations, not infrastructure management. This has boosted the case for using SaaS-based security analytics with unlimited data storage. But here is the trick: unlimited scale of SaaS-based analytics should not mean unlimited rise in costs. Because enterprises need to vastly scale their security data and perform security analytics on it, we predict that the use of cloud-based security technology will grow dramatically for the next couple of years.
Q2. What are some of the key requirements for threat hunting from a technology and a process standpoint? What do you need to do to be successful at it?
Effective threat hunting is supported by having the right technology and processes in place - but it truly relies on the right people. From a technology perspective, you need to be able to collect and store as much security telemetry as possible - such as endpoint, network and log data - all in one place. By having this data collected - but also enriched and cross-correlated, threat hunters can discover and investigate threats that have been hiding over long periods of time.
Threat intelligence is also central for threat hunting as it often—but not always—provides the initial thread for the analyst to pull. Also, threat intelligence helps understand the impact of a potential threat on your organization by associating the activity observed with the threat actors type.
From a process standpoint, it's critical to have incident response processes in place so that you can escalate any threats discovered during threat hunting. The first step is to review the activity and a system deemed suspicious during the hunt. For this, you need to check the context data that was added to enrich the alerts such as system name, system users, running processes, and threat intelligence feeds. From there, you can look at the history of similar suspicious events in this system and in other systems, focusing on the nature of the uncovered suspicious activity.
Your incident response process should include identifying your compromised systems, as well as the systems that have connected to and from them, and reviewing activities on those systems to find further affected resources (hunting pivot). Lastly, security teams need to remediate all affected systems at the same time to avoid an attacker persisting in the environment. Note however that cutting off attacker access before you are confident that you uncovered the true extent of a compromise is a mistake as it tips the attacker that you are onto them.
Q3. What does Chronicle Security plan on highlighting at the Black Hat Asia 2020 virtual event this year? What can organizations expect to hear from Chronicle?
This year, we're excited to talk about the release of Chronicle Detect, a threat detection solution built on the power of Google's infrastructure to help enterprises identify threats at unprecedented speed and scale.
2020 has introduced complex challenges for enterprise IT environments. Data volumes have grown, attacker techniques have become complex yet more subtle, and existing detection and analytics tools struggle to keep up.
Chronicle Detect brings modern threat detection to enterprises with the next generation of our rules engine that operates at the speed of search, a widely-used language designed specifically for describing threat behaviors, and a regular stream of new rules and indicators, built by our research team.
With Chronicle Detect, you can use advanced rules out-of-the-box, build your own, or migrate rules over from legacy tools. The rules engine incorporates one of the most flexible and widely-used detection languages in the world, YARA, which makes it easy to build detections for tactics and techniques found in the commonly used MITRE ATT&CK security framework. YARA-L, a language for describing threat behaviors, is the foundation of the Chronicle Detect rules engine. Many organizations are also integrating Sigma-based rules that work across systems, or converting their legacy rules to Sigma for portability. Chronicle Detect includes a Sigma-YARA converter so that customers can port their rules to and from our platform.
Chronicle customers can also take advantage of detection rules and threat indicators from Uppercase, Chronicle's dedicated threat research team. Uppercase researchers leverage a variety of novel tools, techniques, and data sources to provide Chronicle customers with indicators spanning the latest crimeware, APTs, and unwanted malicious programs. The Uppercase-provided IOCs—such as high-risk IPs, hashes, domains, registry keys—are analyzed against all security telemetry in your Chronicle system, and let you know right away when high-risk threat indicators are present in your environment.
Since joining Google Cloud over a year ago, the Chronicle team has been innovating on our investigation and hunting platform to bring a new set of capabilities to the security market—and we won't stop here. Chronicle has also added new global availability and data localization options, including data center support for all capabilities in Europe and the Asia Pacific region.