Commit Graph
5 Commits
Author SHA1 Message Date
anqorithm 7b92b8c352 docs(security): link the private vulnerability report form 2026-11-18 22:09:58 +01:00
BaaRai 9767a70205 docs(security): name the real ingest counters and block rules
in_scope_not_asset counts in-scope events that are not asset types, not
gate rejects: a rejected candidate comes back as an insertion forbidden
error in the insert_assets result. EvaluateAssetGate also applies block
rules whether or not an allow-list exists, so the no-allow-list gap is
about the allow rule, not the whole gate.
2026-11-18 12:12:50 +01:00
dach-a 94be0148ce docs(security): document scope_distance as a trusted input
States the trust boundary discussed in #317:

- output.json's scope_distance is the integrated scanner's own verdict
  and is ingested as-is; in-scope events are not re-checked against
  ARTEX's rule set.
- The enforced boundary is the task allow-list: assets reach the graph
  (insert_assets) only through EvaluateAssetGate, and rejects are
  recorded as in_scope_not_asset.
- The no-allow-list case is an accepted gap, with operator guidance:
  configure an allow-list per task or review output.json before feeding
  it to ARTEX. Cross-checking ingested events against ARTEX's rule set
  would redefine existing scanner configurations, so it is a deliberate
  design question, not an accepted vulnerability.

Option 2 as picked on #317; documentation only.
2026-11-18 03:15:57 +00:00
BaaRai f3a8e82d29 docs(security): point reports to the BaaRai repository and drop placeholders
Replace the [owner] placeholder and the unfilled email and PGP lines with GitHub Security Advisories as the sole reporting channel. Replace the 0.4/0.5 support table with the latest release line, and turn the response timeframes into best-effort goals.
2026-11-14 20:47:28 +01:00
Long Ngo 33078a7d35 Create SECURITY.md 2026-11-06 14:01:04 +07:00