Uloq App

iOS and Android App with strong security algorithms.

Verification, Identification and Authorization

Uloq is an App which provides ironclad, undisputable personal identification, and authorization.

Uloq allows users to:

★ Personally identify themselves, undeniably.

★ Approve or decline workflow requests

★ Provide audit trails to verify and valdate user actions and transactions

★ Verify and validate the recipients signature using digital signing.

How Uloq works:

  1. Identifies the user and allows them to authenticate events or transactions from anywhere in the world
  2. Uloq creates a secure key that can be incorporated into any workflow type applications either via the Eccenscia Security Network or a private corporate channel.
  3. The proprietary environmental scanning algorithm effectively identifies a user’s virtual location, providing further identification

 

Download for free

Coming Soon

Download for free

Coming Soon

Product Features

Simple User Interface

Verify your identity securely

Make official and workflow decisions on the go.

Security Algorithms used have never been hacked (NIST-P256 elliptic curve cryptographic algorithms)

Verification through Biometrics/ Facial Recognition or via Pin

The proprietary environmental scanning algorithm effectively identifies a user’s location, providing further verification

The keys used to sign requests are user owned. (cryptographic keys)

Get Secure verification

Coming Soon

We adopt a Zero Trust methodology

Principles
Verify explicitly
Least Privilege
Assume breach
What it
means
Always authenticate and authorize based on all available data points, including user identity, location, device health, service or workload, data classification, and anomalies



Limit user access with just-in-time and just-enough-access (JIT/JEA), risk based adaptive policies, and data protection to help secure both data and productivity.
Minimize blast radius and segment access. Verify end-to-end encryption and use analytics to get visibility, drive threat detection, and improve defences.
How we
tackle it
1. Confisense verifies data origination by creating a relationship between senders and receivers. This relationship is verified using key deriving algorithms.
2. Confisense verifies the identity of the user. This is done using Uloq.
1. Data access is limited by environmental and identity authorization.
2. The configuration files are not accessible to system users.
1. Access to Confisense can be restricted using Uloq as a second-factor authentication.
2. Application setting changes can be protected and authorized with a Uloq key. (No setups and settings changes are permitted without performing an identity verification using Uloq. )
3. Files cannot be decrypted without a user being fully identified by Uloq.

We adopt a Zero Trust methodology

What it means

Verify explicitly

Always authenticate and authorize based on all available data points, including user identity, location, device health, service or workload, data classification, and anomalies

Least Privilege

Limit user access with just-in-time and just-enough-access (JIT/JEA), risk based adaptive policies, and data protection to help secure both data and productivity.

Assume breach

Minimize blast radius and segment access. Verify end-to-end encryption and use analytics to get visibility, drive threat detection, and improve defences.

How we tackle it

Verify explicitly

  1. Confisense verifies data origination by creating a relationship between senders and receivers. This relationship is verified using key deriving algorithms.
  2. Confisense verifies the identity of the user. This is done using Uloq.

Least Privilege

  1. Data access is limited by environmental and identity authorization.
  2. The configuration files are not accessible to system users.

Assume breach

  1. Access to Confisense can be restricted using Uloq as a second-factor authentication.
  2. Application setting changes can be protected and authorized with a Uloq key. (No setups and settings changes are permitted without performing an identity verification using Uloq. )
  3. Files cannot be decrypted without a user being fully identified by Uloq.