Skip to content

Research / Follow the connections

A wider view.
A clearer boundary.

Look beyond one server. Explore how capabilities combine, follow the evidence behind a finding, and see where that evidence ends.

Cross-server flow is labelled observed or inferred. Kill-chain patterns are always hypothetical.

Four ways to examine the ecosystem

Separate the signal from the assumption.

01 / Connections

Cross-server flow

Follow untrusted input, private readers, and external destinations across a configuration. The walkthrough distinguishes sandbox-observed behavior from connections inferred from declared capabilities.

Observed and inferred paths carry different evidence.

See the walkthrough
02 / Possibilities

Attack chains

Examine multi-step patterns matched against documented templates from real incidents. They describe what a combination of capabilities could permit, rather than claiming that an attack occurred.

Hypothetical patterns, not witnessed attacks.

Explore attack chains
03 / Method

Rule taxonomy

Explore the active rules across categories A-U: what they inspect, which inputs they need, their severity, and their OWASP MCP and MITRE ATLAS mappings. Actual execution and input gaps belong to each report.

A rule's presence does not mean it executed in every assessment.

Browse the rules
04 / Context

Compliance & governance

Connect findings to security controls, articles, and techniques. Inspect the framework mappings and learn how to access signed server reports without confusing a report with a guarantee of safety.

Framework mappings support review; they are not certification.

Explore framework mapping

02 / Examine the prerequisites

A possible route.
Visible prerequisites.

Look at the capabilities, preconditions, and mitigations behind a computed chain. Keep the possible path beside the evidence available for its individual steps.

Review the assumptions at each connection before deciding whether a pattern applies to your configuration.

An observed flow does not establish that a hypothetical attack chain occurred.

Inspect the chain patterns

Return to the source

A connection is only as strong as its evidence.

Open a server report to inspect its findings, assessment method, history, and coverage. Missing observations and failed execution remain part of the decision.

Explore the registry