Detection Lead @ Mandiant Managed Defense / Former IR Consultant @mandiant. Tier 3 Hipster; I came in like a #WrectorBall

San Francisco, CA
Joined July 2012
Great cross team collaboration across Google Cloud to get this service off the ground. Let's find some evil!
Just announced in preview: Mandiant Hunt for Chronicle Security Operations! This new service is tailored to organizations with existing security programs who want a threat hunting capability to discover new threats that may be missed by product detection. cloud.google.com/blog/produc…
1
12
1,442
I don't feel like this is the right question. Threat hunting is a function of detection engineering, where detections are being tested and matched against customer telemetry. If not matches, no additional work. The question we should be asking is what is the service hunting for?
If you were procuring managed threat hunting services from a major security vendor, how many hours per week do you expect a threat hunter is threat hunting in your environment?
33%11+
33%5-10
21%2-4
13%An hour or less
959 votes • Final results
2
13
2,972
I couldn't be prouder of my team for the work they did to implement auto containment at scale in Managed Defense. Auto containment stops impactful threats in their tracks. Jon's tweet alludes to the challenge that this entails. Here's a🧵on how we did it, and it's impact⬇️
How many folks perform auto remediation actions on alert creation? E.g, an EDR alert is created with “Critical” severity; when any “Critical” sev EDR alert is created, auto contain the host(s). If alert is marked as “fp/benign” auto remove containment. If else, keep contained.
28%Nope. Hard pass.
28%For a small % of alerts.
6%For most/all alerts.
38%Show me the results.
361 votes • Final results
1
10
2
44
15,273
I don't think it's unreasonable to say that auto containment protects networks from ransomware deployment. There are so many wins in auto containment, ranging from solid application of theory (funnel) to providing the analyst everything they need to know to respond quickly, to
1
2
505
straight up stop threat in its tracks. This work is built on the A+ efforts of teammates like @tommysec and @PootSoHard and many more to maintain and improve the entire system. It turns out in Security Operations, Whack-A-Mole can work very well!
1
7
514
Question for Threat Intelligence Analysts, and SOC alike... would you consider Detection Rules Threat Intel? Curious on the perspective of consumers of DE content whether or not Detection Rules should be considered Threat Intelligence or not.
29%As SOC, yes
38%As CTI, yes
17%As SOC, no
17%As CTI, no
24 votes • Final results
1
1
465
Strong agreement here. Detection Engineering is an exercise in labeling and classifying security relevant data. FP reduction is critically important in reducing alert fatigue, but the opportunity to tune comes directly from SOC dispositions. It's the best feedback loop you have
This Post is from an account that no longer exists. Learn more
3
19
1,573
I don't think ASO is about replacing humans and being fully automated. It's about leveling up analysts to become analyst/engineer hybrids. The industry talks all day about the talent shortage, and it's not getting better. ASO is an answer to that. It provides a blueprint for 1/2
2
1
6
leveling up your SOC to think about threats in terms of how you can automate them away so that your analysis is spent on the most impactful and novel threats. Automation buys the analyst time. ASO is just putting the power of buying time in the hands of the practitioner. 2/2
7
If you're in the Detection Engineering space, come watch @FryGuy2600 and I geek out on all things DE. We have the following planned: 1️⃣ Establish what DE is and isn't 2️⃣ Details on the DE process from a practitioners perspective 3️⃣ DE Maturity model 4️⃣ Measuring success 🎯🎯🎯
Attending #mWISE? Catch our CTO Fred Frey (@FryGuy2600) and @Mandiant's Andrew Rector (@DetectorRector) for their talk 10/19 at 3:15 about #detectionengineering and leveraging tech + teams in a repeatable process, driving robust, resilient, and efficient detection development.
3
2
21
For some context on this poll, this is a fun conversation we've been having internally. I've landed on both, for the following reasons: 1️⃣ Vendors/MSSP have constraints on how they can craft their logic. High efficacy, low FP. 2️⃣ Vendors/MSSP have competing opp queues.
Detection Engineers, is DE Ops only for Vendors/MSSPs/MDRs or should it be something that corporations should pursue too? Curious on your thoughts!
9%Vendors & Managed Service
10%Corporations
80%Both
213 votes • Final results
1
4
Meaning, you may ask for detection coverage on a thing, but it may take a while, or may not be feasible at scale. 3️⃣Bespokeness - a bit related to the other points, but generally, you know your network better than anyone else. Meaning, you can craft tailored escalation logic
2
Detection Engineers, is DE Ops only for Vendors/MSSPs/MDRs or should it be something that corporations should pursue too? Curious on your thoughts!
9%Vendors & Managed Service
10%Corporations
80%Both
213 votes • Final results
10
3
2
5