Security & Privacy Engineering

AppSec, threat modeling, SBOMs, secrets, SAST/DAST, authN/Z, and privacy by design.

  • 4 Subtopics
  • 14 Tracked terms
  • Last 30 days Feed window

Inside Security & Privacy Engineering

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Security & Privacy Engineering

dev.to
705 words

OAuth Test Tokens Need a Trust Boundary

OAuth tests often stop at “the token was returned.” That proves the protocol completed, but it does not prove that the right client, tenant, user, or scope received access. A test token can be cryptographically valid and still represent a…

dev.to
708 words

OAuth Test Users Need a Privacy Budget

OAuth test accounts are often treated as disposable infrastructure. A script creates a user, requests a verification email, follows a link, exchanges a code, and deletes the account. The flow looks harmless because the data is synthetic. But synthetic does…

infoq.com
910 words

Server-Side DPoP and Token Exchange in Spring Security 7

Live Webinar and Q&A: From Tokens to Features: Architecting Cost Attribution for AI-Assisted Engineering (Oct 29, 2026) Save Your Seat Discover how to keep software evolvable as systems, technology, and teams shift. This edition explores agentic fitness functions for semantic drift, treating…

Token authentication final cut.

This article is finalization of two previous pieces one and two. Token authentication is realization of “Pay for registration” concept. This concept has several benefits: no CAPTCHA which collects your data, no stupid and over-complicated OAUTH, no other stupid things…