tag: Oauth · 8 items
- Engineer — Plan: Device code phishing abuses the OAuth device authorization grant, which many cloud tenants leave unrestricted by default; audit Conditional Access policies in Entra ID to block or scope device code flow to legitimate managed devices only.
- SOC/IR — Act: Active named campaign targeting U.S. organizations via device code auth abuse — hunt for anomalous device code authentication events in Entra ID/M365 sign-in logs (filter on ‘DeviceCode’ grant type) and flag suspicious OAuth token issuances since at least early October 2026.
- Leader — Learn: This campaign highlights that modern account takeover can succeed through legitimate auth flows rather than credential theft, making it harder to detect via traditional controls; useful framing for risk conversations but no immediate leadership action required absent a confirmed breach at a dependent vendor.
- Engineer — Learn: OAuth flows and OIDC configurations are core to cloud/app infrastructure; a landscape piece from Unit 42 can sharpen threat modeling for token handling and consent flows, but no enrichment signals indicate immediate exploitation pressure requiring a config or patch change.
- SOC/IR — Learn: Understanding current OAuth abuse TTPs (token theft, consent phishing, app impersonation) can improve detection coverage in M365 and cloud environments, but the summary provides no specific IOCs or ATT&CK mappings to act on today.
- Leader — Skip
- Engineer — Plan: OAuth grant sprawl is a real exposure in any cloud/SaaS estate; this quarter, audit all third-party OAuth grants in your IdP and SaaS apps, revoke stale ones, and implement a review gate for new grant requests.
- SOC/IR — Learn: The Klue breach illustrates how dormant OAuth grants become persistent access paths, but no IOCs or ATT&CK-mapped TTPs are provided here — useful framing for future detection design around anomalous OAuth token usage, not actionable today.
- Leader — Plan: The Klue breach case makes this board-adjacent: establish an OAuth grant inventory and periodic review policy for your SaaS estate before an unreviewed grant becomes your own incident.
- Engineer — Plan: Any application built on the MCP Python SDK before 1.30.0 could expose OAuth client secrets, authorization codes, and PKCE keys to a malicious MCP server; upgrade to 1.30.0 and audit all MCP server endpoints your app trusts. No active exploitation signals yet, but the credential theft path is direct.
- SOC/IR — Learn: No IOCs, no exploitation activity, and no useful detection surface today, but understanding that MCP servers are a potential OAuth credential harvesting vector is worth noting as AI-agent tooling proliferates in enterprise environments.
- Leader — Learn: This is an early signal about supply-chain risk in AI-agent SDK infrastructure; no breach or active exploitation reported, but worth factoring into any AI-agent adoption policy before MCP-based tooling is widely deployed internally.
- Engineer — Plan: Device-code phishing bypasses MFA by abusing the OAuth device-authorization flow; review Conditional Access policies to restrict or block device-code grant type for untrusted networks or users who don’t need it.
- SOC/IR — Plan: The service is dismantled but the TTP persists — build or tune detections for anomalous device-code authentication requests (unusual tenant, geolocation, or off-hours token grants) in your SIEM before copycats emerge.
- Leader — Learn: Takedown of a 12,000-inbox-compromise phishing platform reinforces the AI-enhanced threat narrative worth including in the next leadership or board briefing on evolving phishing sophistication; no immediate exposure action required given the service is offline.
- Engineer — Plan: Device code flow abuse bypasses MFA by design; audit your identity provider (Entra ID, Okta) and restrict or disable the OAuth Device Authorization Grant for users/apps that don’t require it — block or conditional-policy-gate this flow this quarter.
- SOC/IR — Plan: No IOCs provided, but Greatness PhaaS commoditizing device code phishing signals growing campaign volume; build detections in Entra/Okta logs for unexpected device code authorization requests, particularly outside normal device-enrollment windows.
- Leader — Learn: MFA bypass techniques are now packaged in commercial crimeware toolkits, eroding the assurance value of standard MFA — useful context for risk register updates and for evaluating phishing-resistant auth (FIDO2/passkeys) as a strategic control.
- Engineer — Plan: RabbitMQ is widely deployed as enterprise messaging infrastructure; these access control flaws — OAuth client secret leakage and cross-tenant queue metadata exposure — represent real risk for teams running it in multi-tenant or OAuth-integrated configurations. No active exploitation or PoC reported, but identify affected versions and schedule patching once a fix is available.
- SOC/IR — Learn: No IOCs, no reported exploitation, and no actionable detection surface in this disclosure; file for context in case RabbitMQ compromise indicators surface later, but no hunt or detection work is warranted now.
- Leader — Skip
- Engineer — Plan: At least two active threat actors are exploiting this Entra ID gap, but there’s no patch—the exposure is architectural. Audit your Entra OAuth app registrations and conditional access policies, and restrict which OAuth clients are permitted for interactive and non-interactive flows.
- SOC/IR — Act: This technique deliberately suppresses successful sign-in events, creating a blind spot in standard Entra telemetry; shift detection to Entra audit logs for anomalous OAuth client IDs and non-standard token-request patterns, and run a retrospective hunt across the past 90 days of OAuth activity.
- Leader — Plan: Credential-validation activity against your Entra tenant may be occurring without triggering existing alerts; ask your security team to assess current detection coverage for OAuth-based evasion and confirm whether identity monitoring logs are capturing the necessary audit events.