Skip to main content
Aspex is one security model with several views. Most sessions start from a task, not a command. Find yours below.

​
The five questions

Everything above is one of five questions. This is the whole mental model.

What CAN happen?

aspex scan finds dangerous combinations across your tools and shows the resulting blast radius.

What DID happen?

aspex trace reconstructs what your agents actually did from the logs they already write. aspex explore opens it visually.

What CHANGED?

aspex diff main..HEAD shows whether a change added capabilities or created new attack paths. aspex lock / verify catch drift over time.

WHY does it matter?

aspex explain says why a path exists, what evidence supports it, and what would break it. It follows data, and it says “no complete path found” when there is none.

WHAT IF I change it?

aspex simulate tests a security change without touching your real configuration.

​
Two loops

Most work is one of two loops. Harden before you commit
Scan finds a path, explain names the controls that break it, simulate proves one works, you apply it, verify confirms it. tighten suggests the change; simulate shows what it would do. Investigate what happened
Trace reconstructs the session, explore shows it as a timeline and a graph, explain separates observed from inferred, and a reproduction bundle lets someone else analyze it offline without executing anything. Everything computes from configs and logs already on your machine. Nothing is sent anywhere, and no answer claims a path was walked unless the trace shows it. See how Aspex reasons.