Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Shortcut: sc-15620
What
Documents the new ability to hand-edit Exploit Maturity and Reachability on a finding, in the Threat Intelligence panel of the Add and Edit Finding forms. This is the docs half of a Pro change on the same release line.
Changes
triage_findings/findings_workflows/editing_findings.md) — the Threat Intelligence panel section now lists Exploit Maturity and Reachability, with the persistence rules (a hand-set value on a CVE-bearing finding is replaced by the next sync; a finding with no CVE keeps it) and how hand-set values feed the priority floors. Corrects the prior text that called Exploit Maturity feed-only.triage_findings/finding_scoring/reachability.md) — adds a "Setting reachability by hand" section: a manual verdict competes with scanner verdicts by tier (a stronger scanner verdict still wins the Resolved value) and is exempt from the staleness sweep.asset_modelling/PRO_hierarchy/threat_intelligence.md) — notes Exploit Maturity can be set by hand.Text-only, per the OSS docs conventions. English source pages only; translations are handled separately.