docs: Add SECURITY.md

[mc-nv]

What does the PR do?

• Adds SECURITY.md, which this repository did not have. Flagged by an AIVO asset review.
• Uses NVIDIA's current standard template, as in NVIDIA/NeMo, cuda-python and Megatron-LM. Text is NVIDIA-authored, unmodified except the platform-neutral "GitHub/GitLab" wording from cuda-python.
• Reporting policy only: no threat model or architecture section.
• Applied across all Triton repositories.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

• docs: Adopt current NVIDIA SECURITY.md template server#8997

Where should the reviewer start?

• SECURITY.md — compare against NVIDIA/NeMo/SECURITY.md for the canonical wording.

Test plan:

• Documentation only; no code paths affected.

• CI Pipeline ID:

Caveats:

• NVIDIA ships two variants of the warning sentence: NVIDIA/NeMo says "through GitHub", NVIDIA/cuda-python says "through GitHub/GitLab". This PR uses the latter because Triton repositories exist on both GitHub and internal GitLab.
• The template's PGP wording is "we encourage you" rather than a hard requirement. Kept as-is for template fidelity; raised on docs: Adopt current NVIDIA SECURITY.md template server#8997.

Background

An AIVO asset review (securityportal.nvidia.com/aivo/assets) flagged Triton repositories with no SECURITY.md. Rather than authoring per-repository security documentation, every repository adopts NVIDIA's current standard template so the policy is identical everywhere and carries no repository-specific claims to maintain.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Resolves: TRI-1935

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds security reporting guidance document.

The PR appears safe to merge; no new blocking issue was established.

Findings

1.  Missing tensor validation assumption ▶
2.  Missing trace path assumption ▶
3.  Local hook boundary omitted ▶

Summary

The PR replaces the repository-specific security policy with NVIDIA’s standard vulnerability-reporting template.

• Directs reports to NVIDIA’s submission form or PSIRT email.
• Removes the former threat model and operational assumptions.

_{Reviews (4) · Last reviewed commit: "docs: Adopt current NVIDIA SECURITY.md t..."}

[greptile-apps]

Missing tensor validation assumption The revised assumptions no longer tell callers to validate tensor buffer sizes, shapes, data types, and memory types. Tensor stores these values without checking them, and the wrapper passes them to Triton unchanged. An embedding application that relies on the gateway assumption could miss the validation needed to avoid invalid memory access.

[greptile-apps]

Missing trace path assumption The revised assumptions no longer say that trace output paths must remain under operator control. Trace settings accept a supplied path, and trace output opens that path directly. A gateway cannot restrict where an embedding application writes traces, so operators lose a warning against allowing request-controlled paths to overwrite files or consume disk space.

[greptile-apps]

Local hook boundary omitted The new security-boundary description leaves out this repository’s add-license hook. It runs locally, accepts file paths, and rewrites them in place, following symlinks; a network gateway does not protect that filesystem boundary. Without the trusted-working-tree assumption, hook consumers lose the warning that supplied paths can lead to changes outside the intended repository.