Faraday Tutorial: Findings, Workspaces and Assessment Provenance
Faraday organizes assessment information into structured workspaces and findings. Imports and analyst changes need a traceable relationship to the evidence that produced them. Collaboration makes records easier to manage, but combining reports does not automatically resolve inconsistent observations or validate every imported conclusion.
Here's a popular Faraday video — watch it, then summarize it with one click. Or paste any other YouTube link below.
— or paste your own YouTube link —
Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.
Why Use Faraday Tutorial: Findings, Workspaces and Assessment Provenance
- Organize findings within assessment workspaces
- Connect records to affected assets
- Preserve the source of imported evidence
- Distinguish duplicate reports from separate conditions
- Track verification and remediation context
Frequently Asked Questions
What is a workspace used for?
A workspace groups information for a defined assessment context. Its organization helps relate assets and findings, but the workspace boundary should still reflect the scope and sources of the actual investigation.
Why preserve a finding's provenance?
Provenance identifies where the observation originated and how it was collected. It allows another analyst to evaluate the evidence and distinguish a tool report from a separately validated condition.
Does importing a report verify its findings?
Importing transforms report data into records the platform can manage. The underlying claims retain their original evidence and limitations, so import success does not establish that each finding is accurate.
How should duplicate-looking findings be handled?
Compare the affected asset, mechanism and supporting evidence before consolidating them. Similar labels can describe separate conditions, while different labels can refer to the same issue reported by multiple sources.
What makes a finding actionable?
An actionable finding identifies the affected component, observed condition and relevant impact with evidence. Remediation and verification context then connect that information to the work needed to address it.