hve-core skill-security-model.instructions.md

Skill Security Model Conventions

Every skill that ships an executable runtime (network egress, credential handling, subprocess execution, or untrusted document/content parsing) carries a SECURITY.md STRIDE threat model next to its SKILL.md. These models mirror the repo-wide model at docs/security/security-model.md and are registered in its Skill Security Models section, which is the authoritative index for locating any of them. When that index is unavailable, say so and locate models by looking for a SECURITY.md beside the skill's own SKILL.md rather than assuming a skill has no model. The canonical exemplars are the SECURITY.md files bundled with the mural, jira, and gitlab skills; resolve them by skill name rather than by a package path, which is not stable across repository, plugin, and extension layouts. When none of them is available, follow the Required Structure below, which is self-contained. The fill-in template is docs/templates/skill-security-model-template.md; when it is unavailable, build the document from the Required Structure section instead of improvising a layout.

Required Structure

A conformant skill SECURITY.md contains, in order:

1. Frontmatter: title (" Skill Security Model"), description, author: microsoft/hve-core, ms.topic: reference, ms.date, keywords, and an estimated_reading_time; followed by <!-- markdownlint-disable-file --> and the H1.
2. An intro paragraph naming the runtime files and trust-bucket decomposition, stating that each bucket enumerates all six STRIDE categories.
3. A "See also: repo-wide STRIDE model" callout linking docs/security/security-model.md.
4. ## Executive Summary with a ### Security Posture Overview table.
5. ## Contents (anchored table of contents).
6. ## System Description with a ### Components list and a ### Data Flow mermaid flowchart TD whose subgraphs are trust zones and whose edges are labeled with protocols.
7. ## Trust Boundaries with a ### Boundary Diagram (ASCII box diagram) and a ### Boundary Descriptions table.
8. ## Assets (A1…) and ## Adversaries (ADV-a…) tables.
9. One ## Bucket B1…Bn section per trust bucket (there is no umbrella ## Trust Buckets heading). Each bucket enumerates all six STRIDE categories as ### headings in canonical order (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege), using an explicit "Not applicable. ." where a category does not apply, and ends with a ### Risk Rating table (Threat / Likelihood / Impact / Residual Risk / Status).
10. ## Enterprise Readiness Gaps register.
11. ## References.