Security Concepts

Internal

• Security
• OAuth 2.0 Concepts

Identity

The identity could be that of a human using the computer and running programs, or of a automation system. In the first case we qualify the identity as "end-user" or "user" identity, and in the second case we use the terms "system account" or "service account" identity. The identity can be proven by a certificate or by other means, such as providing a password.

Established Identity

An established identity is an identity proven by a trusted certificate.

End User Identity

A human user.

Platform Identity

The platform identity is the kind of identity information an entity that seeks attestation presents at the very beginning of the attestation process. Usually, this is some sort of hardware identity, which could be theoretically verified against an inventory. Also see Zero to One and the First Key Problem.

Trust

A claimed identity is useless if it is not trusted by the party.

Zero-to-One and the First Key Problem

There is always a moment in the processing of establishing trust when the entity that seeks attestation cannot present any trusted certificate yet, because it doesn't have one. This is the zero-to-one problem. Usually, the entity presents some sort of hardware identity, also referred to as platform identity, which could be theoretically verified against an inventory.

Public Key Cryptography

Public Key Cryptography, also known as asymmetrical cryptography

Private Key

Key Residency Attestation

Key residency attestation is the process by which one peer proves to another that a private key is stored in a certain way. Private keys stored in hardware are usually better protected than software private keys. This kind of attestation helps assessing risk, since a private key stored in hardware are less likely to be copied around.

Certificate

Certificates are used to prove identities.

Certificate Authority

https://en.wikipedia.org/wiki/Certificate_authority

Authentication

Authentication is the process of identifying a subject and verifying the authenticity of the identification information.

The most common authentication mechanism is username/password. Other mechanisms are available: public key, shared key, smart cards, etc.

In the context of JEE declarative security, the result of a successful authentication is called a principal.

Related subjects: Basic and Digest HTTP Authentication.

Authorization

Authorization is the mechanism for granting or denying access to a resource based on identity.

In JEE, this is usually implemented by matching a principal with a set of actions they are or are not allowed to perform. This mapping is referred as a role.

Encryption

TODO https://home.feodorov.com:9443/wiki/Wiki.jsp?page=CryptographicAlgorithms#EncryptionAndDecryption

SSL/TLS

TLS

SSO

TODO https://home.feodorov.com:9443/wiki/Wiki.jsp?page=SingleSign-On

LDAP

TODO https://home.feodorov.com:9443/wiki/Wiki.jsp?page=LDAP

Security Protocols

Authentication Protocols

• SAML
• OpenID Connect
• Kerberos

Authorization Delegation Protocols

• OAuth 2.0

Others

• WS-*

To Process

Identity Federation and Single Sign-On are related concepts.

Single Sign-On (SSO) systems allow a single user authentication process across multiple IT systems and organizations. SSO is a subset of federated identity management, as it relates only to authentication and technical interoperability.

User's presence in the system - means that the user identity is associated with the thread that is processing the user's request, and in a way, it is the user that "drives" the thread. The identity is associated with the thread in the form of a security context.

Authentication. The whole point of an authentication protocol is to tell whether the user is present in the system.

Identity Provider (IdP) and Relying Party (RP).

Authentication protocols, single sign-on, SAML.

Authorization.