The latest product update on this page is currently in English. Navigation and account services remain available in your selected language.

Sentinel ID · National identity & operationsExplore all four products →

Security and operations

Controlled access from connection to case review

Decide who can connect, what they can access and which changes need approval. Keep a clear record of the work.

Host the application and records on infrastructure controlled by the organisation. Enable only authorised external services and preserve private access to data and management systems.

Choose the controls your organisation needs. External archives and identity checks require an authorised service provider.

01 / Security control

Approved devices for web access

Web access can require the Sentinel access client on an approved device. The server checks the installation before allowing a connection, including for privileged accounts.
The client opens the workspace through a local connection and stops after an hour without activity. A copied program folder does not give another device approval.
The Android Field app uses its own device approval. Partner systems connect through permission-controlled APIs, with IP restrictions when enabled. Neither needs the desktop access client.

02 / Security control

Keep the application on your private network

Staff and authorised partner systems connect through a secure public gateway. It carries pages, API requests, file transfers and live communications.
The private application server starts the connection to the gateway. This allows the application and database to stay on the organisation’s private network.
The gateway supports a separate access point for the service. Production planning covers network security, reliable connectivity and enough capacity for the expected traffic.

03 / Security control

Account security and temporary access

Each account has one active login. Signing in on another device signs out the earlier session. Password and security changes also end earlier sessions.
Web users receive a 14-day deadline to set up an authenticator app. They can manage their password, authenticator and single-use recovery codes from their profile.
Administrators can grant extra permissions for a set number of days. Attempt limits and account lockout help prevent repeated password or code guesses. The Android Field app follows its own device security controls.

04 / Security control

Case and identity approvals

Every officer belongs to a unit or station. Approval permissions can limit case reviewers to their own unit or agency. Self-approval follows the organisation’s policy.
A separate review queue handles suggested links between cases and people, missing biometrics, new person records and possible duplicates.
Removing a biometric requires the relevant permission and approval. The system checks the reviewer’s authority and records the decision before applying the change.

05 / Security control

Evidence and confidential records

Evidence records include checks for file changes and a history of who handled each item. Digital signatures and legal holds are available when set up for the organisation.
Permissions govern access to personal details, biometrics, reports and downloads. Operational reports let authorised staff choose dates and open supporting records from available charts.
Temporary scans and processing files are kept separately for cleanup. Clearing them leaves registered biometrics and protected evidence intact.

06 / Security control

Activity records and recovery

Activity records help administrators review actions and investigate unusual use. Integrity checks help identify changes to the audit trail. An external archive can be connected where required.
Encrypted backups, archive checks and restore exercises support recovery. Signing and backup keys need their own protected storage.
Device revocation, secure connections and release checks support day-to-day security. External identity checks and device verification work only after the required services have been connected.

Security that fits your operation

Validate permissions with different agencies and units, revoke devices during active sessions, test interrupted uploads and restore a backup into a separate environment. Set biometric thresholds using representative captures and examiner review.

Recognition performance and capacity need to be tested for each deployment. The population and camera calculators provide planning estimates.

Security overview How secure access works

Review your security workflow

Demonstrate approvals, device revocation, gateway routing and recovery with representative test records.

Arrange a demonstration

Site security and AI training

Sites, cameras and detection rules

Explore Site security

Add examples and validate training

Extend existing datasets, continue training and review independent results before activation.

Explore AI training