saml
for security engineers, auth developers
Why this scored 15
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 130
SAML: A fractal of bad design
Points out systemic design flaws in SAML that can lead to security vulnerabilities. · for security engineers, auth architects
lobstersSteady 2 · samlsecurity10d ago - 222
How SAML works, and why XML signature wrapping keeps breaking it
Explains SAML flow and why XML signature wrapping remains a recurring vulnerability. · for security engineers, auth developers
devtoSteadysecurity58m ago - 316
SAML: A fractal of bad design
Highlights design flaws in SAML that can affect authentication implementations. · for security engineers
hackernewsSteadysecurity10d ago