Menu

Eliminating False-Positive Criticals: Sentinel Rank Handling in OASIS SARIF v2.1.0 Ingestion
📰

Eliminating False-Positive Criticals: Sentinel Rank Handling in OASIS SARIF v2.1.0 Ingestion

DEV Community: cicd·Aryan Rajput·about 3 hours ago
#BQuqD3pQ
#devtocicd#devto#dev#rank#sarif
Reading 0:00
15s threshold

The Hook

In the OASIS SARIF v2.1.0 specification, an omitted result.rank property defaults to the sentinel value -1.0 —meaning a security report parser that compares numeric rank thresholds without guarding against negative values will silently promote low-severity unranked findings into critical vulnerabilities.

The Deep Dive

Enterprise DevSecOps teams rely on Static Application Security Testing (SAST) and third-party scanners emitting Static Analysis Results Interchange Format (SARIF) reports to gate merge requests cleanly. Under the OASIS SARIF v2.1.0 standard, rank is a floating-point value between 0.0 (lowest priority) and 100.0 (highest priority) representing the relative importance of a finding, while -1.0 is reserved as a sentinel default indicating that no rank was specified by the analyzer.

While investigating SARIF severity resolution in gitlab-org/gitlab and authoring MR !271129 ( fix(sarif): ignore negative result ranks ) , I analyzed how Gitlab::Ci::Reports::Security::Locations::Sarif…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.