Shedding Light: How OpenGraph enables TaskHound to expose Hidden Attack Paths in AD | SO-CON 26
Source: YouTube · SpecterOps · published Jun 4, 2026 · 41:15
The speaker highlights that misconfigured scheduled tasks are a persistent vulnerability in almost every engagement, with an average of 21 broken or misconfigured tasks found per environment, emphasizing that this issue is never absent in their recent work.
Key Takeaways:
• The presenter opens with a statistic about the high frequency of misconfigured scheduled tasks found during security engagements, noting that it is never zero 0:15.
• The speaker admits to fabricating the specific number "21" initially to make a point, but confirms that misconfigurations are consistently present across different clients 0:38.
• The discussion transitions into a specific case study where the team failed to find any scheduled tasks, marking a rare exception to their usual findings 0:45.
This presentation underscores the critical importance of auditing scheduled tasks as a routine part of security assessments due to their frequent misuse or misconfiguration.
Sources:
Generate CPE Credits
Generate a professional CPE document from this video's transcript.
Estimated credit: 0.5 CPE hours
Estimate uses the video runtime (1 hour ≈ 1 CPE, rounded to the nearest 0.5, minimum 0.5, maximum 2.0). The final amount can be lower after review, never higher.
Topic: Cybersecurity. Commonly maps to: Security and Risk Management, Security Operations. Exact CISSP domains are assigned during generation.
Free account. One generation at a time, with a daily limit.
CPEBuddy is independent and not affiliated with or endorsed by ISC2, ISACA, or any certification body. Exports are formatted for common CPE submissions; acceptance is at your certification body's discretion.
Transcript Preview
First 800 characters of the transcript
Welcome everybody and I also hope you had a great lunch and I know the first talk after the lunch break is always uh a bit weird. So I hope I can uh maybe lighten the mood a bit and keep you awake. So I want to start out with a number actually uh which is 21. that is the average number of broken or misconfigured schedule tasks in uh environments that the team and I encountered over the past few months different engagements and I completely made that number up. Oh, no. No, I'm just kidding. But it sometimes it's a bit more, sometimes it's a bit less. It's a bit less. But the point is it's never zero. Not in a single engagement over the past few months. Uh where I first uh not first but where I really had to dig into the topic was a time where we didn't encounter misconfigured or scheduled t…