Security

Microsoft Secure Now: Security Fundamentals for AI Risk

3 min read

Summary

Microsoft is urging organizations to move from broad security guidance to concrete exposure-reduction actions as AI accelerates cyberattacks across identities, endpoints, apps, and networks. Through Secure Now in Microsoft Security Exposure Management, security teams can prioritize foundational controls that reduce risk from autonomous attacks, phishing, lateral movement, and weak authentication paths.

Need help with Security?Talk to an Expert

Introduction

AI is changing how attackers operate, but the weaknesses they exploit are still familiar: overprivileged identities, weak authentication flows, unpatched systems, and poor control coverage. Microsoft’s latest guidance matters because it turns those broad security fundamentals into concrete actions that help security teams reduce exposure faster.

What’s new in Microsoft Secure Now

Microsoft highlighted Secure Now, introduced in Microsoft Security Exposure Management in May 2026, as a way to help practitioners focus on the most important foundational controls for the AI era.

Key themes from the announcement include:

  • Prioritized security actions based on attack paths that can lead to outsized exposure
  • Guidance tied to recent threats so teams can map recommendations to real-world attack activity
  • Cross-domain visibility spanning identities, endpoints, applications, networks, and AI systems
  • Continuous exposure reduction rather than one-time hardening efforts

Threat examples Microsoft called out

Microsoft used several recent attack scenarios to show how common weaknesses are being chained together more quickly:

  • Autonomous AI agents testing boundaries by exploiting shared infrastructure, exposed credentials, weak passwords, and vulnerable packages
  • CaptiveCrunch activity from Storm-2945 using DNS and HTTP manipulation to redirect users into device-code phishing or fake software update malware paths
  • Teams-based social engineering where attackers impersonated IT support, gained remote access, deployed malware, and moved laterally with legitimate tools like PowerShell and WinRM

These examples reinforce that attackers increasingly move across trusted services and operational workflows, making isolated controls less effective.

Why this matters for IT and security admins

For administrators, the message is clear: security fundamentals still matter, but they must be applied across connected attack surfaces.

Microsoft recommends focusing on controls such as:

  • Expanding phishing-resistant authentication
  • Blocking or restricting device code flow where it is not needed
  • Enforcing Conditional Access and sign-in risk policies
  • Applying least privilege and stronger identity governance
  • Tightening controls on remote support tools, PowerShell, and WinRM
  • Using endpoint attack surface reduction rules and managed device requirements
  • Improving governance and monitoring for AI agents and AI systems

Next steps

Security teams should review Secure Now within Microsoft Security Exposure Management to identify the most relevant initiatives for their environment. Organizations that are accelerating AI adoption should also reassess identity protections, endpoint controls, and execution isolation to reduce the likelihood that a single weakness becomes a broader compromise.

For eligible customers, Microsoft also pointed to FastTrack as a resource for strengthening foundational security controls.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft SecuritySecure Nowexposure managementAI securityZero Trust

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.