Skip to content
IT Atlas

Knowledge graph

The connected model behind IT Atlas

Content here is stored as entities and relationships rather than pages, so a topic knows which section it belongs to, which protocols and ports it uses, which technologies implement it, which vendor supplies those, which attacker techniques target it and which control baselines reduce them. This page exposes that model directly, which is also how new pages get added later without rewriting anything.

431 entities1442 relationships12 relationship types

What is modelled

defined inexplained inimplemented byimplemented throughlistens onmaps toreducesrelates tosits in sectionsupplied bytargetsuses protocol

Explore the graph

The map centres on one entity and draws everything connected to it. Click a node to travel to it, hover to read the relationship, and use the kind switches to thin the view.

Trail
Show
Port 546PortDHCPv6

Click any node to centre the map on it. 1 of 1 relationships shown.

Open the Port 546 page

Port · UDP

Port 546

Registered or conventional port used by DHCPv6.

1 connectionsOpen its page

listens on (incoming)

  • Protocol

Busiest entry points

The entities with the most relationships, which makes them the most useful places to start.

Vendors in the model

Vendors are first class entities, connected to the technologies they supply and the topics those technologies appear in.

Ports in the model

Each port is a node, so a port number resolves to the protocols that use it and the topics that explain them.

Modelled but not yet written

These entities exist in the graph through their relationships and are the natural candidates for their own pages next.

Because every entity already carries typed relationships, adding a page for one of these is a matter of writing the body: its inbound and outbound links, search entry and breadcrumbs come from the graph.