Map the resources you need to access or recover an account, and see what remains reachable after a loss.
Status · Current capabilities · Run the example · How it works · Development · Contribute
If your phone disappears, can you still sign in to your email account? OpSecMap represents each access or recovery procedure as a route. A route can require several resources together, while another route offers an alternative. A scenario states what you still have and what is excluded; the Rust evaluator works out which resources the documented routes can reach.
OpSecMap is at an early, source-only stage. The crate's version is 0.1.0, and the command-line program runs one fixed demonstration. It cannot load a personal map or scenario. There is no persistence, encryption, graphical view, or downloadable release yet. The roadmap tracks those steps.
The result describes the routes in the map; it does not check whether a provider will accept a real recovery procedure. Do not place passwords, recovery codes, or other secrets in source files or examples.
| In the Rust library | What it does |
|---|---|
| Resources and routes | Validates IDs, labels, route prerequisites, and references to resources in the map. A resource can be renamed without changing its ID. |
| Scenarios | Declares resources initially available and resources excluded throughout evaluation. |
| Access evaluation | Follows AND prerequisites and alternative routes through chains, even when the map contains cycles. |
| Explanations | Records whether access was initial or derived through a chosen route; for unresolved targets, lists each blocked route and its missing prerequisites. |
The CLI prints a sample map and the result of one hard-coded scenario. It does not accept a map file, scenario file, or interactive input.
You need Cargo and a Rust toolchain. Cargo.toml declares Rust 1.75 as the minimum version.
git clone https://github.com/onyks-os/OpSecMap.git
cd OpSecMap
cargo run --The example creates four resources and two routes to email. It then starts with phone accessible and excludes email. Its output ends with:
Scenario access:
phone: initially accessible
Email accessible: false
The exclusion keeps email inaccessible even though routes to it exist. cargo run -- --version prints the crate version. The CLI reference describes the other current behavior.
password manager + phone ── login ────┐
├── email account
offline recovery sheet ── recovery ───┘
The login route needs both the password manager and phone. The recovery route is an alternative. The evaluator starts with the resources marked available, applies every usable route, and repeats until no more resources become accessible. A cycle alone cannot create access.
For each accessible resource, the result distinguishes an initial assumption from access derived through a route. For an inaccessible, non-excluded target, it records which prerequisites are missing from each documented route. That information helps identify what to prepare or check before an incident; it is not proof that recovery is impossible in the real world. The architecture document explains the model and its limits.
cargo test
cargo fmt --all -- --checkThe tests cover validation, alternative routes, chains, cycles, exclusions, evidence, and blocked routes. The evaluator runs in memory and the example does not save application data. Release packaging and verification are future work.
Bug reports, questions about the model, and small contributions are welcome; see CONTRIBUTING.md. For security issues, follow the security policy.
The maintainer is learning Rust and writes the core Rust engine. AI tools are used to help write tests and documentation, discuss the initial architecture, and make small supporting code changes that the maintainer reviews. The maintainer decides what belongs in the project and checks the resulting work.
OpSecMap is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later).