Collect and keep evidence current

Discovery scaffold for collecting evidence and keeping its status current.

Quellinhalt wird angezeigt aus `en-gb` solange diese Sprache noch nicht übersetzt ist.

Product discovery scaffold. This page captures the intended evidence-collection area and the evidence needed before public capability claims are written. It does not confirm that these capabilities are available in the released Aeptus GRC product.

What this area is for

Gather relevant evidence from connected sources, keep track of its freshness, and help a team see what has changed or needs attention.

Questions to answer

  • Which evidence types are collected automatically, supplied by a person, or not supported?
  • How often is evidence refreshed, and can customers control the schedule?
  • How does Aeptus decide that evidence is current, stale, missing, or needs review?
  • What history is retained when a value changes, a source is disconnected, or a collection fails?
  • How are partial failures surfaced and resolved?
  • What notifications or review actions are available, and who can perform them?

Product and code information needed

  • Collection jobs, supported schedules, source timestamps, and freshness rules.
  • Change detection, history/versioning, failure handling, retry, and notification behavior.
  • Workspace scoping, access permissions, audit records, and customer controls.
  • Release evidence that distinguishes shipped collection behavior from planned work.