It’s key to note the potential relationships between different NIST models.

In particular one key dynamic is that while IDaaS (Identity as a Service) is a standalone service, it’s also a component part of the other scenarios. For example all of the Business Use Cases define a common IDaaS layer.

Specifically in the E-Discovery use case it stipulates IDaaS requirements including VPN access methods et al, identity management features that would also be common to other applications.

The key feature areas for EDaaS are those relevant to compliance – For example logging the activities of users and how they access various records, and also related access control, such as enabling the legal department to access user file systems when conducting legal retrievals.

It’s also key to note the common role of Identity that this diagram illustrates for the Cloud Service Broker scenario.

This will enable agencies to equip their users with identity services that ensure their use of remote Cloud services is secured in line with these IDaaS standards.