Evidence Collection
Evidence links your security posture to ISM controls. QuantAssure collects evidence automatically from pipeline runs and allows you to add manual evidence for controls that aren't covered by integrations.
The Evidence Library
Compliance → Evidence lists every evidence item across all your frameworks and controls in one place, so you can see what is stale before an audit without opening each control.
- Each row shows the evidence title, the framework and control it supports, its type and source, when it was collected, its freshness and its expiry
- Filter by framework, by type (Technical, Policy or Manual) and by freshness (Fresh, Aging, Stale or Expired), or search by evidence title or control
- Filters and the page number are kept in the address, so you can bookmark or share a filtered view
- Select a row to open its control, where you can add manual evidence
Freshness uses the same thresholds as the control page and the SOA tab, described under Evidence Freshness. A framework's Readiness tab shows evidence coverage as a share of applicable controls.
Evidence Types
| Type | Source | Example |
|---|---|---|
| Finding | Pipeline scans | Dependabot alert mapped to ISM-1504 |
| Policy | Google Drive sync | Information Security Policy |
| Resolution | Pipeline runs | A merged pull request that fixed a finding |
| Scan Activity | Pipeline scans | A scan that ran against a system in scope |
| Asset | Asset inventory | A registered asset in scope for the control |
| Manual | Added by a person | A title, description and link to a screenshot, config export or attestation |
| Assessor Review | SOA import | Assessor determination and notes |
Automated Evidence
How Findings Link to Controls
- Pipeline runs collect findings from your integrations
- AI enrichment maps findings to specific ISM controls
- Linked findings appear automatically on the control detail page
- Run scans regularly to keep evidence current
Policy Evidence
- Policies synced from Google Drive provide documentary evidence
- Link policies to your compliance framework
- Policies are referenced by AI during assessment
Tip: Run pipeline scans weekly to maintain fresh automated evidence.
Manual Evidence
When to Add Manual Evidence
- Physical security controls (building access, server room)
- Procedural controls (hiring processes, training records)
- Third-party attestations (vendor security certifications)
- Configuration screenshots not captured by integrations
Adding Evidence
- Open the ISM control detail page (from Compliance → Frameworks and the Controls tab, or from a row in Compliance → Evidence)
- In the Evidence & Artifacts section, click Add
- Enter a title (e.g., "MFA configuration screenshot")
- Add a description explaining what the evidence demonstrates
- Optionally add a URL linking to the source document
- Click Save
Evidence Freshness
| Status | Age | Meaning |
|---|---|---|
| Fresh | < 60 days | Current and audit-ready |
| Aging | 60–90 days | Consider refreshing before audit |
| Stale | > 90 days | Should be refreshed |
| Expired | Past expiry date | No longer valid |
Warning: Assessors expect recent evidence. Stale evidence may be questioned during audit.
System Boundaries
- Evidence is collected against registered systems and their assets
- If a system isn't registered, its findings won't appear
- If an asset isn't in scope, evidence won't link to controls
- Register all in-scope systems before running assessments