The identity layer

Verify identity.
Keep your access system.

Authara issues the credential. TrustPoint verifies it at the door. Your existing PACS applies access permissions.

Add an identity layer at the edge.

Illustration: at the building entrance, an employee holds a smart card to a door reader; a red ribbon runs from the reader through the wall to the existing access-control panel in the back office.
© 2026 IDFactors. All rights reserved.

A credential number tells an access system which record to look up. With cryptographic authentication, the reader verifies the credential before sending its ID to the controller.

TrustPoint Cards and Readers add that verification at the door. Authara brings issuance and credential management together. The PACS then decides who can enter, where and when.

Same card ID. Different result.

Watch a copied card meet a number-only reader, then the identity layer.

Number only, copied card

  1. The reader reads the card ID and passes it on.
  2. The PACS finds a matching record and grants access.
  3. The door opens. A number-only system can’t tell a copy from the original.

Identity layer, copied card

  1. The TrustPoint Reader sends a random challenge.
  2. The copy has no private key, so it can’t sign it.
  3. Rejected at the reader. The card ID never reaches the PACS.

Identity layer, genuine card

  1. The card signs the challenge with a private key that stays on the chip and sends a signed response.
  2. The reader verifies the signed response, then passes the same card ID on.
  3. The PACS applies its usual rules. Nothing changes there.

Three parts. One connected workflow.

Issue with Authara.

Create and personalize TrustPoint PIV-C credentials through a guided desktop workflow.

Explore Authara →

Verify with TrustPoint.

The reader challenges the credential and verifies its response before passing the identifier onward.

Explore the readers →

What changes. What stays.

The credential and verification.

Introduce TrustPoint credentials and authenticating readers where needed. Configure the reader for the credential format and controller interface.

The access-system investment.

For compatible deployments, retain the controller, access rules and credential-number mapping. Confirm site-specific integration before rollout.

Own the keys behind the credential.

You can supply supported signing hardware and keep control of your certificate authority (CA) signing key. Authara uses that hardware to sign certificates, and the key stays on the device.

Explore protected signing hardware →

Read the Authara white paper →

Build on the identity layer.

As cryptography evolves, the credential and its verification become an important part of long-term access-control planning.

Explore post-quantum credential security →

Let’s talk

Plan your next step.

Tell us about your credentials, readers and access system.

Contact sales