Live data from Hacker News

OWASP Non-Human Identities Top 10

owasp.org

11–20 of 37 posts

Re: OWASP Non-Human Identities Top 10

#11
post #8
post #2

They are using some fancy wording, but this just seems to be about regular service accounts (i.e. "bots") when they are mixed with user accounts in a SoA setting. No AI needed.

I am confused with the wording. Is there an official description of Non-Human Identities? I only known service accounts, which pose similar threat. Both AI and Humans can use service accounts and api-keys to pose the same threats. But it's ultimately known and wide-spread as service accounts from what I know. Is non-human identity referring to a special case or attack vector?

I think it's just a fancy description for service accounts, but possibly extended to any kind of access that is used for machine-to-machine interaction rather than for users; I guess tokens used by IoT devices to access an API would also count as NHI. I guess that "Non-Human" doesn't imply any AI around (nor other animals or extraterrestrials, although I guess nobody thought that...).

Re: OWASP Non-Human Identities Top 10

#12
post #8
post #2

They are using some fancy wording, but this just seems to be about regular service accounts (i.e. "bots") when they are mixed with user accounts in a SoA setting. No AI needed.

I am confused with the wording. Is there an official description of Non-Human Identities? I only known service accounts, which pose similar threat. Both AI and Humans can use service accounts and api-keys to pose the same threats. But it's ultimately known and wide-spread as service accounts from what I know. Is non-human identity referring to a special case or attack vector?

Here is how OWASP define it:

> Non-human identities (NHIs) are used to provide authorization to software entities such as applications, APIs, bots, and automated systems to access secured resources. Unlike human identities, NHIs are not controlled or directly owned by a human. Their identity object and authentication often work differently to human, and common human user security measures do not apply to them.

https://owasp.org/www-project-non-human-identities-top-10/20...

Re: OWASP Non-Human Identities Top 10

#14
post #2

They are using some fancy wording, but this just seems to be about regular service accounts (i.e. "bots") when they are mixed with user accounts in a SoA setting. No AI needed.

they kind of mention various examples throughout, e.g.:

- such as service accounts and access keys

- such as API keys, tokens, encryption keys, and certificates

- typically achieved using static credentials or OpenID Connect (OIDC)

- sensitive NHIs such as API keys, tokens, encryption keys, and certificates

Re: OWASP Non-Human Identities Top 10

#15
post #13

A better link would be the dedicated site for it, also contains introduction which describes what NHI are: https://owasp.org/www-project-non-human-identities-top-10/20...

Ok, we've changed to that from https://owasp.org/www-project-non-human-identities-top-10/. Thanks!

Re: OWASP Non-Human Identities Top 10

#20
TIL that OWASP has a bunch of Top 10 projects other than application security. Some others I found:

- Top 10 for LLMs - https://owasp.org/www-project-top-10-for-large-language-mode...

- Top 10 for OT - https://ot.owasp.org/

- Top 10 for Smart Contracts - https://owasp.org/www-project-smart-contract-top-10/

- Top 10 for Open Source Software - https://owasp.org/www-project-open-source-software-top-10/

Post reply on HN