Sponsored LinkedIn post
A dedicated post to introduce your brand to my audience.
Senior Security Solution Engineer @ Microsoft
Companies pay David to write a post about their product on LinkedIn.
This page is where they book it. Below: David's audience, recent posts and price. Naano, the platform behind this page, handles the brief, your approval of the post and the payment.
€313per post, fixed price
You approve the post before it goes live
Looking for David? View LinkedIn profileA creator yourself? Create your own page
I help organizations strengthen their security posture and accelerate their security transformation through Microsoft Security, AI-powered defense, and modern SOC practices. As a Senior Security Solution Engineer at Microsoft with more than 25 years of experience in IT and cybersecurity, I work with enterprise customers to design, evaluate, and adopt security solutions that deliver both business value and measurable risk reduction. My expertise spans Microsoft Sentinel, Defender XDR, Entra ID, AI Security, Detection Engineering, Threat Hunting, Security Operations, Multi-Cloud Security and Security Governance. I collaborate closely with customers, partners, architects, and consulting teams to translate complex security challenges into practical and scalable solutions. Throughout my career, I have: • Helped organizations modernize their SOC and security operations capabilities • Supported incident response and compromise recovery activities during critical security events • Delivered technical workshops, executive briefings, and presentations at Microsoft and industry events • Built and shared security solutions, detections, workbooks, connectors, and automation assets for the security community I am passionate about continuous learning, emerging technologies, and helping security teams stay ahead of evolving threats. I enjoy mentoring others, sharing knowledge through speaking engagements and community contributions, and creating practical content that helps defenders solve real-world problems. Areas of focus: • AI Security & Agentic AI Governance • Microsoft Sentinel & Security Operations • Detection Engineering & Threat Hunting • Microsoft Defender XDR • Identity Security & Entra ID • Security Automation & SOC Modernization Author, speaker, content creator, and contributor to the Microsoft Security community. If you are interested in my content you can follow me here as well: Youtube: https://www.youtube.com/@davidalonso1867 Substack: https://substack.com/@davidalonsodominguez Github: https://github.com/davidalonsod/Dalonso-Security-Repo
Public LinkedIn data · Oct 1, 2026
Your company deployed 10 AI agents. Then 50. Then 100. Some live in Microsoft 365 Copilot. Others in Copilot Studio. Others call models through Azure AI Foundry or APIs. And now local agents and MCP tools are entering the picture. The problem? 🔎 The security evidence doesn’t live in one place. A SOC analyst may need to understand agent activity, identity, prompts, tool usage, model activity, API behavior, alerts and endpoint evidence. That's exactly the problem I’ve been working on with AI Agents Monitoring Workbook V2 for Microsoft Sentinel. V2 moves beyond simply asking: “What are my AI agents doing?” Now we can start asking much more useful security questions: 🧠 Microsoft 365 Copilot What activity and security signals are we seeing? 🤖 Copilot Studio Which agents are active? What tools and MCP capabilities are they using? ☁️ Azure AI Foundry What is happening with models, tokens and guardrails? 🌐 Azure APIM / AI Gateway Are there anomalous API behaviors or unusual activity patterns? 🛡️ Content Safety Are we seeing prompt injection or sensitive-data-related signals? 🚨 Defender XDR Can agent activity be connected with security alerts and investigations? 📡 Telemetry Health Are my AI security data sources actually producing the evidence I expect? 🔐 Identity & Governance Do I have agents that are inactive or without clear ownership? 💻 Local AI Agents & MCP Can endpoint and Advanced Hunting telemetry help investigate local agents and MCP activity? The workbook is designed as a monitoring and investigation layer, rather than a replacement for detections. Analytics, hunting and visualization have different roles and work better together. AI security isn't just about detecting a malicious prompt. It's about connecting the evidence around: Identity → Agent → Model → Tool → API → Data → Endpoint → Alert So when an analyst sees something suspicious, they have somewhere to start investigating. 🎥 In the new video in comments I walk through V2, from deployment to Copilot telemetry, MCP monitoring, Foundry, APIM, Content Safety, Defender XDR, telemetry health, identity governance and local agent visibility. 👉 Full technical article: AI Agents Monitoring Workbook V2 in comments 👉 Workbook and deployment files: AI Agents Monitoring V2 in comments If AI agents are becoming part of your environment, how are you monitoring them today? #AISecurity #MicrosoftSentinel #SecurityOperations #MicrosoftSecurity #AIagents #CopilotStudio #MicrosoftCopilot #DefenderXDR #ThreatHunting #MCP
Your company deployed 10 AI agents. Then 50. Then 100. Some live in Microsoft 365 Copilot. Others in Copilot Studio. Others call models through Azure AI Foundry or APIs. And now local agents and MCP tools are entering the picture. The problem? 🔎 The security evidence doesn’t live in one place. A SOC analyst may need to understand agent activity, identity, prompts, tool usage, model activity, API behavior, alerts and endpoint evidence. That's exactly the problem I’ve been working on with AI Agents Monitoring Workbook V2 for Microsoft Sentinel. V2 moves beyond simply asking: “What are my AI agents doing?” Now we can start asking much more useful security questions: 🧠 Microsoft 365 Copilot What activity and security signals are we seeing? 🤖 Copilot Studio Which agents are active? What tools and MCP capabilities are they using? ☁️ Azure AI Foundry What is happening with models, tokens and guardrails? 🌐 Azure APIM / AI Gateway Are there anomalous API behaviors or unusual activity patterns? 🛡️ Content Safety Are we seeing prompt injection or sensitive-data-related signals? 🚨 Defender XDR Can agent activity be connected with security alerts and investigations? 📡 Telemetry Health Are my AI security data sources actually producing the evidence I expect? 🔐 Identity & Governance Do I have agents that are inactive or without clear ownership? 💻 Local AI Agents & MCP Can endpoint and Advanced Hunting telemetry help investigate local agents and MCP activity? The workbook is designed as a monitoring and investigation layer, rather than a replacement for detections. Analytics, hunting and visualization have different roles and work better together. AI security isn't just about detecting a malicious prompt. It's about connecting the evidence around: Identity → Agent → Model → Tool → API → Data → Endpoint → Alert So when an analyst sees something suspicious, they have somewhere to start investigating. 🎥 In the new video I walk through V2, from deployment to Copilot telemetry, MCP monitoring, Foundry, APIM, Content Safety, Defender XDR, telemetry health, identity governance and local agent visibility. https://lnkd.in/eK5K-2uB 👉 Full technical article: AI Agents Monitoring Workbook V2 https://lnkd.in/eYH74ZZB 👉 Workbook and deployment files: AI Agents Monitoring V2 on Github https://lnkd.in/eMDEGn9Z If AI agents are becoming part of your environment, how are you monitoring them today? #AISecurity #MicrosoftSentinel #SecurityOperations #MicrosoftSecurity #AIagents #CopilotStudio #MicrosoftCopilot #DefenderXDR #ThreatHunting #MCP
Do you know what’s really hiding in your DNS traffic? DNS logs are a goldmine for security teams, but they can also be a massive headache for your budget if you aren't careful. Real-World Threat Hunting: I’ll show you how to spot DNS Tunneling, Beaconing, and DGA patterns before they escalate. Smart Cost Optimization: Stop paying for "noise." Learn how to use AMA and DCR filtering to ingest only the high-value security data you actually need. The Ultimate DNS Workbook: A full tour of my custom dashboard—from executive security summaries to geolocation and ingestion health. Jump to the section you need: 0:00 — Intro: Why DNS telemetry is a game-changer 0:50 — Overview: The DNS Workbook & Hunting strategy 1:16 — Where to get the templates (GitHub & ARM) 2:30 — Saving Money: Filtering DNS logs with AMA/DCR 4:50 — Setting up the Windows DNS Connector 5:50 — Analytical Rules & Mitre Att&ck Mapping 7:10 — Deep Dive: The Centralized DNS Workbook 11:00 — Analyzing traffic noise to optimize filtering 12:58 — Identifying suspicious and malicious domains 14:40 — Threat Geolocation: Visualizing the origin of attacks 17:35 — Investigating DNS Incidents 19:19 — Final wrap-up and recommendations Resources: Workbook https://lnkd.in/e7BtbFGm Detections https://lnkd.in/eNz3syKK #MicrosoftSentinel #CloudSecurity #CyberSecurity #ThreatHunting #DNSMonitoring #AzureSecurity #SOC #BlueTeam #Infosec #CostOptimization #dns #microsoftsecurity #activedirectory
Choose a format for your next LinkedIn collaboration.
A dedicated post to introduce your brand to my audience.
Your collaboration, managed on Naano
How does this price compare? B2B creator rates 2026
Based on 41 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 41 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 41 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 41 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
I help security professionals get more value from Microsoft Security through practical detections, hunting queries, workbooks and real-world security research.
Storefront by Naano · Create yours
David Alonso Dominguez is a B2B LinkedIn creator based in Spain with 5,563 followers, posting about Cybersecurity, AI, and Software. On Naano, one sponsored LinkedIn post by David Alonso Dominguez costs €313, a fixed price per post.
The Naano team casts the creators, writes the briefs, reviews every draft with you and reports results per creator. You approve the shortlist and every draft.