docs(smart_upload): document multi-Asset finding fan-out - #15738
Merged
Conversation
Smart Upload matches an incoming Finding's Host against every Asset that owns a Location with that host, and creates a copy of the Finding in each matching Asset (its own Smart Upload Engagement and Test). The page only ever described the single-Asset case, so the multi-Asset behavior was undocumented. Add a "Findings that match more than one Asset" section explaining the fan-out, that it is intentional (independent reports/SLAs/metrics per Asset), and that matching is host-based (FQDN, IP fallback). Clarify the existing single-Asset line and add a matching note to the glossary. Propagated to the de/es/fr/ja translations. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
blakeaowens
approved these changes
Aug 19, 2026
devGregA
approved these changes
Aug 19, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 20, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 20, 2026
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
3 participants
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.
[sc-14662]
What
Documents how Smart Upload behaves when a scanned Host belongs to more than one Asset.
The Smart Upload page previously described only the single-Asset case ("all subsequent Findings that share an Endpoint or Host will be sent to the same Asset") and said nothing about what happens when a Host matches multiple Assets.
Why
Smart Upload matches an incoming Finding's Host against every Asset that owns a Location with that host, then creates a copy of the Finding in each matching Asset (in that Asset's own Smart Upload Engagement and Test). Because a Location can be associated with multiple Assets, one scanned vulnerability can fan out to several Assets. This is intentional infrastructure-scan behavior, but it was undocumented, which led to real confusion about whether the finding lands in one Asset or all of them.
Changes
de/es/fr/jatranslations (page and glossary).Documentation-only change. No behavior change.
Verification
Built the docs site locally with Hugo (clean build, no errors or warnings). Confirmed the new section renders in all five languages, the in-page anchor link resolves, and the surrounding sections remain intact.