Modern phishing increasingly abuses legitimate authentication workflows, trusted infrastructure, and encrypted browser sessions.
This forces SOCs to rethink how they investigate, detect, and respond. Here are key strategic priorities you can adapt as a security leader in order to maintain a strong security posture, based on recent cyber threat research from ANY.RUN.
Strategic Priority #1: Protect Identity Beyond Credentials
The abuse of legitimate authentication flows rather than password theft is on the rise. Using device code phishing, threat actors behind campaigns such as Kali365 exploit Microsoft’s legitimate Device Code authentication flow, obtain access to the OAuth, and refresh tokens without having the need to host a fake login page.
The entire attack flow resembles the standard flow too closely to be easily detectable and generate many indicators. The key lesson is: even legitimate authentication flows can lead to unauthorized cloud access, making identity visibility and token security essential parts of modern SOC operations.
1) Expand monitoring for OAuth and device code abuse
Ensure the SOC can detect unusual OAuth activity, token issuance, new application access, and suspicious use of Microsoft 365 resources.
2) Prepare for token-based compromise
Incident response plans should include session revocation, refresh-token invalidation, OAuth consent review, and investigation of mailbox, document, and SaaS activity. Measure how quickly teams can confirm token abuse, identify affected accounts, and determine business impact.
3) Review authentication policies
Restrict or disable device code authentication flow where possible and apply conditional access controls to reduce unnecessary exposure.
Strategic Priority #2: Increase SOC Investigation Visibility
Modern phishing can remain visible as isolated detections without being understood as a wider operation.
It unfolds by abusing trusted platforms, anti-bot checks, and convincing login pages that delay detection and incident response in many companies.
Campaigns such as Kratos demonstrate how threat actors can hide credential theft behind normal-looking user interactions, making phishing harder to investigate and connect across incidents.
For security leaders, this means that there’s a need to ensure that SOC analysts have enough visibility to reconstruct the complete attack chain, piece together technical evidence, and respond before a compromised account escalates into a large-scale incident.
1) Beyond MTTD: Measure time to attribution
Phishing investigations don’t end with detection: analysts should be able to connect related activity, understand campaign scale, identify affected users, and assess business impact.
.webp)
Browser-level visibility into page behavior, redirects, network requests, and DOM changes makes this possible.
ANY.RUN Interactive Sandbox provides that visibility through browser-level analysis, behavioral telemetry, and SSL decryption, allowing analysts to reconstruct the complete phishing chain and investigate activity inside encrypted browser sessions.
Detect, investigate, and respond faster with in-browser data inspection from ANY.RUN. Gain complete phishing visibility to strengthen your SOC and reduce MTTR
2) Create separate response playbooks for different phishing types
While credential-harvesting attacks may be contained with password resets, suspected AiTM or session-theft activity requires session revocation, refresh-token invalidation, and broader identity investigation. Those are completely different approaches, and SOC teams should be ready for any scenario.
3) Avoid broad infrastructure blocking
Modern phishing frequently abuses shared cloud services, Cloudflare, and compromised legitimate websites. Instead of fully blocking infrastructure, SOC analysts need to first validate browser behavior and evidence to minimize unnecessary business disruption.
Strategic Priority #3: Build Behavioral Detection
Phishing campaigns like PhantomEnigma demonstrate how modern threats can evade detection by combining trusted infrastructure, modular malware, and rapidly changing delivery paths.
The lesson is that reducing business risk takes more than collecting new IOCs. The strategic priority is to improve how investigations are prioritized and connected overall, while relying less on static indicators and more on behavioral evidence that persists as campaigns evolve.
1) Review how “clean” verdicts are escalated
Establish clear escalation criteria for suspicious files delivered through trusted infrastructure, even when automated detections classify them as benign.
2) Prioritize behavioral evidence over infrastructure
Detection strategies must include recurring malware behavior, execution chains, persistence mechanisms, and network patterns that remain stable across campaign updates.
3) Correlate investigations across security solutions
Email alerts, endpoint activity, sandbox analysis, and threat intelligence should contribute to a single investigation. Fragmented workflows make coordinated campaigns appear as isolated incidents, delaying containment and increasing response costs.
Putting This Strategy into Practice
The campaigns we discussed differ in their techniques, but they point to the same strategic shift: modern phishing increasingly exploits trust rather than technical vulnerabilities.
Legitimate authentication workflows, trusted websites, and constantly changing infrastructure make static detections alone insufficient, which is why SOC teams should prioritize:
- Validating behavior over reputation
Compromised government portals, legitimate email accounts, and trusted cloud services can all become part of a phishing attack. Instead of relying solely on reputation, security teams should validate how a page behaves and how an attack unfolds before making response decisions.
- Turning investigations into threat hunting
Every phishing investigation should strengthen future detection. Operationalize validated indicators and behavioral intelligence by feeding them into SIEM, SOAR, and threat hunting workflows to uncover related activity and identify emerging campaigns earlier.
Actionable threat intelligence from ANY.RUN delivers fast access to enriched indicators and industrial context across 15K+ companies.

This enables analysts to pivot directly from sandbox investigations into TI Lookup and YARA Search, expanding a single incident into proactive threat hunting and broader campaign analysis.
- Continuously operationalizing threat intelligence
As attackers rotate infrastructure, delivery techniques, and malware variants, detection logic should evolve just as quickly. Continuously updating security controls with validated threat intelligence helps prevent detections from becoming outdated.
ANY.RUN TI Feeds, built on real-world threat data from more than 15,000 organizations, deliver continuously updated, analysis-backed indicators to SIEM, SOAR, TIP, and EDR platforms, helping security teams detect and respond to emerging phishing campaigns faster.
How Changing Phishing Strategy Benefits SOC and Business Security
- Reduce investigation time by up to 21 minutes per case through faster triage and streamlined investigations.
- Increase detection rates by 36% with greater visibility into modern phishing techniques.
- Detect up to 5× more encrypted phishing activity by inspecting attacks hidden inside HTTPS sessions.
- Expand every investigation into proactive threat hunting with more than 60,000 confirmed malicious URLs added to ANY.RUN TI Lookup each month.
- Improve analyst productivity and reduce unnecessary escalations by giving teams complete behavioral context from the start.
Modern phishing demands a streamlined SOC investigation process. Reduce investigation time by 21 minutes per case and improve detection rates by 36% with ANY.RUN → Power Your SOC
Conclusion
Protecting against modern phishing requires more than blocking malicious emails. SOCs that prioritize identity visibility, behavioral analysis, and continuous threat intelligence are better equipped to stop today’s most advanced attacks.





