use-threat 0.0.1

Threat modeling and threat-category primitives for RustUse
Documentation
  • Coverage
  • 37.5%
    21 out of 56 items documented1 out of 23 items with examples
  • Size
  • Source code size: 10.58 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.02 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 4s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • Documentation
  • RustUse/use-security
    1 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • CloudBranch

use-threat

Threat modeling and threat-category primitives for RustUse.

Experimental

use-threat is experimental while the use-security workspace remains below 0.3.0. Expect small API adjustments during the first release wave.

Example

use use_threat::{ThreatActorKind, ThreatCategory, ThreatId, ThreatScenario};

let scenario = ThreatScenario::new(
    ThreatId::new("T-1")?,
    ThreatCategory::Spoofing,
    ThreatActorKind::External,
);

assert_eq!(scenario.category().as_str(), "spoofing");
# Ok::<(), use_threat::ThreatError>(())

Scope

  • Threat IDs, actor kinds, categories, capabilities, intents, surfaces, models, and scenarios.
  • STRIDE-style labels and local metadata helpers.

Non-goals

  • MITRE ATT&CK mapping.
  • Attack simulation.
  • Detection engineering, SIEM behavior, or threat intelligence feeds.

License

Licensed under either of the following, at your option:

  • Apache License, Version 2.0
  • MIT license