# MFA Published articles for MFA. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Auth0 launches v0 integration for production application authentication DevFeed: [Auth0 launches v0 integration for production application authentication]() Original publisher: [Read original article]() Author: Juan Cruz Martinez Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [Authentication](), [app builder](), [Access Control](), [Artificial Intelligence](), [Vercel](), [MFA]() Tags: [access-control](), [ai](), [app-builder](), [auth0](), [authentication](), [mfa](), [sdk](), [vercel]() ### AI overview Auth0 is launching an integration with v0 that lets users configure authentication directly from prompts, including login, protected routes, B2B use cases, enterprise identity providers, and MFA. The integration can create Auth0 applications, configure connections, and wire the SDK into generated code. ### Source excerpt Stop relying on generic login forms. Use the new Auth0 v0 integration on the Vercel identity platform to build secure, production-ready AI app authentication. ## Authentication is a long-running Workflow DevFeed: [Authentication is a long-running Workflow]() Original publisher: [Read original article]() Author: Mason Williams Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Authentication](), [MFA](), [browser](), [Go Language](), [TypeScript](), [Deployment](), [push-notification](), [sessions](), [API]() Tags: [api](), [authentication](), [browser](), [community](), [deployment](), [go](), [mfa](), [push-notification](), [sessions](), [typescript]() ### AI overview This article explains how KERNEL models Managed Auth as a long-running Temporal workflow. A parent workflow maintains connection state, health checks, reauthentication, and cancellation, while child workflows handle individual login attempts with separate browsers, timeouts, and cleanup. Durable state stays in Go, and model-driven work runs in a dedicated TypeScript Worker. ### Source excerpt In this article# - A login is not a request - Model the connection, not the attempt - The human is part of the Workflow - Staying logged in is part of the product - Go owns durability; TypeScript runs the agent - What we learned 1. A login is not a request# An agent can enter a password, stop at an MFA prompt, wait for a person to approve a push notification, and then resume in the same browser. A deployment or Worker restart can happen anywhere in between. ## AuthKit vs Better Auth for B2B SaaS DevFeed: [AuthKit vs Better Auth for B2B SaaS]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-14T00:00:00Z Content type: comparison Language: en Sources: [WorkOS Blog]() Topics: [Software as a service](), [Single sign-on (SSO)](), [Security](), [log management](), [threat detection](), [Frameworks](), [MFA](), [Passkeys]() Tags: [auth](), [comparison](), [enterprise](), [logs](), [mfa](), [saas](), [security](), [threat-detection](), [vercel]() ### AI overview This comparison examines AuthKit and Better Auth as platforms for B2B SaaS products selling to enterprise IT buyers. It argues that both now provide core capabilities such as SSO, SCIM, and audit logs, so the meaningful differences are provider coverage, where user lifecycle management begins, and contractual responsibility. The article also describes Better Auth's hosted infrastructure, dashboard, SIEM drain, self-service provisioning, and threat detection features, while noting its convergence with AuthKit on enterprise requirements. ### Source excerpt Both ship SSO, SCIM and audit logs now. The comparison that decides enterprise deals has moved to the long tail: provider coverage, where user lifecycle actually starts, and who is contractually on the hook. ## Passkey-themed social engineering leads to identity and cloud compromise DevFeed: [Passkey-themed social engineering leads to identity and cloud compromise]() Original publisher: [Read original article]() Author: Microsoft Security Research, Krithika Ramakrishnan, Bharat Vaghela, Vaibhav Deshmukh, Subhajit Ghosh, Anusha Chakraborty, Akash Chaudhuri, Victor Chingtham and Ivan Macalintal Published: 2026-09-09T17:41:18Z Content type: article Language: en Sources: [Microsoft Security Blog]() Topics: [MFA](), [data-processing]() Tags: [adversary-in-the-middle-aitm](), [apis](), [attacks](), [authentication](), [cloud](), [data](), [identity](), [mfa](), [phishing](), [security](), [social-engineering]() ### AI overview Microsoft Security Research describes a passkey-themed social-engineering campaign that compromises cloud identities through AiTM phishing or device-code flows, establishes authentication persistence, and collects cloud data. It outlines investigation signals and recommends revoking sessions and removing unauthorized authentication methods after confirmed compromise. ### Source excerpt Passkey-themed social engineering is being used to compromise identities and enable broader cloud attacks. Learn how threat actors establish MFA persistence, abuse Microsoft Graph for reconnaissance, and access SharePoint, OneDrive, and email data, along with key detection and mitigation guidance. The post Passkey-themed social engineering leads to identity and cloud compromise appeared first on Microsoft Security Blog. ## How to add AuthKit to a Next.js app DevFeed: [How to add AuthKit to a Next.js app]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-02T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Tutorial](), [Authentication](), [Next.js](), [SDKs]() Tags: [auth](), [authentication](), [callback](), [cors](), [email-verification](), [how-to](), [mfa](), [next-js](), [sdk](), [tutorial]() ### AI overview This tutorial explains how to add WorkOS AuthKit to a Next.js app using either an AI-powered CLI installer or a manual integration. It covers hosted sign-in, session handling, redirect configuration, and validating the build. ### Source excerpt Go from no auth to a full hosted sign-in flow, either in one command or step by step. ## Continuous identity intelligence for post-login security evaluation DevFeed: [Continuous identity intelligence for post-login security evaluation]() Original publisher: [Read original article]() Author: Catie Kolander Published: 2026-09-01T00:00:00Z Content type: article Language: en Sources: [Twilio Blog]() Topics: [Digital Security](), [Authentication](), [MFA](), [API](), [passwords](), [Passkeys]() Tags: [ai](), [authentication](), [industry-insights](), [mfa](), [passwords](), [security]() ### AI overview The article argues that passwords, MFA, and passkeys secure only the initial login, while later session activity may become risky. It advocates continuous post-login identity and context evaluation, delegated authority, communication guardrails, and auditability for sensitive actions. ### Source excerpt Secure your platform in the AI era with continuous identity intelligence. Learn how. ## Break-glass access for Amazon EKS when federated identity fails DevFeed: [Break-glass access for Amazon EKS when federated identity fails]() Original publisher: [Read original article]() Author: Sam Mukherjee Published: 2026-08-26T16:20:28Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon EKS](), [AWS Identity and Access Management (IAM)](), [Infrastructure as code](), [MFA](), [Authorization](), [iac-security](), [migration]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [aws-iam](), [best-practices](), [identity-and-access-management](), [infrastructure-as-code](), [mfa](), [migration](), [technical-how-to]() ### AI overview This post presents a break-glass access pattern for Amazon EKS clusters when a federated identity provider fails. It describes a dedicated cross-account IAM role with enforced, recency-aware MFA, infrastructure-as-code templates, validation tests, and post-incident recovery procedures. ### Source excerpt Implementing break-glass access for Amazon EKS clusters removes the circular dependency where a federated identity provider outage locks you out of the clusters you need to reach to fix it. This post supplies a cross-account IAM role with enforced MFA, infrastructure-as-code templates, validation tests, and a post-incident recovery procedure. ## How to let support agents act as a user without losing the audit trail DevFeed: [How to let support agents act as a user without losing the audit trail]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-25T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Authorization](), [audit trail](), [Security](), [Auth0](), [browser](), [MFA]() Tags: [audit-trail](), [auth0](), [authorization](), [b2b](), [browser](), [mfa](), [security]() ### AI overview This tutorial explains how to implement delegated support sessions so support agents can view an application as a customer while preserving authorization scope, short session lifetimes, revocation, dual-identity records, and separate audit events. It uses AuthKit and Audit Logs and compares the approach with Auth0's Session Delegation. ### Source excerpt Support agents need to see what a user sees. Here is how to run impersonation on AuthKit and Audit Logs with scoping, short sessions, clean revocation, and dual-identity records. ## Identity Abuse Through Trusted Communication Channels DevFeed: [Identity Abuse Through Trusted Communication Channels]() Original publisher: [Read original article]() Author: Bill Batchelor Published: 2026-08-20T10:00:25Z Content type: article Language: en Sources: [Unit 42]() Topics: [Security](), [Authentication](), [Social engineering](), [Software as a service](), [Incident response]() Tags: [authentication](), [credential-theft](), [identity](), [identity-theft](), [incident-response](), [malware](), [mfa](), [phishing](), [remote-access-software](), [saas](), [security](), [social-engineering](), [threat-research]() ### AI overview Unit 42 examines how attackers abuse trusted enterprise communication and collaboration platforms for identity phishing, impersonation, credential theft, malware delivery and social engineering. The article describes how compromised identities can make malicious activity appear legitimate within authenticated collaboration sessions and offers recommendations for detecting and defending against these attacks. ### Source excerpt Unit 42 details how attackers exploit enterprise collaboration tools for identity phishing and credential theft. Discover key defense strategies. The post Identity Abuse Through Trusted Communication Channels appeared first on Unit 42. ## Threat Brief: Mitigating Large-Scale Credential Attacks (Updated August 18) DevFeed: [Threat Brief: Mitigating Large-Scale Credential Attacks (Updated August 18)]() Original publisher: [Read original article]() Author: Unit 42 Published: 2026-08-18T19:05:33Z Content type: article Language: en Sources: [Unit 42]() Topics: [Credential theft](), [password spraying](), [MFA](), [Microsoft](), [Incident response]() Tags: [credential-based-attacks](), [credential-theft](), [general](), [high-profile-threats](), [identity](), [incident](), [incident-response](), [mfa](), [microsoft](), [password-spraying](), [thehatman]() ### AI overview This threat brief examines large-scale credential attacks, including password spraying campaigns and claimed credential theft from Microsoft Entra tenants. It provides guidance for identifying suspicious login activity, auditing remote access logs, and hardening internet-exposed edge devices. ### Source excerpt In August 2026, the actor TheHatman claimed to have stolen large volume of credentials from organizations' Microsoft Entra tenants. We provide guidance on mitigating large-scale credential attacks. The post Threat Brief: Mitigating Large-Scale Credential Attacks (Updated August 18) appeared first on Unit 42. ## Custom MFA factor: send a second factor through any channel DevFeed: [Custom MFA factor: send a second factor through any channel]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-08-14T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [MFA](), [Authentication](), [API](), [Node.js](), [Rust]() Tags: [announcements](), [api](), [authentication](), [backend](), [console](), [mfa](), [node](), [rust](), [security](), [voice](), [whatsapp]() ### AI overview Appwrite introduces a custom MFA factor that generates and verifies authentication codes while allowing applications to deliver them through channels such as WhatsApp, voice calls, or internal providers. The article explains how to retrieve the code through a server-side function and deliver it securely. ### Source excerpt Appwrite now supports a custom MFA factor. Appwrite generates and verifies the code, and your function delivers it through WhatsApp, a voice call, or any provider you choose. ## How to add step-up authentication to your Next.js app with WorkOS AuthKit DevFeed: [How to add step-up authentication to your Next.js app with WorkOS AuthKit]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-10T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Next.js](), [Authentication](), [Tutorial](), [OpenID connect (OIDC)](), [MFA](), [ui]() Tags: [auth](), [authentication](), [build](), [how-to](), [mfa](), [next-js](), [oidc](), [sign-in](), [ui]() ### AI overview This tutorial shows how to add step-up authentication to a Next.js application using WorkOS AuthKit. It gates a destructive action, revoking all API keys, behind recent interactive re-authentication using auth_time and max_age, while preserving the user's session and location in the interface. ### Source excerpt Build a Next.js app with AuthKit sign-in, then gate a destructive action behind a fresh re-authentication using auth_time and max_age. ## Inside the Modern SOC: The Identity Front Door DevFeed: [Inside the Modern SOC: The Identity Front Door]() Original publisher: [Read original article]() Author: Sharon Maydar Published: 2026-08-07T23:00:01Z Content type: article Language: en Sources: [Unit 42]() Topics: [Incident response](), [MFA](), [Vulnerabilities]() Tags: [ai](), [attacks](), [authentication](), [credential-theft](), [identity](), [incident-response](), [inside-the-modern-soc](), [insights](), [mfa](), [phishing](), [soc](), [social-engineering](), [unit-42-incident-response-report](), [vulnerabilities]() ### AI overview The article examines identity-based initial access, including credential theft, MFA manipulation, session hijacking, phishing, and social engineering. It describes how attackers expand access through persistence, privilege escalation, and lateral movement, challenging SOC teams to correlate signals across environments. ### Source excerpt Identity-based attacks drive 90% of incidents. Learn how modern attackers exploit identities and what SOC leaders can do to respond. The post Inside the Modern SOC: The Identity Front Door appeared first on Unit 42. ## Bring your security stack into Edge for Business -- with support for more partners DevFeed: [Bring your security stack into Edge for Business -- with support for more partners]() Original publisher: [Read original article]() Author: Microsoft Edge Team Published: 2026-08-04T16:00:24Z Content type: article Language: en Sources: [Microsoft Edge Blog]() Topics: [Edge for Business](), [browser](), [Cisco Secure Access](), [Security](), [Endpoint Security & XDR](), [MFA](), [telemetry](), [Microsoft]() Tags: [browser](), [cisco-secure-access](), [edge-for-business](), [endpoint-security](), [integrations](), [mfa](), [microsoft](), [security](), [telemetry](), [uncategorized]() ### AI overview This Microsoft Edge Blog article announces expanded Edge for Business security connector integrations. It highlights Cisco Secure Access, Tanium, and Clever integrations for browser-based security, telemetry, endpoint visibility, compliance validation, data protection, AI guardrails, and streamlined MFA in education environments. ### Source excerpt At a glance Edge for Business security connectors extend your security tools into the browser, so you gain visibility and enforcement where work happens. This update adds new partner integrations, including Cisco Secure Access, The post Bring your security stack into Edge for Business -- with support for more partners appeared first on Microsoft Edge Blog. ## Behind the console: An AiTM phishing kit harvesting AWS console credentials and beyond DevFeed: [Behind the console: An AiTM phishing kit harvesting AWS console credentials and beyond]() Original publisher: [Read original article]() Author: Datadog Published: 2026-06-24T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [Adversary-in-the-middle (AiTM)](), [Amazon Web Services](), [Security](), [MFA](), [Cloudflare](), [JavaScript](), [VirusTotal](), [Batch file](), [cURL](), [Amazon Route 53]() Tags: [adversary-in-the-middle-aitm](), [aws](), [batch](), [cloudflare](), [dns](), [javascript](), [mfa](), [security](), [virustotal]() ### AI overview Datadog Security Research analyzes a June 2026 campaign using cloned AWS console login pages and adversary-in-the-middle techniques to harvest credentials and MFA codes. The article details the phishing infrastructure, delivery methods, VirusTotal artifact, and JavaScript-based credential-harvesting flow. ### Source excerpt Datadog Security Research investigates a June 2026 adversary-in-the-middle phishing campaign that cloned the AWS console login page to harvest victim credentials and multi-factor authentication codes. ## Automatically enrich security logs with MITRE ATT&CK context before they reach your SIEM DevFeed: [Automatically enrich security logs with MITRE ATT&CK context before they reach your SIEM]() Original publisher: [Read original article]() Author: Danielle Park Published: 2026-06-24T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [observability pipelines](), [SIEM, Security](), [SIEM, Security, Observability](), [log management](), [Incident response](), [Threat Hunting & Intel](), [Firewall](), [MFA](), [Amazon Web Services](), [DDoS]() Tags: [api](), [aws](), [cloud-siem](), [devsecops](), [firewall](), [incident](), [incident-response](), [log-management](), [logs](), [malware](), [mfa](), [network](), [observability](), [observability-pipelines](), [security](), [techniques](), [threat-detection]() ### AI overview This article explains how Observability Pipelines uses MITRE ATT&CK Enrichment Packs to automatically map security logs and events to common attacker tactics and techniques before they reach a SIEM, data lake, or archive. It describes the initial packs for Okta, Palo Alto, FortiGate, and AWS WAF, covering identity, firewall, network, and web security activity. ### Source excerpt Learn how Observability Pipelines enriches security logs with MITRE ATT&CK tactics and techniques before routing them to your SIEM or storage destination. ## AI-driven zero-day combinations are challenging software security and open-source consumption DevFeed: [AI-driven zero-day combinations are challenging software security and open-source consumption]() Original publisher: [Read original article]() Published: 2026-05-28T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Artificial Intelligence](), [open-source-security](), [Security](), [Open Source](), [Machine Learning, Security Attacks](), [Critical Infrastructure](), [openssf](), [sigstore]() Tags: [ai](), [anthropic-mythos](), [chainguard-containers](), [critical-infrastructure](), [fork](), [mfa](), [mythos](), [open-source](), [open-source-security](), [openssf](), [oss](), [project-glasswing](), [rust](), [sast](), [secure-open-source](), [security](), [sigstore]() ### AI overview The article argues that Mythos represents a potential new class of software-security threat: AI-driven combinations of existing issues that can produce more serious attacks than individual scanner findings. It discusses the limits of government regulation and calls for stronger trust infrastructure, coordinated disclosure, and safer open-source consumption. ### Source excerpt Mythos is changing software security fast. AI-driven zero-days demand new trust infrastructure, coordinated disclosure, and secure open source consumption. ## Credential management for AI agents DevFeed: [Credential management for AI agents]() Original publisher: [Read original article]() Author: info@1password.com (Rachel Sudbeck) Published: 2026-05-07T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [AI Bots](), [passwords](), [MFA]() Tags: [ai](), [ai-agents](), [api-keys](), [developer](), [identity](), [management](), [mfa](), [saas](), [secrets](), [security](), [unified-access]() ### AI overview The article examines how AI agents intensify credential sprawl by creating, using, and replicating non-human credentials at machine scale. It highlights risks from overprivileged, long-lived, and poorly audited API keys and service accounts, alongside gaps in traditional identity controls. ### Source excerpt This blog has been adapted from an excerpted section of 1Password's ebook: Credential sprawl: How AI increases the risks. To read the complete ebook and learn more about the evolving challenges of credential sprawl, click here. The proliferation of credentials outside centralized visibility and control is known as "credential sprawl," and attackers are eager to take advantage of it. Unfortunately, credential management is a broad problem that only grows in complexity as organizations add new tools, employees, and partners. Today's companies have to manage an ever-growing number of credentials that go well beyond traditional passwords, such as developer secrets, passkeys, shared logins, API keys, SSH keys, service accounts, and SSO access tokens. Each of these, if exposed in an attack or breach, can have severe consequences, and developer secrets pose particular, systemic risk. Addressing credential sprawl has become especially urgent due to the rise of AI-based tools and agents. AI agents are a primary driver of credential sprawl because they create, use, and replicate credentials at machine scale. They have unique access needs and can behave both autonomously and unpredictably. Companies that want to integrate AI-based tools must carefully consider how to mitigate these risks to avoid an exponential rise in unmanaged and vulnerable credentials. How do AI agents increase credential risk? AI agents increase credential security risks through their reliance on non-human identities like API keys and service accounts, which are frequently overprivileged, long-lived, and poorly audited. Agents create and use these credentials at machine scale, beyond centralized oversight, leading to rapidly expanding credential sprawl with limited oversight for security teams. And while AI tools and agents pose new and distinct risks, they're also expanding on credential problems that have existed for years, stemming from SaaS sprawl, shadow IT, and unsafe developer practices. Traditiona ## Secure Marketplace credentials with Production-only access DevFeed: [Secure Marketplace credentials with Production-only access]() Original publisher: [Read original article]() Author: Hannah Hearth Published: 2026-05-06T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authorization](), [MFA]() Tags: [cli](), [mfa](), [production](), [secrets](), [vercel]() ### AI overview Vercel now lets teams restrict native integration resources to Production-only environments. This removes or blocks non-production connections and protects integration credentials from dashboard and CLI access; secret rotation is recommended after enabling the restriction. ### Source excerpt You can now secure native integration resources by restricting where they can be used. Setting a resource to Production only removes non-production access and protects credentials as sensitive environment variables. This makes it so secret values or no longer readable from the dashboard or CLI From the integration resource Settings, select Allowed Environments -> Production only and save. We recommend that you rotate the secrets of the integration resource after saving. Once applied: Development and Preview connections are removed New non-production connections are blocked Connections without a Production target are disconnected Credentials are protected and no longer readable Reverting this setting requires Owner permissions for your Vercel team. Owners can re-enable Development and Preview environment from Settings and reconnect projects if needed. You may be prompted to reauthenticate with an MFA challenge depending on your settings. Learn more in the Vercel documentation. Read more ## PCI DSS Compliance: What Digital Businesses Need to Know DevFeed: [PCI DSS Compliance: What Digital Businesses Need to Know]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Security](), [Social engineering](), [Network Segmentation](), [TLS (Transport Layer Security)](), [vulnerability management](), [SIEM, Security](), [Software as a service](), [tokenization]() Tags: [compliance](), [digital-products](), [firewalls](), [mfa](), [network-segmentation](), [pci-dss](), [saas](), [scope](), [security](), [siem](), [tls](), [tokenization](), [vulnerability-management]() ### AI overview This guide explains how PCI DSS applies to digital businesses that accept card payments, including SaaS companies and sellers of digital products. It outlines the standard's 12 requirements and discusses controls for networks, account data, vulnerabilities, access, monitoring, and information security. It also covers card-not-present transactions, recurring billing, and tokenization. ### Source excerpt PCI DSS compliance explained for digital businesses. Understand the 12 requirements, compliance levels, and how to reduce your scope when selling digital products online. ## From Plaintext, to BLESS, to Identity: The Evolution of Secure Remote Access DevFeed: [From Plaintext, to BLESS, to Identity: The Evolution of Secure Remote Access]() Original publisher: [Read original article]() Author: info@goteleport.com (Leon Fong) Published: 2026-04-09T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [remote access](), [Security](), [ssh](), [Unix](), [MFA]() Tags: [mfa](), [remote-access](), [security](), [ssh]() ### AI overview A historical developer article traces secure UNIX remote access from plaintext telnet and rsh to SSH encryption and key-based login, then discusses the operational risks of long-lived SSH keys. It also describes Netflix's use of MFA and signed SSH certificates as a more secure remote-access approach. ### Source excerpt A senior Adobe security engineer traces the evolution of secure remote access from telnet to SSH keys, Netflix's BLESS, and modern certificate-based identity. ## As breakout time accelerates, prevention-first cybersecurity takes center stage DevFeed: [As breakout time accelerates, prevention-first cybersecurity takes center stage]() Original publisher: [Read original article]() Author: Phil Muncaster Published: 2026-04-07T09:00:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [Cybersecurity](), [Threat Research](), [Artificial Intelligence](), [Automation](), [MFA](), [passwords](), [Reconnaissance](), [Social engineering](), [spoofing](), [ransomware]() Tags: [ai](), [ai-automation](), [attacks](), [authentication](), [automation](), [business-security](), [cybersecurity](), [exploits](), [malware](), [mfa](), [passwords](), [phishing](), [ransomware](), [social-engineering](), [tools]() ### AI overview Threat actors are using AI, automation, credential theft, phishing, zero-day exploits, reconnaissance, and AI-powered scripts to accelerate attacks. The article argues that shrinking breakout times require defenders to adopt a prevention-first cybersecurity strategy. ### Source excerpt Threat actors are using AI to supercharge tried-and-tested TTPs. When attacks move this fast, cyber-defenders need to rethink their own strategy. ## Go beyond device health with External Checks in 1Password Device Trust DevFeed: [Go beyond device health with External Checks in 1Password Device Trust]() Original publisher: [Read original article]() Author: info@1password.com (1Password) Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Device Trust](), [Zero Trust](), [API](), [Security](), [MFA]() Tags: [api](), [compliance](), [device-trust](), [external](), [mfa](), [security](), [zero-trust]() ### AI overview 1Password Device Trust now supports custom External Checks that use signals from third-party systems, such as compliance status, policy acknowledgments, MFA enrollment, and employment status, in access decisions for protected applications. ### Source excerpt Most organizations already have the policies they need in place. The problem is enforcement. Employees must complete security awareness training, contractors must acknowledge updated agreements, and teams must meet compliance requirements. But the systems that track these requirements rarely connect to the systems that control user and device access. As a result, access is granted even when required conditions haven't been met. That's why we're excited to announce that 1Password Device Trust can now take signals from other systems into account before allowing users to reach sensitive company apps and data. External Checks in Device Trust Until now, 1Password Device Trust focused primarily on device telemetry. That meant administrators could block employees from accessing company resources if their device failed to meet certain requirements, but they couldn't enforce compliance based on signals that live outside of the device. With the ability to create custom External Checks, that changes. Access to protected apps can now depend on: User compliance status Policy acknowledgments MFA enrollment status Active employment status Many other external verification signals Access decisions are no longer limited to what's happening on the device. They reflect whether the user of the device has met required conditions across systems. How External Checks work Administrators configure an External Check by connecting Device Trust to a third-party system via API. That external system becomes a source of truth for a specific requirement, such as whether a user has completed training or acknowledged a required policy. When a user attempts to access a protected application: Device Trust evaluates device posture as it does today. Device Trust sends a request to the configured external system. The external system returns a simple result: pass or fail. Device Trust incorporates that result into the overall access decision. If the check passes, access proceeds normally. If the check fail ## Anonymous credentials: an illustrated primer DevFeed: [Anonymous credentials: an illustrated primer]() Original publisher: [Read original article]() Author: Matthew Green Published: 2026-03-02T17:29:36Z Content type: tutorial Language: en Sources: [Matthew Green]() Topics: [Authentication](), [Cryptography](), [Security & Privacy]() Tags: [ai](), [anonymous-credentials](), [artificial-intelligence](), [authentication](), [cryptography](), [cybersecurity](), [mfa](), [passwords](), [privacy](), [security](), [technology]() ### AI overview This primer introduces anonymous authentication as a computer-security problem and explains how websites use credentials, pseudonymous accounts, cookies, CAPTCHAs, MFA, and passkeys to control access. It argues that advertising-driven data collection and expanding age-verification laws are pushing more services toward identity checks, potentially reducing anonymous online use. ### Source excerpt This post has been on my back burner for well over a year. This has bothered me, since with every month that goes by, I become more convinced that anonymous authentication the most important topic we could be talking about as cryptographers. This isn't just because I love neat cryptography: it's that I don't trust ... Continue reading Anonymous credentials: an illustrated primer -> [Next page]()