Skip to content

Feature: GoWitness Integration for Web Service Screenshots with MD5 Hashing #14

Description

@techmore

Summary

Add optional screenshot capture for discovered web services and surface those captures in the UI and reports where useful.

The current issue body is too implementation-heavy. The useful feature is broader: enrich host discovery with visual evidence for HTTP/HTTPS services without degrading the core scan workflow.

Desired Outcome

  • detect screenshot-worthy web targets from scan results
  • capture screenshots out-of-band from the main scan path
  • store and index screenshot artifacts cleanly
  • display them in the UI in a way that improves operator review

Scope

  1. Capture Model
  • identify HTTP/HTTPS services from saved scan results
  • run screenshot capture as a secondary enrichment step
  • avoid making screenshot capture a blocking dependency for scan completion
  1. Tooling Boundary
  • decide whether GoWitness is the chosen implementation or one possible backend
  • make missing screenshot tooling a supported degraded mode rather than a hard failure
  1. Storage and Metadata
  • store screenshot artifacts predictably
  • track enough metadata to associate screenshots with host, port, and scan context
  • use a stronger integrity or deduplication strategy than MD5 if hashing is retained for operational purposes
  1. Presentation
  • show screenshot availability in the asset/history experience
  • support larger preview/open behavior where it adds value
  • keep the table usable when screenshots are absent

Recommendation

Treat this as a web-service enrichment feature with a clean backend/tool boundary. If GoWitness is selected, it should live behind that abstraction rather than defining the entire issue around one binary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions