# Security, Privacy and Abuse Prevention A Google Research topic covering computer security, data privacy, and online-abuse prevention research. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## KYC Onboarding: From Signup to Accepting Payments DevFeed: [KYC Onboarding: From Signup to Accepting Payments]() Original publisher: [Read original article]() Author: Deepak Jangir Published: 2026-09-17T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Requirements](), [Security, Privacy and Abuse Prevention](), [account](), [Website]() Tags: [account](), [business](), [credentials](), [guide](), [onboarding](), [payments](), [saas](), [verification](), [website]() ### AI overview This guide explains KYC onboarding for online sellers, including the identity, eligibility, ownership, bank account, and website checks payment providers may perform before enabling payments and payouts. It outlines the onboarding sequence, common causes of delays, and differences between freelancers and companies. ### Source excerpt What KYC onboarding involves when you sign up to sell online: the stages, the documents, why applications stall, and how it differs for freelancers and companies. ## Online Gambling Fraud Prevention for iGaming Operators DevFeed: [Online Gambling Fraud Prevention for iGaming Operators]() Original publisher: [Read original article]() Author: Ben Price Published: 2026-09-11T21:00:00Z Content type: article Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Bot](), [Sports]() Tags: [2026](), [bonus-abuse](), [bots](), [fraud-prevention](), [gambling](), [gambling-fraud](), [igaming](), [igaming-fraud-prevention](), [online-gambling](), [online-gambling-fraud](), [prevent-fraud](), [sports-betting-fraud]() ### AI overview The article examines fraud in U.S. iGaming and sportsbook operations, focusing on signup, deposit, and cashout risks. It highlights organized bonus abuse involving synthetic identities, stolen credentials, linked accounts, bots, device farms, and fabricated identities. ### Source excerpt In just Q1 2026, U.S. iGaming has generated about $3.04 billion, marking over 20% growth year-over-year and nearly $1 billion in April 2026 alone. For the full 2025 year, iGaming hit over $10 billion in revenue, up 27.6% over the previous year. With it being such a profitable industry, there's no wonder why it's ripe [...] The post Online Gambling Fraud Prevention for iGaming Operators appeared first on Sift. ## iGaming Fraud Prevention: Key Strategies to Implement DevFeed: [iGaming Fraud Prevention: Key Strategies to Implement]() Original publisher: [Read original article]() Author: Ben Price Published: 2026-09-14T21:00:00Z Content type: article Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Exploit](), [math]() Tags: [2025](), [2026](), [acquisition](), [bonus-abuse](), [customer](), [fraud-prevention](), [gaming-fraud](), [igaming](), [igaming-fraud](), [igaming-fraud-prevention](), [industrial](), [marketing](), [multi-account-abuse](), [multi-accounting-detection](), [multi-accounting-fraud](), [network](), [prevent-fraud](), [revenue](), [synthetic](), [time](), [trust-and-safety](), [verification](), [volume]() ### AI overview This article explains how bonus abuse and multi-accounting have become major sources of iGaming fraud. It describes fraudsters exploiting promotional offers through repeated registrations, synthetic identities, stolen credentials, device farms, residential proxies, and synthetic documents, and argues that operators should justify prevention spending by measuring protected revenue. ### Source excerpt While every operator budgets for promotions as a customer acquisition cost, very few budget for the version of that cost that never converts into a real player. Bonus abuse and multi-accounting now account for the single largest fraud category in iGaming, making up 64% of fraud according to a recent study. But unlike chargebacks or [...] The post iGaming Fraud Prevention: Key Strategies to Implement appeared first on Sift. ## What is Trust and Safety? DevFeed: [What is Trust and Safety?]() Original publisher: [Read original article]() Author: Ben Price Published: 2026-08-28T23:00:00Z Content type: article Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Transactions](), [account takeover]() Tags: [account-takeover](), [authentication](), [chargebacks](), [digital-platforms](), [digital-trust](), [digital-trust-safety](), [fraud-detection](), [fraud-prevention](), [payment-fraud](), [trust](), [trust-and-safety](), [trust-safety]() ### AI overview This article explains Trust and Safety as an organizational capability for protecting digital platforms, users, transactions, and interactions. It describes how the discipline brings together fraud prevention, content moderation, abuse prevention, and policy enforcement across the user journey, including payment fraud, fake account creation, account takeover, and content integrity. ### Source excerpt Trust and Safety is the practice of protecting the integrity of digital platforms, their users, and the transactions and interactions that take place on them. As a discipline, trust and safety spans fraud prevention, content moderation, abuse prevention, and policy enforcement across the full user journey. For fraud teams and platform operators, it represents a [...] The post What is Trust and Safety? appeared first on Sift. ## Know Your Super Bowl: How Fraud Teams Can Prepare for Peak Payment Volume Spikes DevFeed: [Know Your Super Bowl: How Fraud Teams Can Prepare for Peak Payment Volume Spikes]() Original publisher: [Read original article]() Author: Sift Trust and Safety Team Published: 2026-09-02T16:15:14Z Content type: opinion Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Finance]() Tags: [agentic-commerce-fraud](), [business](), [digital-trust-safety](), [fraud-prevention](), [fraud-prevention-planning](), [incident-response-plan](), [payment-fraud](), [payment-volume-spikes](), [peak-payment-volume](), [product](), [seasonal-fraud-trends](), [shared-payment-credentials]() ### AI overview The article explains how fraud teams can prepare for predictable and unexpected payment volume spikes. It recommends identifying business-specific peak periods, coordinating forecasts and risk tolerance in advance, and tightly controlling fraud-rule changes around high-volume events. ### Source excerpt Every business has a Super Bowl. It just isn't always the Super Bowl. For one company, it might be Black Friday. For another, Valentine's Day. For others, the biggest payment spike of the year comes from a product launch, ticket release, or viral moment nobody saw coming. That was the premise of a recent Merchant [...] The post Know Your Super Bowl: How Fraud Teams Can Prepare for Peak Payment Volume Spikes appeared first on Sift. ## What Stripe data shows about fraud at AI startups DevFeed: [What Stripe data shows about fraud at AI startups]() Original publisher: [Read original article]() Author: Jacob Meltzer; Samuel Bakouch Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Stripe Blog]() Topics: [Artificial Intelligence](), [stripe](), [Security, Privacy and Abuse Prevention](), [multi-account abuse]() Tags: [ai](), [fraud](), [multi-account-abuse](), [stripe]() ### AI overview Stripe reports that AI startups experienced higher attempted transaction fraud and multi-account abuse than startups overall. Its data found a 4.3x higher attempted transaction fraud rate in Q3 2025, falling to 2.6x by Q1 2026. ### Source excerpt We analyzed attempted fraud rates and customer abuse patterns on Stripe over the past year and found that AI companies faced 4.3x more fraud attempts than startups overall in Q3 2025. ## One Decade of Rustls: Evolution, Benchmarks, and Future Roadmap DevFeed: [One Decade of Rustls: Evolution, Benchmarks, and Future Roadmap]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-12T07:07:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Cryptography](), [Security, Privacy and Abuse Prevention](), [interoperability](), [Refactoring]() Tags: [benchmarks](), [development](), [memory-leaks](), [memory-safety](), [news](), [open-source](), [performance](), [post-quantum](), [release](), [retrospective](), [rust](), [rustls-one-decade](), [security](), [tls]() ### AI overview Rustls marks its tenth anniversary with a retrospective on its growth, funding, security work, and performance. The article compares Rustls 0.23.37 with OpenSSL and BoringSSL and notes architectural changes planned for version 0.24. ### Source excerpt Rustls, a Rust TLS library, marks its decade-long progression from a grassroots project to a funded open-source initiative. Key contributions from organisations boosted development, resulting in features like post-quantum cryptography and robust performance. The upcoming 0.24 release aims to enhance architecture and flexibility, including new input buffering and improved session handling By Olimpiu Pop ## How to Connect to HMRC's Making Tax Digital API: A Beginner's Guide DevFeed: [How to Connect to HMRC's Making Tax Digital API: A Beginner's Guide]() Original publisher: [Read original article]() Author: Solomon Amos Published: 2026-09-11T22:10:33Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [API](), [Security, Privacy and Abuse Prevention]() Tags: [api](), [apis](), [code](), [guide](), [hmrc](), [hmrc-tax-filing](), [hmrc-tax-returns](), [how-to](), [integration](), [mtd](), [node](), [oauth](), [tax](), [tax-return](), [typescript]() ### AI overview A beginner-friendly guide to connecting software to HMRC's Making Tax Digital API. It explains the MTD context, sandbox setup, OAuth 2.0 authentication, fraud prevention headers, and authenticated API calls using Node and TypeScript. ### Source excerpt If you write software for anyone who pays UK tax, sooner or later you'll need to talk to HMRC. Making Tax Digital (MTD) for Income Tax went live on 6 April 2026, and it's already mandatory for self-em ## Security updates for Thursday DevFeed: [Security updates for Thursday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-10T13:14:35Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security, Privacy and Abuse Prevention](), [.NET](), [Boot Process, passwd, systemd](), [Grafana]() Tags: [ansible](), [grafana](), [kernel](), [linux](), [net](), [opentelemetry](), [oracle](), [prometheus](), [python](), [redis](), [rust](), [security](), [systemd](), [ubuntu](), [updates]() ### AI overview A roundup of security updates issued by several Linux distributions for a range of packages. ### Source excerpt Security updates have been issued by AlmaLinux (389-ds-base, ansible-core, buildah, expat, glib2, gpsd, gpsd-minimal, gzip, kernel, kernel-rt, opentelemetry-collector, osbuild-composer, perl-DBI, python-lxml, python3.12-lxml, qt5-qtbase, thunderbird, valkey, vim, and xz), Debian (pyasn1), Fedora (darktable, freeipa, freerdp2, gdk-pixbuf2, GitPython, libsoup3, openssl, perl-Net-DNS, rust-ppmd-rust, samba, and valkey), Mageia (ceph, firefox, nss, perl-DBI, thunderbird, and wget), Oracle (389-ds-base, buildah, expat, git-lfs, glib2, glibc, gpsd, gpsd-minimal, grafana-pcp, kernel, libssh, nginx, perl-GD, python3.14-cryptography, redis:7, skopeo, thunderbird, valkey, xmlrpc-c, and xz), Slackware (xz), SUSE (bzip2, cpio, curl, dracut, fuse-overlayfs, golang-github-vpenso-prometheus_slurm_exporter, helm, java-1_8_0-ibm, kbfs, kernel, kernel-devel, libopenslide-devel, libsoup, libssh2_org, libusb-1_0, libvirt, libzypp, zypper, mcphost, multipath-tools, NetworkManager, opensc, openssl-3, perl-Net-DNS, python-aiohttp, python-Authlib, python-pip, python-sqlparse, python313-dnspython, python313-idna, rpcbind, sssd, strongswan, systemd, tomcat11, ucode-intel, and wget), and Ubuntu (dotnet8, dotnet10, ffmpeg, flatpak, netty, and perl). ## A decade of Rustls DevFeed: [A decade of Rustls]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-09T18:11:54Z Content type: news Language: en Sources: [LWN.net]() Topics: [releases](), [Cryptography](), [Security, Privacy and Abuse Prevention]() Tags: [api](), [blog](), [compression](), [cryptography](), [performance](), [post-quantum](), [releases](), [tls]() ### AI overview A retrospective on ten years of the Rustls TLS-library project, covering its release history, the forthcoming 0.24 and eventual 1.0 releases, and features added in the stable 0.23 line. ### Source excerpt Joe Birr-Pixton has written a blog post reflecting on a decade of the Rustls TLS-library project and looking ahead to the upcoming 0.24 release and an eventual 1.0 release. Rustls began with a first commit on May 2, 2016. Progress was quick: a month later, on June 5, it could interoperate with most sites on the web. The first release, 0.1.0, followed on August 27, 2016 - less than four months after the first commit. [...] From the 0.1.0 release, the project moved through a long series of releases over the following eight years, building out functionality, hardening and refining the API. That sequence of release lines culminated in 0.23, released on February 29, 2024. The 0.23 release line has been a stable one: in the time since, it has seen 43 non-breaking releases. That stability didn't come with stagnation. The 0.23 line delivered a wide range of important features, including a FIPS-certified cryptography option, certificate compression, Encrypted ClientHello, post-quantum cryptography, and performance improvements. ## Use a local and open source code assistant DevFeed: [Use a local and open source code assistant]() Original publisher: [Read original article]() Author: Seth Kenlon Published: 2026-09-09T14:01:45Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [ai-coding](), [Local AI](), [Open Source Models & Datasets](), [Large Language Model](), [Model Context Protocol](), [ide](), [Security, Privacy and Abuse Prevention](), [Command-line interface](), [Homebrew](), [Linux](), [macOS]() Tags: [ai-coding](), [ai-inference](), [artificial-intelligence](), [command-line](), [developer-tools](), [ide](), [linux](), [llm](), [local-ai](), [macos](), [model-context-protocol](), [ollama](), [open-source](), [privacy]() ### AI overview This Red Hat Developer article explains how to use OpenCode as a local, open source AI coding assistant. It covers OpenCode's terminal, desktop, and IDE extension interfaces, its use of the Model Context Protocol, installation requirements, and the need to configure an LLM. For privacy-conscious local development, it recommends open source local AI tools such as Ollama or OpenVINO. ### Source excerpt There's a lot of excitement about AI coding assistants, but many of the available options either aren't open source, or don't respect your data privacy by sending what you're working on to the cloud for processing. If you're looking for an alternative to closed AI, then you need an open coding assistant and an open source IDE. The post Use a local and open source code assistant appeared first on Red Hat Developer. ## OSPAR 2026 report now available with 167 services in scope DevFeed: [OSPAR 2026 report now available with 167 services in scope]() Original publisher: [Read original article]() Author: James Chang Published: 2026-09-04T18:13:04Z Content type: news Language: en Sources: [AWS Security Blog]() Topics: [Security, Privacy and Abuse Prevention](), [Cryptography]() Tags: [amazon-web-services-aws](), [announcements](), [compliance](), [cryptography](), [financial-services](), [foundational-100](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS completed its annual OSPAR assessment under the OSPAR 2.0 framework. The certification covers 167 AWS services in the Asia Pacific (Singapore) Region and is intended to support customer compliance due diligence. ### Source excerpt We're pleased to confirm the successful completion of our annual Amazon Web Services (AWS) Outsourced Service Provider's Audit Report (OSPAR) assessment on July 29, 2026, in line with the OSPAR version 2.0 framework. The Association of Banks in Singapore (ABS) established the Guidelines on Control Objectives and Procedures for Outsourced Service Providers (ABS Guidelines) to [...] ## Panopto Alternatives for Higher Education: Comparing Kaltura, IBM Video Streaming, and Dacast DevFeed: [Panopto Alternatives for Higher Education: Comparing Kaltura, IBM Video Streaming, and Dacast]() Original publisher: [Read original article]() Author: Jon Whitehead Published: 2026-09-04T11:55:41Z Content type: comparison Language: en Sources: [DaCast]() Topics: [Streaming](), [Security, Privacy and Abuse Prevention](), [Accessibility](), [data](), [ibm](), [Canvas]() Tags: [accessibility-compliance](), [comparison](), [data](), [data-privacy](), [ibm](), [streaming](), [the-video-experts-blog](), [video]() ### AI overview This comparison guide evaluates Panopto alternatives for higher education, focusing on Kaltura, IBM Video Streaming, and Dacast. It explains that university buyers should consider LMS integration, student data privacy, accessibility compliance, procurement requirements, pricing, bandwidth, and support for public-facing content. ### Source excerpt By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated September 2026 Choosing a video streaming platform for a university isn't the same evaluation as picking one for a corporate training program or an individual course creator. University IT and AV teams have to weigh LMS integration, student data privacy, accessibility [...] The post Panopto Alternatives for Higher Education: Comparing Kaltura, IBM Video Streaming, and Dacast appeared first on Dacast. ## Announcing Chainguard container images for Go 1.27 DevFeed: [Announcing Chainguard container images for Go 1.27]() Original publisher: [Read original article]() Published: 2026-08-31T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [container images](), [Go Language](), [Cryptography](), [Deployment](), [Security, Privacy and Abuse Prevention](), [Post-Quantum]() Tags: [chainguard](), [container](), [container-images](), [cryptography](), [deployment](), [fedramp](), [fedramp-ato](), [fips](), [go](), [hardening](), [images](), [post-quantum](), [release]() ### AI overview Chainguard announces three Go 1.27 container images: go, go-fips, and go-openssl-fips. The options differ in their FIPS-validated cryptography, including whether cryptography is built in or selected at deployment time. ### Source excerpt Chainguard simplifies Go 1.27 with three images and a new option to choose FIPS-validated cryptography at deployment without recompiling. ## Why a cryptographic inventory is key for addressing the quantum computing threat DevFeed: [Why a cryptographic inventory is key for addressing the quantum computing threat]() Original publisher: [Read original article]() Author: Christopher Day Published: 2026-08-28T14:01:00Z Content type: article Language: en Sources: [Tenable Blog]() Topics: [Cryptography](), [Security, Privacy and Abuse Prevention](), [migration](), [Security Attacks]() Tags: [algorithms](), [attacks](), [cryptographic](), [cryptography](), [encryption](), [migration](), [post-quantum](), [quantum](), [quantum-computing](), [security]() ### AI overview The article explains how a cryptographic inventory and phased migration to quantum-resistant cryptography can address the risk that future quantum computers pose to public-key algorithms. It highlights harvest-now, decrypt-later attacks, the vulnerability of RSA, ECC, and Diffie-Hellman to Shor's Algorithm, and the expected resilience of AES-256. ### Source excerpt When quantum computers become generally available, they'll be able to crack current public-key cryptographic algorithms, putting digitally stored and transmitted data at risk. But the threat already exists, as attackers use the "harvest now, decrypt later" tactic. Discover why building a comprehensive cryptographic inventory and executing a phased operational strategy are critical for protecting your data against quantum computing attacks. Key takeaways Quantum computing risks are an operational threat today due to "harvest now, decrypt later" (HNDL) tactics, in which adversaries actively harvest and store encrypted data to decrypt it retroactively once quantum capabilities mature. When run on a quantum computer that's powerful enough, Shor's Algorithm will break foundational asymmetric infrastructure like the RSA, ECC, and Diffie-Hellman algorithms, although symmetric encryption standards like AES-256 are expected to remain secure against quantum attacks. Globally, more regulatory bodies are starting to mandate a comprehensive cryptographic inventory, making absolute visibility across the digital environment a prerequisite for an orderly post-quantum migration. Transitioning to quantum-resistant cryptography requires a phased operational strategy spanning discovery, prioritization, remediation, and verification. The quantum threat to modern security architecture Future quantum computers will represent a threat to the foundational security architecture that protects digital data. For decades, the global economy, national security apparatus, and critical infrastructure have relied on asymmetric cryptography, specifically RSA and elliptic curve cryptography (ECC), to secure data in transit, authenticate identities, and protect digital signatures. The mathematical difficulty of factoring large integers or solving discrete logarithm problems has long provided a robust shield against cyber attacks launched using conventional computing capabilities. However, the rapid mat ## How WhatsApp Implemented Passkey Authentication for Faster, Phishing-Resistant Sign-In DevFeed: [How WhatsApp Implemented Passkey Authentication for Faster, Phishing-Resistant Sign-In]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-27T17:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Passkeys](), [Authentication](), [Security, Privacy and Abuse Prevention](), [Cryptography](), [Android]() Tags: [api](), [authentication](), [credential-theft](), [cryptography](), [developer](), [google](), [meta](), [sign-in](), [whatsapp]() ### AI overview The article describes how WhatsApp implemented passkey-based authentication to provide faster sign-ins and reduce phishing and credential-theft risks. It explains the use of public-private key cryptography, biometric or screen-lock authentication, and Android's Credential Manager API. ### Source excerpt Posted by Niharika Arora, Senior Developer Relations Engineer, Tracy Agyemang, Product Marketing Manager, Google and Mayank Manuja, Android Engineer, Meta WhatsApp is the world's largest messaging platform, serving billions of users globally. It is the default communication tool for people across diverse regions, connecting users through private, reliable, and secure messaging. "What excites me most is the sheer scale of WhatsApp's impact. Even a small improvement to WhatsApp touches billions of users worldwide," says Mayank Manuja, an Android Engineer on the WhatsApp Registration and Access team who led the design and implementation of passkey-based authentication for WhatsApp. Building for an audience of this magnitude requires navigating a vast range of network conditions, device capabilities, and levels of digital literacy. Recognizing the potential early, WhatsApp committed to adopting passkeys in 2023, becoming one of the first major consumer apps to integrate the technology. By implementing passkeys, WhatsApp aimed to provide a fast, phishing-resistant option that significantly reduces user friction while providing robust protection against account takeovers and credential theft. A user creating a passkey on WhatsApp for faster, more secure sign-ins. The Decision to Adopt Passkeys For WhatsApp, offering multiple access methods is key to making it easier for users to stay connected and regain access when needed. Passkeys offer users a streamlined, one-tap login experience that eliminates phishing risks and functions reliably even in regions where OTP message delivery can be inconsistent. Underneath, passkeys leverage public-private key cryptography to replace manual entry with biometric or screen lock authentication. This workflow drastically improves sign-in speeds by reducing the process to a single tap via a unified, bottom-sheet interface that keeps users engaged within the app's context. The benefits are twofold: passkeys offer users a streamlined login e ## How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys DevFeed: [How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-27T17:00:00Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Passkeys](), [Authentication](), [Security, Privacy and Abuse Prevention](), [Cryptography](), [Android](), [App](), [API]() Tags: [android](), [api](), [app](), [authentication](), [credential-theft](), [cryptography](), [phishing](), [scale](), [whatsapp]() ### AI overview WhatsApp's adoption of passkeys provides a fast, phishing-resistant sign-in method for its large global user base. The article explains how passkeys use public-private key cryptography with biometric or screen-lock authentication, reduce reliance on inconsistent SMS OTP delivery, and simplify implementation through Android's Credential Manager API. ### Source excerpt Posted by Niharika Arora, Senior Developer Relations Engineer, Tracy Agyemang, Product Marketing Manager, Google and Mayank Manuja, Android Engineer, Meta WhatsApp is the world's largest messaging platform, serving billions of users globally. It is the default communication tool for people across diverse regions, connecting users through private, reliable, and secure messaging. "What excites me most is the sheer scale of WhatsApp's impact. Even a small improvement to WhatsApp touches billions of users worldwide," says Mayank Manuja, an Android Engineer on the WhatsApp Registration and Access team who led the design and implementation of passkey-based authentication for WhatsApp. Building for an audience of this magnitude requires navigating a vast range of network conditions, device capabilities, and levels of digital literacy. Recognizing the potential early, WhatsApp committed to adopting passkeys in 2023, becoming one of the first major consumer apps to integrate the technology. By implementing passkeys, WhatsApp aimed to provide a fast, phishing-resistant option that significantly reduces user friction while providing robust protection against account takeovers and credential theft. A user creating a passkey on WhatsApp for faster, more secure sign-ins. The Decision to Adopt Passkeys For WhatsApp, offering multiple access methods is key to making it easier for users to stay connected and regain access when needed. Passkeys offer users a streamlined, one-tap login experience that eliminates phishing risks and functions reliably even in regions where OTP message delivery can be inconsistent. Underneath, passkeys leverage public-private key cryptography to replace manual entry with biometric or screen lock authentication. This workflow drastically improves sign-in speeds by reducing the process to a single tap via a unified, bottom-sheet interface that keeps users engaged within the app's context. The benefits are twofold: passkeys offer users a streamlined login e ## PSD3 Explained: What SaaS and Digital Sellers Need to Know DevFeed: [PSD3 Explained: What SaaS and Digital Sellers Need to Know]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-08-27T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Security, Privacy and Abuse Prevention]() Tags: [article](), [compliance](), [eu](), [europe](), [guide](), [legal](), [payments](), [saas]() ### AI overview A plain-English guide to PSD3 and the PSR for SaaS products and digital sellers serving European customers. It explains that the reforms are close to final but not yet law, distinguishes PSD3's licensing and supervision rules from the PSR's checkout-related conduct rules, and outlines implications for payment providers, fraud prevention, and payment execution. ### Source excerpt A plain-English PSD3 and PSR guide for SaaS founders: where the legislation stands in 2026, what changes on fraud liability and SCA, and what it means for checkout. ## Bringing ChatGPT for Teachers to more U.S. school districts DevFeed: [Bringing ChatGPT for Teachers to more U.S. school districts]() Original publisher: [Read original article]() Published: 2026-08-26T10:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Artificial Intelligence](), [AI Strategy](), [Security, Privacy and Abuse Prevention](), [FIRST]() Tags: [ai](), [ai-adoption](), [chatgpt](), [education](), [openai](), [privacy](), [product](), [responsible-ai](), [support]() ### AI overview OpenAI is expanding ChatGPT for Teachers to 55 additional U.S. school systems across 20 states, providing free access, training, and support to more than 100,000 additional educators and staff. The announcement also introduces a 16-state data privacy agreement intended to simplify responsible adoption by school districts. ### Source excerpt ChatGPT for Teachers is expanding to 55 U.S. school systems, bringing secure AI tools, training, and support to over 100,000 more educators and staff. ## Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java DevFeed: [Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java]() Original publisher: [Read original article]() Author: Poonam Parhar Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [Inside Java]() Topics: [Cryptography](), [fips 140-3](), [openssl](), [Java](), [Encryption](), [Security, Privacy and Abuse Prevention]() Tags: [cryptographic](), [cryptography](), [fips](), [fips-140-3](), [java](), [openssl](), [oracle](), [security](), [standard]() ### AI overview Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module and exposes cryptographic services through Java Cryptography Architecture (JCA). ### Source excerpt Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module, making cryptographic services available through the standard Java Cryptography Architecture (JCA) framework. ## Offering Zero Data Retention for frontier models DevFeed: [Offering Zero Data Retention for frontier models]() Original publisher: [Read original article]() Published: 2026-08-19T19:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [OpenAI](), [Responsibility & Safety](), [Artificial Intelligence](), [Security, Privacy and Abuse Prevention](), [API](), [Monitoring]() Tags: [agentic](), [ai](), [ai-agents](), [ai-safety](), [api](), [company](), [data](), [enterprise](), [monitoring](), [openai](), [privacy](), [retention](), [safety](), [security]() ### AI overview OpenAI reaffirms Zero Data Retention for eligible API customers and previews Private Safety Processing, which analyzes patterns across related interactions through automated systems without exposing prompts or responses to OpenAI personnel. The approach is intended to support safety monitoring for complex and agentic tasks while preserving customer control over sensitive content. ### Source excerpt OpenAI reaffirms Zero Data Retention for eligible API customers and previews Private Safety Processing for advanced AI safety without compromising data privacy. ## Discord Update: August 11, 2026 Changelog DevFeed: [Discord Update: August 11, 2026 Changelog]() Original publisher: [Read original article]() Author: Clyde Published: 2026-08-11T00:00:00Z Content type: release Language: en Sources: [Discord Blog]() Topics: [changelog](), [Discord](), [App](), [Electron](), [cpu](), [Messaging](), [Security, Privacy and Abuse Prevention]() Tags: [app](), [apps](), [changelog](), [cpu](), [customization](), [data](), [discord](), [messaging](), [mobile](), [os](), [privacy](), [tools](), [update](), [updates]() ### AI overview Discord's August 11, 2026 changelog highlights new desktop formatting tools, profile privacy and customization options, friend-request notes, spoiler channels, game mentions, Meta Quest support, and ongoing settings improvements. The desktop client also upgraded to Electron 42, with incremental CPU usage improvements. ### Source excerpt Here's the Discord Changelog from August 11, 2026, so you can stay informed on what's new in recent app updates! ## Keleusma Research Spike: What Happens When Error Correction Meets a Signature DevFeed: [Keleusma Research Spike: What Happens When Error Correction Meets a Signature]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-10T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [Security, Privacy and Abuse Prevention](), [Cryptography](), [Code](), [Compiler]() Tags: [bytecode](), [compiler](), [compilers](), [cryptographic](), [engineering](), [integrity](), [research](), [security](), [test](), [verification]() ### AI overview This case study examines how combining error correction with cryptographic signatures can create an unsafe verification order. Exhaustive analysis of bit errors shows that some damaged inputs are incorrectly repaired or reported as clean, so a clean correction result does not establish integrity. ### Source excerpt A file carries an error-correcting code so that a flipped bit can be repaired, and a cryptographic signature so that a changed byte is refused. Both are ordinary. Putting them in the same file forces a choice that neither feature announces, and one of the two answers is sound only under an assumption that the error-correcting code exists because it is false. The uncomfortable part is that the two answers are indistinguishable on every input anybody tests. An undamaged file behaves identically under both. They diverge only on damaged input, and damaged input is the case the error-correcting code exists for and the case no test suite exercises, because producing it requires deliberately corrupting your own artefact. Enumerating the fault space of a single 64-bit word exhaustively, rather than sampling it, gives four numbers that decide the design. The space is small enough to enumerate because the number of ways to flip $w$ bits out of 64 is a binomial coefficient, and for $w \le 4$ it stays under a million. \[\binom{64}{1} = 64, \quad \binom{64}{2} = 2{,}016, \quad \binom{64}{3} = 41{,}664, \quad \binom{64}{4} = 635{,}376\] flipped bits patterns repaired exactly wrongly "repaired" invisible 1 64 64 0 0 2 2,016 0 0 0 3 41,664 0 23,364 (56.08%) 0 4 635,376 0 0 5,133 (0.81%) Three flipped bits are reported as a successful repair 56.08 percent of the time, and the repair is wrong every time it happens. Four flipped bits are, 5,133 times, completely invisible, because the code reports the word as clean when the error pattern is itself a valid codeword. The consequence is one sentence, and everything else in this article is either its derivation or its implications. The corrector is not an authority on whether it corrected, and a clean report from it is not evidence of integrity. What this is a case study of The setting is the bytecode format for Keleusma, a language whose value proposition is that a program's worst-case time and memory can be proven before it runs, and wh ## Essential legal requirements for websites and how to meet them DevFeed: [Essential legal requirements for websites and how to meet them]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-08-07T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [web design](), [Security, Privacy and Abuse Prevention](), [tenant data protection](), [data](), [Software as a service]() Tags: [article](), [b2b](), [compliance](), [enterprise](), [legal](), [privacy](), [strategy](), [web-design]() ### AI overview This article explains how website legal requirements vary by site type, audience, industry, and publication location. It introduces privacy, data protection, accessibility, and jurisdiction-specific compliance considerations, including CCPA, GDPR, and HIPAA. ### Source excerpt Learn how to navigate legal requirements for websites, which ones apply to your type of site, and what you'll need to stay ready for future legal changes. [Next page]()