threat-model:tna

Analyze pull requests for TNA topology security threats using STRIDE and DFD mappings.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill threat-model-tna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-model:tna
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/threat-model/skills/tna
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill threat-model-tna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns a pull request into a structured security threat analysis for the TNA (Two-Node Arbiter) topology so reviewers can understand what security risks the change may introduce.

Core Features & Use Cases

  • PR threat analysis for TNA: Performs STRIDE/DFD analysis focused on TNA-specific code paths, trust boundaries, and elements.
  • Security mapping for faster triage: Maps discovered threats to MITRE ATT&CK techniques and OWASP Top 10:2025 references.
  • Repeatable reporting with a findings tracker: Generates a formal report and appends cumulative findings to a TNA-specific tracker for ongoing review.

Quick Start

Run: /threat-model:tna 1437 to analyze PR 1437 for security threats in the TNA topology and produce a report mapped to MITRE ATT&CK and OWASP.

Frequently Asked Questions about threat-model:tna

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a pull request for security threats in a TNA topology?

To analyze a pull request for TNA security threats, run the tool against your PR number. It performs STRIDE and DFD analysis on installer, MCO, and CEO code paths, mapping changes to MITRE ATT&CK and OWASP references.

What security frameworks are used to map pull request changes for threat modeling?

Pull request threat modeling maps identified risks using STRIDE, DFD element mappings, MITRE ATT&CK techniques, and OWASP Top 10:2025 references. This cross-referencing helps security reviewers triage findings quickly.

How do I generate a formal threat modeling report for TNA deployment code changes?

Generate a formal TNA threat modeling report by running the analysis on your target PR. The tool retrieves changed files via gh, applies optional ShellCheck scanning, and outputs a structured report appended to a persistent findings tracker.

Does this threat modeling tool require any external dependencies or API keys?

This threat modeling tool has no external dependencies. It relies on workspace discovery and standard gh or web fetch mechanisms to retrieve pull request data and changed files for security posture review.

Can I use this STRIDE analysis for general pull requests outside of TNA deployments?

This STRIDE analysis is specifically scoped to TNA (Two-Node Arbiter) deployments. It targets PRs modifying trust-boundary-relevant code for TNA topologies, making it unsuitable for general, non-TNA security reviews.

Why do I need threat modeling for Two-Node Arbiter installer and MCO code paths?

Threat modeling for Two-Node Arbiter code paths is needed because TNA topologies have specific trust boundaries. Analyzing installer, MCO, and CEO changes ensures new PRs do not introduce spoofing, tampering, or elevation risks.