PasskeyBridge —

Compliance & Privacy · 2026-11-16

One Signal, Three Frameworks: Mapping Carrier Attestation to SOC 2, DORA and NIS2

By J. W. Bouckaert

One Signal, Three Frameworks: Mapping Carrier Attestation to SOC 2, DORA and NIS2

One control, written once

A group with an EU bank, an EU payment or hosting subsidiary and US enterprise customers can face three sets of reviewers for the same authentication control. The bank answers to its DORA supervisor. The subsidiary answers to its NIS2 competent authority, unless a sector-specific Union act such as DORA already covers it: NIS2 Article 4(1) says that where such an act imposes requirements "at least equivalent in effect", the relevant NIS2 provisions "shall not apply to such entities." The US customers ask for a SOC 2 report from a CPA firm. Each reviewer reads a different text. The control is the same: before a high-risk action, check that the person and device in front of you are who the account says, and keep the record.

This post maps one such control, a carrier state check plus a phishing-resistant authenticator at the moment of a sensitive change, against the exact clauses of each framework, and lists the evidence that answers all three.

The three texts

DORA. Regulation (EU) 2022/2554, which applies from 17 January 2025, requires financial entities in Article 9(4)(d) to "implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys ...". Article 9(4)(c) adds policies that "limit the physical or logical access to information assets and ICT assets to what is required for legitimate and approved functions and activities only". Article 9(1) requires entities to "continuously monitor and control the security and functioning of ICT systems and tools".

NIS2. Directive (EU) 2022/2555, Article 21(2), lists the minimum cybersecurity risk-management measures. Point (i) covers "human resources security, access control policies and asset management". Point (j) covers "the use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate." Article 21(1) frames all of them as measures "appropriate and proportionate" to the risk.

SOC 2. The AICPA's 2017 Trust Services Criteria (March 2020 revision) set the criteria a SOC 2 examination tests against. CC6.1: "The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives." One of its points of focus is that persons, infrastructure and software "are identified and authenticated prior to accessing information assets". CC6.6: "The entity implements logical access security measures to protect against threats from sources outside its system boundaries." CC7.2: the entity "monitors system components and the operation of those components for anomalies that are indicative of malicious acts".

The mapping

Control elementDORANIS2SOC 2 (TSC 2017)
Phishing-resistant authenticator with user verification at the sensitive stepArt. 9(4)(d) strong authenticationArt. 21(2)(j) multi-factor authenticationCC6.1 identify and authenticate before access
Carrier state check (SIM swap, port) before the stepArt. 9(4)(d) dedicated control systems; Art. 9(1) monitoringArt. 21(2)(j) continuous authenticationCC6.6 threats from outside the boundary; CC7.2 anomaly monitoring
Step-up or deny when the check failsArt. 9(4)(c) access limited to approved activityArt. 21(2)(i) access control policiesCC6.1 restricts logical access
Record of each check and decisionArt. 9(1) monitor and controlArt. 21(2)(f) assessing effectiveness of measuresCC7.2 anomalies analyzed

The table maps clauses to a control element. It is not a legal opinion, and each reviewer decides for themselves whether your implementation meets their text. Its use is that one control design, one evidence pack and one owner answer three reviews.

The evidence pack

Every reviewer asks some version of the same three questions: what the control is, that it runs, and that someone looks at its output. One evidence pack answers all three if it holds:

  • The written policy naming the sensitive actions, the checks before each, and the outcome on failure.
  • Configuration exports showing the authenticator policy, including the user verification setting, and the carrier check wired to those actions.
  • A sample of decision records for a period, each with the time, the action, the signals at decision time and the outcome.
  • Exception handling: what happened when the carrier gave no answer, and who reviewed it.
  • A review record showing someone read the anomalies and acted.

PasskeyBridge in the evidence pack

PasskeyBridge supplies verified identity signals; the access decision and the policy belong to the customer. Within that boundary, the parts of the control it provides are these:

  • Passkey ceremonies that require user verification. By default the hosted relying party requires user verification at registration and at assertion and refuses a response without it. A relying party can change that setting, and the configuration export in the pack shows which applies.
  • Carrier state. A lookup returns SIM swap, porting and reachability where the provider answers, with a score capped at 1.0. A SIM swap insight the provider does not answer fails the lookup, which gives the exception-handling item above a defined input.
  • Records without personal data. Phone numbers and IP addresses are stored only as keyed digests, HMAC-SHA-256 under a server-held pepper, so the decision records in the pack can be shared with a reviewer without exporting the identifiers.

On our own assurance: PasskeyBridge describes its SOC 2 and ISO 27001 status as readiness. No audit firm is engaged and no audit is scheduled.

For the DORA register work this pack feeds, see DORA evidence ownership. For NIS2 scope and what essential entities must show, see NIS2 identity assurance. The product view is on the identity assurance platform page.

Frequently Asked Questions

Which DORA article covers strong authentication?

Article 9(4)(d) of Regulation (EU) 2022/2554 requires financial entities to implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems. DORA applies from 17 January 2025.

Which NIS2 article covers multi-factor authentication?

Article 21(2)(j) of Directive (EU) 2022/2555 lists the use of multi-factor authentication or continuous authentication solutions, where appropriate, among the minimum risk-management measures.

Does NIS2 apply to banks already covered by DORA?

Article 4(1) of NIS2 says that where a sector-specific Union act imposes requirements at least equivalent in effect, the relevant NIS2 provisions do not apply to those entities.

What is PasskeyBridge's own SOC 2 status?

PasskeyBridge describes its SOC 2 and ISO 27001 status as readiness. No audit firm is engaged and no audit is scheduled.

Start free · Test the API