stride-tampering

Identify tampering threats in system architecture using the STRIDE methodology.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Jayarr03/Codex_ThreatModel_Skills --skill stride-tampering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stride-tampering
Source: https://github.com/Jayarr03/Codex_ThreatModel_Skills/tree/main/skills/stride-tampering
Command: npx skills add https://github.com/Jayarr03/Codex_ThreatModel_Skills --skill stride-tampering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify potential Tampering threats in a system, focusing on unauthorized modifications of data, messages, and state.

Core Features & Use Cases

  • Identify Tampering Threats: Generate threat ideas for data, messages, and state modifications.
  • STRIDE Methodology: Aligns with the STRIDE model for categorizing threats.
  • Scope Modeling: Helps establish the scope for threat modeling by focusing on specific slices like API write paths or storage paths.

Quick Start

Run the stride-tampering skill to generate Tampering threats for your system architecture.

Frequently Asked Questions about stride-tampering

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

FAQPage Schema
What is a tampering threat in threat modeling?

A tampering threat involves the unauthorized modification of data, messages, or system state. Identifying these threats requires analyzing system write paths and mutable assets to ensure system and data integrity against malicious alterations.

How do I identify data tampering threats in my architecture?

You can identify data tampering threats by applying the STRIDE methodology to your system architecture. This process focuses on mapping API write paths and storage paths to detect where unauthorized modifications to data and state might occur.

Can I use STRIDE to analyze specific API write paths for system integrity?

Yes, using the STRIDE methodology allows you to establish a focused scope for threat modeling. You can specifically target and analyze API write paths or storage paths to uncover potential data and message tampering vulnerabilities.

What is the best way to model unauthorized modification threats for mutable assets?

The best way to model unauthorized modification threats for mutable assets is to use the STRIDE methodology. It systematically categorizes and generates threat ideas specifically targeting unauthorized changes to data, messages, and system state.

Do I need to understand system write paths to detect message tampering?

Yes, detecting message and data tampering requires a clear understanding of system write paths and mutable assets. Analyzing these architectural components is essential for identifying where unauthorized modifications could compromise system integrity.