These answers reflect the IDSENTRA product architecture and intentionally avoid unsupported certification or regulatory claims.
Identity searches, watchlists, cases, evidence, source credentials, operational audit records, and related protected workflows belong inside IDSENTRA-CORE or the customer-controlled operational boundary—not the public website or commercial distribution telemetry.
Commercial customer/site state, deployment identity, signed licensing, entitlements, releases, activation state, and privacy-minimized deployment health required to operate the software fleet.
The architecture is designed around locally verifiable signed license state and bounded continuity during temporary commercial control-plane outages.
The architecture is provider-neutral and intended to isolate directory, identity-provider, SIEM/event, reporting, regulated-source, and site/device integrations behind explicit server-side contracts.
No. Public material describes product architecture and implemented capabilities. Applicable regulatory, legal, security, privacy, and certification requirements must be evaluated against the actual deployment and jurisdiction.
Review workflow fit, authority boundaries, integrations, access control, retention, deployment continuity, licensing, recovery, governance, acceptance testing, training, and go-live ownership together.
IDSENTRA