Security Questions to Ask About Mobile Key and Digital Credential
System integrators are often asked whether a phone-held credential is secure enough for a real door. This tearoff turns mobile key and digital credential security questions into approval checks for credential issuance and revocation, digital credential lifecycle, access credential audit trail, offline credential behavior, and handover access control evidence. Use one copy during evaluation and keep the completed evidence with the design record.
Run the checklist as a decision gate
Direct answer. Mark every line Yes, No
| Area | Question to ask | Evidence to demand | Owner |
|---|---|---|---|
| Credential scope | Which identities, doors and periods may receive this credential? | Written issuance policy | Security lead |
| Device binding | How is a credential associated with the intended phone and user? | Binding procedure and test record | Integrator |
| Revocation | Who may revoke a credential, and how is that decision recorded? | Revocation workflow | Client owner |
| Event evidence | Which issuance, use, denial and revocation events are retained? | Sample event export | Platform owner |
| Clock | Which system supplies the authoritative timestamp? | Clock and synchronisation record | Operations |
| Offline path | What decision remains available when the server cannot be reached? | Approved degraded-mode test | Door approver |
| Handover | What proves that temporary access ended? | Closeout and inventory record | Project manager |
Before integrating the credential with a door, use the Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey to document the installed conditions. A mobile credential can be approved only after the physical door, controller and operating assumptions are known. Specifications at this level come off the smart door locks.
Test issuance, activation and everyday use
Use these mobile key and digital credential security questions before approving a pilot:
- Which system is the source of truth for issuance: the lock platform, identity platform, property system or a local API versus cloud API boundary?
- What identity check occurs before activation, and which team owns exceptions?
- How is the phone, user, credential and door relationship recorded?
- What happens when issuance succeeds in one system but activation fails at the lock?
- Can an administrator distinguish a newly issued credential from an activated, suspended or revoked one?
- Which test covers a normal presentation, an expired credential, a revoked credential and an unknown phone?
- Does phone-held credential security remain understandable when one service is unavailable?
The Mobile Key and Digital Credential: The Test Plan a Buyer Should Demand provides the supporting test structure. Keep its results with the door-by-door design rather than treating a general demonstration as acceptance evidence.
Challenge revocation, return and recovery
- Who can revoke a credential, and does that person have authority over the associated person or role?
- How quickly must a lost phone, terminated worker or changed contractor be removed from the access path?
- Does revocation invalidate the credential, the device binding, the person’s access rights or all three?
- What happens when a revocation request reaches the platform but cannot reach the lock?
- How is a returned or reassigned phone prevented from presenting a previous credential?
- Can the team distinguish attempted use after revocation from a failed presentation caused by connectivity?
- Which service desk owns first response, and when does the issue move to the access-control engineer?
Demand a written sequence showing the initiating actor, affected credential, resulting access state, timestamp source and acknowledgement. A dashboard label alone does not establish that the decision reached the controller.
Inspect identity, privacy and audit evidence
The evidence must distinguish credential issuance from activation, presentation, access decision and revocation. For each event, ask what identity or role was evaluated, which door was involved, which system made the decision and where the event was retained.
The audit log and event memory serve different purposes. The audit log is the retained record; event memory is the lock-side buffer used when it cannot reach the server. Ask how buffered events are transferred, how duplicates are identified and whether source and timestamp remain intact.
CONFIRM-WITH-LOCAL-PRIVACY-LEAD: Confirm the lawful basis, notice, retention, subject-request handling and permitted access for records tied to a person, credential or door event before pilot approval.
CONFIRM-PER-SUPPLIER: Obtain written confirmation of the credential format, issuance method, revocation behavior and event fields for the proposed SKU; confirm on the dated product page for the specific SKU before approval.
Specify the degraded path and its owner
Degraded behavior must be designed, not improvised at the door. Name the decision that remains available when the network, controller or server is unavailable, and show the result at the installed door.
flowchart TD
A[Credential issued] --> B[Identity and device bound]
B --> C[Credential presented]
C --> D{Controller status available}
D -->|Yes| E[Controller evaluates access]
D -->|No| F[Local degraded rule applies]
E --> G[Decision and timestamp recorded]
F --> G
G --> H[Revocation or incident reviewed]
Also ask which team reconciles a partial failure, which side owns the fix and whether a queued revocation can be distinguished from a queued audit event. The offline case is the design, not the exception.
Compare candidate evidence before approval
Use the Mobile Key and Digital Credential Requirements Document Template to capture the evidence rather than accepting a feature comparison alone.
| Decision | Accept when | Escalate when | Recorded proof |
|---|---|---|---|
| Lifecycle | Issued, activated, presented, revoked and returned states are distinguishable | Only an active or inactive label exists | Sample lifecycle sequence |
| Revocation | Actor, affected credential, result and timestamp are visible | The outcome cannot be traced | Revocation audit record |
| Degraded operation | The local rule, recovery owner and reconciliation method are approved | Offline behavior is described as automatic or temporary | Door test result |
| Handover | Outstanding access, open incidents and evidence ownership are closed | Temporary records remain unexplained | Signed handover record |
A supplier statement does not replace the dated product-page evidence for the proposed configuration, nor does it replace the client’s approved door behavior.
Close the evidence pack with explicit owners
Request the final pack before handover: the credential issuance sequence, activation and revocation test records, degraded-mode test, event sample, clock ownership, escalation contacts and a list of unresolved exceptions. Use the Documenting Mobile Key and Digital Credential for Handover and Audit to align that pack with operational handover.
It is worth pairing this with smart lock installation manual requirements. That is the same question mobile key and digital credential security questions has to answer here.Name one owner for every item: access policy, identity source, controller configuration, platform operation, network recovery, privacy review and door-level approval. Then ask the supplier to return written confirmation or a dated source for each unresolved item.
Pilot approval should require a plain answer to four questions: who may issue the credential, who may revoke it, what decision remains available during an outage, and which clock governs the audit trail. Without those answers, the mobile credential remains unproven even if the phone interface works correctly.
When the file is ready, request a quote against the written requirement.

