agentleFS
Sign inStart free
apacheapache/streampipes/.claude/skills/security-triage/SKILL.md

security-triage

Skill756 starsChanged 52 days agoApache-2.0View on GitHub

Assess, route and report a suspected security vulnerability in Apache StreamPipes against the project's threat model. Use when a task involves a potential vulnerability, an exploit claim, a security finding from a scanner, or a decision about whether something is in or out of the security model.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read THREAT_MODEL.md at the repository root: the trust boundaries (the REST front door, the external-data ingestion boundary at the …

    line 14
  2. Very specific:

    Read SECURITY.md for how findings are reported (security@apache.org).

    line 21

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Security triage for Apache StreamPipes

You are helping assess whether a reported or suspected issue is a security vulnerability in Apache StreamPipes and how it should be routed. Complete these steps before drafting any report or reaching any conclusion.

Step 1 — Read the threat model

Read THREAT_MODEL.md at the repository root: the trust boundaries (the REST front door, the external-data ingestion boundary at the adapters, the extension runtime), the adversaries in and out of scope, and what StreamPipes upholds versus what it leaves to the operator. The model is v0; cite sections by number.

Step 2 — Read the security policy

Read SECURITY.md for how findings are reported (security@apache.org). Do not open a public issue or pull request for a suspected vulnerability.

Key scoping facts (details in THREAT_MODEL.md)

  • The streampipes-rest HTTP layer is the primary control boundary; the external-data ingestion boundary is at the adapters. The broker, datastore and extension-runtime services are assumed to run inside an operator-controlled perimeter.
  • Installed extensions (custom adapters, processors, sinks) are code execution by design, not a sandbox.
  • An adapter ingesting data from an external source is the intended function; source trust and the handling guarantee for hostile ingested data are spelled out in the threat model.
  • Transport security (TLS), network isolation and extension vetting are operator responsibilities, not engine invariants.

Step 3 — Route the finding

Route the finding to exactly one disposition in THREAT_MODEL.md §10 — VALID, or one of the OUT-OF-MODEL / BY-DESIGN dispositions — and cite the section that justifies the call. State the affected component from the §2 table and the boundary it crosses.

Output

A short triage note: disposition, justification with section citations, affected component and boundary, and — only for VALID — the reporting route from SECURITY.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free