Posted in Identity and Access Management

The DHS breach published last week didn't leak passwords. It leaked something attackers value almost as…

Craig M. — Chief Product Officer @ Cyberr®

The DHS breach published last week didn't leak passwords. It leaked something attackers value almost as much: the map.

Over 40,000 staff records, reportedly pulled from the department's Okta sign-on system. Names and phone numbers, yes. But also which apps each person can access and which Active Directory groups they belong to, including groups named after specific surveillance tools.

Okta says its systems weren't compromised, and how the data was taken is still unknown. The lesson doesn't depend on that.

Your identity provider is the most complete org chart you own. It tells an attacker who has admin, who touches finance systems, and which project names to drop into a phishing email. Most teams protect credentials and treat directory data as harmless metadata.

What I'd check this week:

→ Entra ID: by default, member users can read the whole directory through Graph. Review whether "allowedToReadOtherUsers" should stay on for your tenant.

→ Okta: API tokens inherit the full rights of the admin who created them. Inventory them, and move integrations to scoped OAuth service apps (e.g. okta.users.read only).

→ Alert on bulk directory reads: large paginated user or group pulls from one token or account in a short window.

→ Group names are intel. "Project-X-Admins" tells an outsider exactly whom to target.

Least privilege usually stops at "what can this person change?" It should also cover "what can this person see?"

Who in your org can export the full user and group list today, and would you notice if they did?

#IdentitySecurity #Okta #EntraID

5 reactions · 0 comments

Topics: #identitysecurity, #okta, #entraid

Read and join the discussion on Cyberr