#identitysecurity
Live, measured metrics for the hashtag #identitysecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #identitysecurity
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-10-17 22:52 UTC5 uses by 5 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-17 22:52 UTCNo related tags with measured usage found for #identitysecurity.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-17 22:52 UTCEverything below is measured over the latest 40 public posts (spanning ~962 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (39) · French (1)
Avg boosts / post: 0.7
Top of the latest posts
BleepingComputer covered this yesterday: Microsoft reports extortion groups including ShinyHunters and Helix are using passkey and SSO enrollment lures to break into corporate Microsoft 365 accounts. Nobody is cracking passkeys. They are ta
After a phishing engagement, everyone fixates on the click rate. It fades fast. What changes config on Monday is the authentication gap: a weak MFA fallback, a Conditional Access policy that did not apply where assumed, a passkey downgrade
Passkeys rolled out. MFA enforced. User consent restricted to admin approval. Someone signs in normally on the real Microsoft login page, pastes the address-bar URL into a page that says it needs one more verification step, and their sessio
#identitysecurity across platforms
every network with a public tag surfaceFollow #identitysecurity straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/identitysecurity