Our solution

IdStory - together we protect the story of your unique identity

IdStory is our proprietary solution for automating identity management on endpoint systems from one central place. IdStory keep records about all important events and changes related to the identity lifecycle.

IdStory

Modules

Re-certification module

Self-registration module

Management of externist - customers, suppliers, patients (CIAM)

Password synchronization module from MS AD

Acess management

Password reset module

VPN Administration Module

Reports module

Managing service and technical accounts

Certification Authority Module

License Management Module

Consents module

SMS modul

IdStory HUB

IdStory

What is identity ?

An identity is an electronic representation of a person or object (such as a computer or phone) from the real world. Identity Management in IT centrally manages identity access to resources (accounts, vpn, certificates) across managed IT systems.

Identity and access management is key to a sustainable IT infrastructure. It enables efficient and secure management of access permissions and minimizes the risk of cyber threats.

Lukáš Cirkva
CEO | IdStory

What is an identity manager?

It is a process tool that has a communication interface to many managed systems. Identity Manager integrates managed systems and allows you to execute processes and manage accounts over them. IdM includes synchronization tools for data transfer, auditing and reporting functions and, of course, a user interface that allows you to delegate responsibility for certain tasks to users.

What are the common problems that IdM helps solve?

  1. We don’t keep track of who has access to where.
  2. It takes a long time to manually create an account and set up rights.
  3. It is time-consuming to obtain supporting documents for an audit review.
  4. Users cannot simply apply for access themselves and have a supervisor approve.
  5. Administrators are overwhelmed with the routine work of setting up access.
  6. There remain accounts that should no longer be in the system.

In principle, IdM provides several basic objectives:

  1. Automates routine identity management processes. Relieves administrators from routine processes.
  2. It centralizes systems under a single administration – you get an overview of the accesses in the systems. You can identify a person across systems.
    Delegate account management to business owners. I.e. for example, supervisors request and approve access to the CRM. Administrators are supposed to be developing systems, not approving whether an applicant should have access.
  3. Records, audits operations over accounts and rights. You will quickly get the basis for IT audits.
  4. It will increase safety, for example by preventing the existence of dead souls. It will no longer be the case that an employee still has access to the system after the end of the contract and can take data away.

What is Role Based Access Control (RBAC)?

IdM uses role-based access control, RBAC – Role-Based Access Control. This is the core functional mechanism of IdM. If I get a role, it typically means that I’ve gained access to the system or some specific permission on the system, such as inclusion in an MS Active directory group.

Support for managed systems?

Any system that is accessible over the network and has a known (or discoverable) identity structure can be connected to IdM. The above may give the impression that connecting endpoint systems to an IdM system must require considerable customisation to support identity management. The opposite is true. A major benefit of IdM is the ease of connecting the end system without having to customize or even reboot it. How do we do that? More general approaches are used, including the so-called. identity connectors.

Connector is a small software tool on the IdM side that allows data exchange with a connected system using its native API. Thus, the connector adapts to the connected system, not the other way around.

Methods that generally provide connectors