A one-door public key infrastructure (PKI) pilot lets you test the full access sequence with your own cards, controller and software. A successful badge tap is one result. You also need to see what happens when an authorized user has trouble getting in, when a valid card lacks door permissions, and when a credential fails validation.

Pick the door and record the baseline

Pick a door that represents the next group you want to upgrade. Match the controller, wiring, credential types and required authentication. A staff entrance where people tap a card tells you how that setup performs. A door that also requires a PIN needs its own test.

Before making changes, record the reader and controller models, software and firmware versions, reader interface and the credential identifier your physical access control system (PACS) expects. Observe normal entry and check which events the PACS records today. If you plan to keep existing cardholder records, include an approved test credential that exercises the identifier mapping. Check reader and controller compatibility.

Agree on a maintenance window with site operations. Name who can pause the pilot, who can restore the prior configuration and who will confirm that routine entry works again if you roll back.

Agree on what counts as a pass

Before testing, ask the site owner and installer to agree on the expected access decision, which events should be available for review and an acceptable time from badge presentation to unlock. Use the existing door as a reference and set a target that reflects how people use it, especially during busy periods.

Separate the reader’s credential check from the PACS access decision in your test plan. A card can authenticate successfully and still lack permission for that door. For a credential the reader rejects, confirm where your configuration reports the failure. Some setups may show it in reader diagnostics while the PACS receives no credential identifier.

Run the test cases

Use site-approved test credentials. For each case, record the reader response, the door outcome and what the PACS logs. Agree in advance which events your system is expected to report.

  • Valid card with permission. Confirm the door grants access and the PACS shows the expected cardholder, door and timestamp. Repeat with representative cards from each issuer or profile the site plans to accept.
  • Valid card without permission. Use a credential that authenticates but belongs to a test account without access to the pilot door. Confirm that the door stays locked and the PACS records the denial as expected.
  • Credential that fails validation. Use an approved test card with an untrusted issuer, an expired certificate or a revoked certificate as applicable. Confirm that the system denies access and check the configured reporting behavior.
  • Card and PIN or biometric. Where the door requires an additional factor, verify successful access with the required factor and denial when that check fails.
  • Credential replacement. If the rollout involves replacing legacy badges, check that the new card resolves to the intended cardholder record. Follow the site’s process to retire the old badge and verify that the access change takes effect as planned.
  • Normal use and recovery. Repeat entry with representative users. Check response time against the agreed target and confirm expected behavior after an approved controller or reader restart. Run another grant and denial test after recovery.

Record what happened

Keep one row per test with the test credential label, expected outcome, observed door and event results, and a pass or fail. Note when the test ran and where the supporting event can be found. Use labels such as “Test card B” so the worksheet can be shared without including cardholder details.

Example test record
Test case Expected Observed Result
Test card B has no permission for this door Door stays locked. PACS records an access denial. Door stayed locked. The PACS log showed the denial at the pilot door. Pass

Decide whether to expand

Review the results with the installer and site owner. If a required test failed, record who owns the fix and rerun the affected cases after the change. For example, if the door opens but the event points to the wrong cardholder record, correct the identifier mapping and repeat both the grant and denial tests.

When the required tests pass, record the configuration the team approved and identify the next group of doors that matches it. If a door uses a different controller, credential profile or authentication method, validate that combination before adding it to the rollout.

Review the PKI retrofit plan or discuss your pilot with IDFactors.

← All articles