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 documentation change appears safe to merge.

Findings

1.  Client inputs are not trusted ▶

Summary

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

• Directs vulnerability reports to NVIDIA’s submission form or PSIRT email.
• Removes the architecture and threat-model sections.

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

[greptile-apps]

Client inputs are not trusted The statement that “other inputs come from trusted sources” conflicts with the threat model’s warning about untrusted requests. Triton clients can supply prompts, images, and sampling parameters, while model configuration comes from the model repository. Grouping them together makes it harder for operators to tell which inputs need request-side limits and validation.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!