VulnParse-Pin

Configs

VulnParse-Pin configuration is split into three primary policy files.

Configuration files

At runtime, defaults are copied into the active app config area if user versions are missing.

config.yaml

Controls feed/cache and runtime data behavior.

Typical sections:

Operationally important fields:

scoring.json

Defines scoring policy behavior, including:

Use this file to align risk output with your organization’s tolerance and remediation policy.

Scoring semantics (important)

Current scoring model combines:

With default policy values, a finding can legitimately exceed 15 raw points. Example worst-case shape:

max_raw_risk is used as a normalization divisor for operational score scaling; it does not hard-cap raw score itself. Operational score is then clamped to max_operational_risk.

March 2026 tuned profile rationale

Validated final tuning (balanced exploit-first posture):

Observed behavior on representative large validation (100k OpenVAS regression sample):

This profile is intended for teams that want strong prioritization of known-exploited risk while avoiding broad “everything is urgent” output.

Current Scoring Profile (March 2026)

VulnParse-Pin now uses a balanced, exploit-first risk model (validated on 100k+ record samples):

tn_triage.json

Controls TopN ranking and inference behavior:

This file is where triage prioritization style is tuned.

Path modes and config location behavior

Path and config directory behavior is resolved through src/vulnparse_pin/core/apppaths.py.

Safe configuration workflow

  1. Copy defaults and commit baseline policy files
  2. Tune one parameter group at a time
  3. Re-run representative datasets
  4. Compare score coverage and TopN output changes
  5. Lock validated policy in version control

Configuration governance guidance