To validate Web sites, transactions, transaction participants, clients, and network services—various forms of identity services—have been deployed on networks.
Ticket or token providing services, certificate servers, and other trust mechanisms all provide identity services that can be pushed out of private networks and into the cloud.
Identity protection is one of the more expensive and complex areas of network computing.
Hundreds of messages on a network every minute are checking identity, and every Ethernet packet contains header fields that are used to identify the information it contains.
Identity as a Service (IDaaS) may include any of the following:
- Authentication services (identity verification)
- Directory services
- Federated identity
- Identity governance
- Identity and profile management
- Policies, roles, and enforcement
- Provisioning (external policy administration)
- Registration
- Risk and event monitoring, including audits
- Single sign-on services (pass-through authentication)
The sharing of any or all of these attributes over a network may be the subject of different government regulations and in many cases must be protected so that only justifiable parties may have access to the minimal amount that may be disclosed.
This level of access defines what may be called an identity relationship.
Comments