What Security Features does BioRegistra Have?

Exact matches only
Search in title
Search in content
Search in posts
Search in pages
Filter by Categories
Billing and Payment
Capturing Data
Contact Us
Fix a Problem
Integrating to Our APIs
Introduction: Getting Started
Managing Your Account
Safety and Standards
Uncategorized

What Security Features does BioRegistra Have?


What Security Features does BioRegistra Have?

Some of the world’s best industry security standards have been adhered to, to ensure the platform is safe and secured. Some of these features include:

User and data account privacy

BioRegistra is a cloud service platform, however, we take maximum caution to ensure your data is only accessible by you or your other users that you have granted the privilege to. You can also assign different roles with different privileges as you desire.

Audit Trail for activity monitoring

With our audit trail reports, you can track the activity of your agents and other users on your project. This helps you monitor and track in cases where you need to do any form of auditing on your account. You can then export this report in multiple formats to be used outside the system. Also, BioRegistra possesses integrated real-time client analytics which probes, stores, and monitors all key activities done on a device.

Secured Connection

Connections between BioRegistra components and devices are secure. The connection between nodes and components on BioRegistra is via HTTPS. Maximum security is ensured at all various data states; Data-in-transit, Data-at-rest, and Data-in-use

Obfuscation of Application

BioRegistra application is obfuscated (rendered obscure, unclear, or unintelligible) so it is not possible to reverse-engineer it and use it for malicious activities.

Verification of Application Signature at Runtime

BioRegistra client application signature is verified each time the application is launched on a client device. With this feature, only connections from valid BioRegistra Clients are allowed

Quarantining of non-compliant captures

Quarantining of non-compliant records is a check put in place to block (quarantine) registrations suspected to be fraudulent. This check minimizes fraudulent infractions by rogue users.

Prevention of injection of records

Injection of records to the secure servers is prevented since synchronization requests coming to the secure servers are verified before they are accepted (rejected records are saved in a separate folder on the server and are not processed). Some of the verifications done are user login details, capture device details etc. With this security feature in place, processing of fraudulent records is non-existent.