[Developers]

Secrecy-Aware Graph Traversal

Secrecy-aware graph traversal that enforces clearance, country, compartment, and tenant restrictions on every node and edge during relationship analysis, so a graph query can never reveal a connection the analyst is not

Category: InvestigationLast Updated: Jul 16, 2026
investigation

Overview#

Secrecy-aware graph traversal that enforces clearance, country, compartment, and tenant restrictions on every node and edge during relationship analysis, so a graph query can never reveal a connection the analyst is not cleared to see.

Graph analysis is powerful because it finds relationships that are not visible in a flat record list. That same power creates risk if a traversal crosses into a country, clearance level, or compartment that the analyst is not allowed to see. The module applies these restrictions edge by edge during traversal rather than after results are assembled, so analysts receive a coherent graph view made only from material they are authorised to inspect.

Key Features#

  • Traversal-Time Filtering: Every node and relationship is checked edge by edge before it enters the analyst's result set, rather than being filtered after the graph has been assembled.
  • Clearance-Aware Expansion: Classification and secrecy labels restrict how far an analyst can traverse into sensitive material, enforced on entities and relationships alike.
  • Country and Jurisdiction Controls: National handling restrictions can prevent traversal across protected boundaries, with country codes matched as equivalent across two- and three-letter forms so a code variant cannot bypass a restriction.
  • Compartmented Operational Picture: Material marked to a compartment on the common operational picture is only visible to analysts holding the matching compartment authorisation, even through multi-hop traversal.
  • Tenant Boundaries Inside Traversal: Multi-tenant access controls are enforced within graph traversal itself, not only at the API edge.
  • Protected Source Relationships: Relationships involving sources marked at a higher classification or within a compartment stay hidden from analysts who lack the matching clearance or compartment authorisation.
  • Partial Graph Results: Analysts still receive authorised relationships even when higher-classification material is suppressed.
  • Proven Denial Paths: Denial behaviour is exercised by extensive regression suites, giving assurance that suppressed relationships stay suppressed as the platform evolves.

Use Cases#

  • Coalition Intelligence Sharing: Two agencies share one investigation graph while each sees only the relationships releasable to their country under national handling restrictions.
  • Financial Crime Link Analysis: Analysts traverse account, company, and person relationships while classification and jurisdiction rules are enforced on every hop.
  • Protected Source Handling: Relationships linked to a source held at a higher classification or inside a compartment are excluded from general graph exploration and visible only to analysts with the matching authorisation.
  • Compartmented Operations: A compartmented source's links remain invisible to analysts outside the compartment, even when a multi-hop query would otherwise reach them.
  • Oversight and Accreditation: Security teams verify that graph analysis cannot become a path around classification, country, or tenant boundaries, supported by regression suites that prove denial behaviour.

Integration#

Secrecy-aware traversal connects to entity profiles, investigation graphs, role-based access control, classification labels, and the common operational picture. It supports visual graph exploration and link analysis while preserving the same access rules that apply to source records.

Open Standards#

  • ISO 3166: Country-based access rules treat two- and three-letter country code forms as equivalent when evaluating national restrictions.
  • ISO/IEC 27001:2022: Access control and information classification controls frame the governance model.
  • OAuth 2.0 and JWT Bearer Token: Authenticated context carries the role, organisation, and clearance information used by traversal policy.
  • ISO 8601: Relationship and event timestamps use standard date-time formatting.

Last Reviewed: 2026-07-16 Last Updated: 2026-07-16

Ready to Build?

Get started with our APIs or contact our integration team for support.