Skip to main content
Version: Cloud

IdentityPROCESS+

The Omada IdentityPROCESS+ describes the standard Omada Identity or Omada Identity Cloud solution offering. In this context, the standard refers to the functionality which is available out-of-the-box (OOTB), provided that Omada Identity is configured correctly.

The IdentityPROCESS+ document assumes that the reader has attended and completed basic Omada Identity training and is familiar with the terms and processes associated with IGA.

Assumptions​

The Master Data needed to run Omada Identity is available via standard collectors.

The description of standards in this document doesn't include a description of the following functions:

  • Default functions that are available when using Omada Identity, for example, adding an email notification in an Identity and Governance Administration (IGA) process.

  • Functions that are available by adding custom code to the Omada Identity installation.

    The mechanism of adding and managing custom code is standardized.

  • Functions or concepts which are described in other documents such as Customer Identity and Access Management (CIAM) or Surveys.

  • Using the built-in Software Development Kit Guide (Connectivity SDK Guide).

Prerequisites​

Here, you can find a brief explanation of the most important preconditions that are necessary to run the standard Omada Identity processes. For a more detailed description of these preconditions, refer to the Installation guide.

Master data​

The most important Master Data required to run the IGA processes are:

  • Identity data
  • Organizational data
  • Applications and systems
  • Resource(s) to apply for

It's assumed that all Master Data is available in the correct form and provided by external systems to Omada Identity. The needed governance is not discussed in detail.

Although Master Data can be created in Omada Identity, this scenario is not part of this document, however, external contractors are considered an exception.

In Omada Identity, there are standard processes to create this Master Data without relying on data imported from other systems.

Governance and Compliance​

In Omada Identity, there are various requirements for governance and compliance.

Governance​

Governance describes how requirements are addressed in Omada Identity. The following are the two types of governance:

  • Type 1: is everything that's needed to run Omada Identity. This includes, for example, the definition of resource owners or the establishment of an escalation hierarchy. As the definition of governance is not the main aim of this document, later chapters explicitly state the governance needed.

  • Type 2: addresses the IGA rules and specifications which are addressed by Omada Identity to solve governance challenges and rules defined within the company as well as laws defined by external authorities. These rules are typically seen in regulated industries such as finance and pharmaceutical. This type of governance provides requirements for:

    • IGA processes
    • SoD (Segregation of Duties) and other compliance rules
    • Reporting to prove compliance

Compliance​

Compliance rules are functional requirements that require dedicated governance to be implemented. Typically, compliance incorporates the requirements as well as the reporting of the already-implemented requirements to prove that a company or organization is compliant.

In Omada Identity, suitable audit reporting is a standard feature. Additionally, Omada Identity is designed to address compliance requirements based on:

  • Rules from authorities in the financial sector.
  • Rules from authorities in the pharmaceutical industry.
  • Rules and directives such as the European Union’s GDPR (EU GDPR) or IT-related policies enforced by the National Institute of Standards and Technology (NIST) in the United States of America.
  • Rules from standards such as ISO 2700x when self-imposed by a company or organization or by their partners or customers.

In addition to printable reports proving compliance, Omada Identity reporting includes:

  • Lists of identities for managers, with a drill-down option for a greater level of detail.
  • Dashboards to compile relevant information.
  • Surveys to match or correlate Omada Identity-based data with information taken outside of Omada Identity.
  • A special user account for auditing purposes.

Moreover, Omada Identity provides tools to access all the data contained in the SQL databases.