Kris McConkey

On Day 2 of CYBERUK, the NCSC and 15 international partners have issued new guidance to help organisations better defend against activity originating from China-linked covert networks. 🌍 🚨 Find out more⬇️ ncsc.gov.uk/news/defending…

Threat Actor: Cluade, compromise this company, be stealthy Claude:

Attack surface.... attack surface everywhere

🚨 The LABScon 2026 Call for Papers is officially OPEN! 🗓️ Deadline to submit: June 19, 2026 🔗 labscon.io <- find the button here

Excited to support @pivot_con again! This year we're hosting a workshop on hunting phishing pages & pivoting across infrastructure. If you're attending, come find us - we'd love to catch up with familiar faces and hear your stories! urlscan.io/blog/2026/04/1…

There is no easy 'just do' in response to the surfacing of latent vulnerability in technology. Vendors must make the investment to address, test and then release. Customers then need to patch. There is no magic - just a sequence of events which now need to take place..

📣#PIVOTcon26 Agenda is here 🤟 We are thrilled to announce the lineup for this year's speaker lineup. 2⃣days and 19 talks from leading #ThreatResearch experts. The agenda link is in the first comment👇, and the talks and speakers are in the thread.🧵 #CTI #ThreatResearch 1/15

Exploitation of Cisco Catalyst SD-WAN Agencies strongly encourage immediate investigation of potential compromise of Cisco Catalyst SD-WAN, and full updating and hardening. ncsc.gov.uk/news/exploitat…

There’s no need to suffer through the rough patch of indeterministic Claude Code behaviors. Here’s my config to get you started w proper planning, implementation, and review, phased development, decision point documentation, git worktrees, and consensus deep research implemented w deterministic hooks. It’s a WIP. Hope it helps! github.com/juanandresgs/c…

I agree, and that’s what I bet my life on at @knosticai. Prevent your coding agents from deleting your computer/code, detect attacks, find agents, and get an inventory of MCP, extensions, rules, etc.

Nice. @Jhaddix is a legend. He just published a treasure trove of context to feed your agents to help them produce more secure code. github.com/Arcanum-Sec/se…

Playing strategy games? You can code. Coding? Manage your code in a strategy game setup. That's the trend from last week. I wonder what will happen next week? Visualizing agent orchestration is amazing, and will go places. These two mockups are from @thekitze

Today @NCSC supported by international partners released guidance on Secure connectivity principles for operational technology (OT) - go forth and secure.. Blog: ncsc.gov.uk/blog-post/desi… Guidance: ncsc.gov.uk/collection/ope… #OT #CyberSecurity

Having responded to probably hundreds of incidents at this point, from ransomware to APT's, in my experience, the lack of knowledge on how to adequately secure Entra applications and service principals continues to be the biggest knowledge gap most defending teams have. You should be able to securely configure apps, detect compromise of apps and understand how to investigate compromise of apps. It seems overwhelming at first, but it isn't. Get started like this Secure them: •Use managed identities where possible - negates the need for credential handling •Limit privilege - reduce both the permissions granted and add additional API specific restrictions (i.e don't grant read/write all to all SharePoint sites, just the ones an application needs to access). This includes pushing back on vendors or internal teams that request privilege not required •High privileged applications should have no direct owners - lower privileged users can be granted direct ownership of an app, don't do this, govern the ability to manage applications via Entra ID roles •Configure credential restrictions such as requiring shorter lived secrets or enforcing use of certificates •Remove unused apps and service principals, this can prevent existing high privileged apps being leveraged and reduces your supply chain compromise footprint for multitenant apps •Monitor risk events for service principals like you would users Detect compromise of them: •Alert on application creation or application credential creation - may be noisy in large environments, but a good starting point •Alert on credentials being added to service principals - credentials generally live on the application object, service principal credential creation should be rare •Alert on permission consent - this can detect not only malicious activity but permission creep •Alert on anomalous resource access - does your app usually access only Azure Storage, and suddenly it accesses Microsoft Graph? - this may indicate a compromised credential •Alert on anomalous ASN or location access - does your app usually access only from a specific ASN or country, and suddenly that changes? - this may indicate a compromised credential Many of these are covered by Defender for Cloud Apps and other tools out of the box, but it is worth ensuring you are covered down and what they actually mean. Investigate compromise of them: Know how to query the following logs and understand the events surfaced •Entra ID sign in data - filter on service principal sign in events via the Entra portal or Kusto in the Defender XDR portal •Entra ID audit logs - filter on events related to the service principal via the Entra portal or Kusto in the Defender XDR portal. Service principals can be used to further establish persistence, such as creation of users or additional service principals, rinse and repeat for any malicious additions to your environment •Microsoft Graph - was the compromised app used to access data via Microsoft Graph? You can query via the Defender XDR portal using Kusto to find these events •Defender for Cloud Apps - did the compromised app access other M365 services? You can query via the Defender XDR portal using Kusto to find these events •Unified Audit Log - you can retrieve the events related to the compromised app via the audit functionality inside the Defender XDR portal

Open Klara released - your own private cloud Yara scanner! Together with our community member Gajesh, I would like to announce the fork of the KLara project into Open Klara! We aim to maintain, support and fix future bugs. Open KLara is a community-driven fork of the original KLara project by Kaspersky Lab, aimed at helping Threat Intelligence researchers hunt for new malware using Yara. Think of it as your own private Yara scanner where you can setup malware / clean collections on multiple distributed servers and fire up Yara rules, everything centralized with a nice web interface / UI. For more info, check github.com/xdanx/open-kla… Happy hunting!

I finally came around and documented all the Conditional Access bypasses in a single blog post. It contains not only the documented bypasses, but also the results of new research. #Entra #ConditionalAccess #Security #Cheese cloudbrothers.info/en/conditional…

ah...memories

#PIVOTcon26 #CfP is open and you can submit your proposals till 6 FEB 2026 CfP rules and submissions here: pretalx.com/pivotcon26/cfp #ThreatIntel #ThreatResearch #CTI

I live in the real world and so I’m not really surprised to see this, but I am definitely shocked. As an incident response person, how do you spend all day supporting and watching your customer’s teams cope with the stress and grief of going through a ransomware incident and then turn around and inflict that on others. 🤦‍♀️😱🤮

What's that tapping noise? Ah - the keystrokes of Candiru licenses being redeployed...