Semantic mapping and traceability layer

 

AIMLUX.AI Proposes: Combining Equitus.ai ArcXA (nnx) and   CyberSpatial Teleseer (ACT) to produce the semantic mapping and traceability layer for the data Teleseer surfaces, while Teleseer provides the network-visibility layer from PCAPs and passive observation. In practical terms, Teleseer is about seeing and carving network behavior, and ArcXA is about explaining how entities, attributes, and transformations relate across a system.dev+2

Where they fit together

• Teleseer can discover devices, traffic patterns, protocols, and timelines from packet captures without agents or scanning.sossecinc+1

• ArcXA is described as mapping intelligence for enterprise data migrations, with schema mapping, lineage, and transformation traceability.github-cn+1

• That means ArcXA could help define the business meaning of what Teleseer detects, especially when you want to connect network events to source systems, data flows, or migration logic.cyberspatial+1

Useful integration patterns

• Metadata enrichment: Export Teleseer findings such as device IDs, protocols, session timelines, and asset attributes into ArcXA so those observations can be linked to a governed model of systems and fields.cyberspatial

• Lineage from network evidence: Use Teleseer packet evidence to validate or annotate lineage claims in ArcXA, especially for migrations where traffic reveals actual source-to-target communication.dev+1

• Investigation workflow: Let Teleseer identify unusual traffic or unmanaged assets, then use ArcXA to map those items back to application ownership, data domains, and transformation dependencies.dev+1

• Migration assurance: During cutovers, Teleseer can confirm what is still talking, while ArcXA can show whether that traffic matches the intended migration map.cyberspatial+1

A concrete example

Suppose a legacy ERP migration is underway. Teleseer could show the real network conversations between the old ERP, middleware, and databases, while ArcXA could store the intended schema and data-flow mapping for those same systems. If Teleseer shows an unexpected downstream service still receiving traffic, ArcXA can help determine whether that is a forgotten dependency, a transformation step, or an unmanaged integration.dev+1

What would be needed

• A shared identifier strategy for hosts, applications, datasets, and migrations.

• An export path from Teleseer outputs into ArcXA-friendly metadata.

• A model in ArcXA that can store evidence from packet analysis alongside business lineage.

• A rules layer that reconciles passive network observations with declared architecture.

A good way to think about it is: Teleseer tells you what is really happening on the wire, and ArcXA tells you what that activity means in the enterprise data model.sossecinc+2