Technology

Two distinct inventions, one combined protection framework, and associated trust services.

TAA SECO is the public platform and brand. Its architecture brings together two distinct inventions — TAA and TPV — with SECO, a public security-identification code derived from the TAA framework, and AOM, an affiliation and mission-verification service enabled by the security infrastructure. TAA and TPV can operate independently in selected use cases; together they form the broader TAA-TPV protection framework.

Canonical architecture

Clear roles for TAA, TPV, SECO and AOM.

The public descriptions below remain intentionally functional. Protected implementation details, enrolment logic, anti-coercion mechanisms and unpublished technical know-how are not disclosed.

TAA · Invention 1

Transaction security and anti-coercion protection

TAA is the principal invention focused on securing sensitive transactions and situations in which a legitimate user may be manipulated, pressured or coerced. At functional level, the TAA framework can support secure identification, authentication of communications and exchanges, transaction protection, selected video-authentication functions and security services used by AOM.

  • Additional protection around sensitive actions
  • Designed for coercion-risk and manipulation scenarios
  • Supports trusted communications and transaction context
  • Complementary to existing authentication and cybersecurity controls
TPV · Invention 2

Controlled trust, pseudonymization and identity status

TPV is the second invention. It complements TAA by providing a controlled trust and pseudonymization layer, particularly when people or organizations interact with counterparts they do not personally know. Depending on the applicable rules, TPV can distinguish an identity correctly registered as an owner from a temporary identity and help users assess the trust level associated with an unknown caller, sender, company or online entity.

  • Controlled pseudonymization
  • Identity-status context
  • Trust support for unknown counterparties
  • Can operate independently or as part of TAA-TPV
SECO · Secure External Code

A public security and identification code from the TAA framework

SECO is not a third independent invention. It is a public security-identification code derived from the TAA framework and designed to provide an additional reference around a protected identity, communication, service or transaction context. A telephone number, email address, website or payment identifier can be altered or impersonated; SECO is intended to add a separate reference before a user relies on that information.

  • Public-facing security and identification reference
  • Supports identity and communication authenticity checks
  • Can accompany compatible transaction and service contexts
  • Internal enrolment, matching and validation logic remains restricted
AOM · Service

Affiliation and mission verification

AOM — Affiliation & Mission Order / Affiliation et Ordre de Mission — is a service enabled by the TAA/SECO security infrastructure. It is designed to help determine whether a person presenting themselves on behalf of an organization is actually affiliated with it and, where applicable, whether the mission or authorization they claim can be authenticated.

  • Organizational affiliation verification
  • Mission or authorization verification
  • Validity, expiry and revocation status where applicable
  • Useful for both digital and physical interactions

TAA-TPV combined framework

Independent when appropriate. Broader protection when combined.

TAA-TPV is the name of the combined protection framework integrating the TAA and TPV inventions. The two inventions can support separate use cases, but their combination creates a wider trust environment around transaction security, identity status, pseudonymization, impersonation risk, manipulation and coercion.

This distinction is important: TAA SECO is the public platform and brand; TAA and TPV are the two inventions; SECO is a public security-identification code from TAA; and AOM is a service enabled by the security framework.

Beyond strong authentication

Authenticating the user is essential — but it is not always enough.

Strong authentication can confirm that the person performing an operation possesses the required authentication means. A fraud may still occur when a legitimate user is manipulated into authorizing an operation they believe to be legitimate.

Within the combined TAA-TPV framework, SECO can add a separate verification reference around the identity, recipient or context the user believes is legitimate. TAA also addresses situations where the legitimate user may be under pressure or coercion.

Human factor

Security must account for manipulation, uncertainty and pressure.

A legitimate user can make an error, face identity impersonation, be manipulated by urgency or fear, or act under coercion. TAA SECO is intended to add trust signals and controls around these decision points rather than placing the entire burden of detection on the user.

The objective is not to claim that one mechanism eliminates every cyber threat. It is to reduce reliance on a single visible identifier, communication channel or possession of stolen data as sufficient proof of legitimacy.

Design principle

Complement existing cybersecurity before and after compromise.

TAA SECO is designed as an additional trust and resilience layer around existing banking, telecommunications, authentication, identity and cybersecurity systems. It does not replace them and does not claim to make an organization invulnerable.

The protection model is intended to remain useful both before an incident and after data has already been copied, exposed or compromised, because possession of real information should not automatically become proof of legitimacy.

Disclosure boundaryThis website does not publish protected code mechanics, anti-coercion logic, silent-alert processes, detailed enrolment sequences, internal validation logic or unpublished patent material.

Next

See where the technology can be applied.

Explore public solution domains →