Creating Custom Evidence Records

You can create custom evidence records for requirements not covered in the pre-populated records. Custom evidence will be highly leveraged for controls in the catalog that do not have pre-defined evidence records mapped to them out of the box.

Steps to create a custom evidence record:

Navigate to SCF Evidence Application, click + New Record to start a custom evidence entry.
Set Evidence Status
Use the Evidence Status dropdown to indicate the current state of the evidence (for example, Not Started, In Progress, Ready, or Expired).
Select Evidence Collection Type
- Manual Upload (PDF, Word, Excel, etc.)
- External URL (for example, links to internal wikis or cloud storage)
- Monitored in Turbine (for automation-based artifacts)
Attach Supporting Materials
- Drag and drop files into the Evidence Artifacts upload area.
- Populate the External URL field if evidence is stored remotely.
- If applicable, link relevant Turbine playbooks in the Referenced Playbooks section.
Describe the Evidence
- Context for the evidence
- How the control is met
- Hyperlinks to additional resources
Fill Metadata Fields
- ERL #: Optional custom identifier.
- Area of Focus: Security domain the evidence addresses.
- Documentation Artifact: Defaults to Custom.
- Custom Documentation Artifact Name: Provide a descriptive title.
- Evidence Owner and Title: Identify the responsible party.
- Review & Expiry Fields:
  - Reviewed By
  - Evidence Review Date
  - Evidence Expiration Date
Save the Record
Click Save to add the record to the SCF Evidence application. It will then be available for use in reporting and metrics.