SWIFT Evidence Vault & Audit Telemetry

Tap to enlarge

Name the artifact and connect it to the owning entity and CSCF control.

• Artifact name (required)

  artifactName

  A name a reviewer will recognise months from now — not the raw filename.

• Owning BIC (required)

  entityBic

  Select the 8- or 11-character BIC of the entity that owns this evidence.

• CSCF control ID (required)

  controlId

  Select the CSCF control or requirement this evidence supports.

• Descriptionoptional

  description

  Briefly state what the evidence demonstrates and the period or system it covers.

• Control objective (1/2/3)optional

  controlObjectiveId

  Optional objective grouping from the selected CSCF control.

• Linked KYC-SA attestation IDoptional

  attestationLink

  Optional UUID of the KYC-SA attestation that this evidence supports.

Tap to enlarge

Classify the evidence and describe how it was collected.

• Evidence type (required)

  evidenceType

  Choose the business form of the evidence so extraction and review use the correct route.

• Collection method (required)

  collectionMethod

  State whether the evidence was uploaded, collected automatically, or received from another governed source.

• Collection tooloptional

  toolUsed

  Name the source product or collection tool, such as Splunk, Nessus, or AWS Config.

Tap to enlarge

Upload the original source and record who collected it, when, and where.

• Artifact (required)

  objectKey

  Upload the evidence file. Its hash, size and type are computed from the stored bytes — you never type them.

• Collected at (required)

  collectedAt

  Use the time the evidence was obtained from its authoritative source.

• Collected by (required)

  collectedBy

  Identify the person or governed service that collected the evidence.

• Collection location (required)

  collectionLocation

  Identify the source environment, system, region, or repository from which it was collected.

• Collection context notesoptional

  collectionContextNotes

  Record collection steps, filters, scope, and any facts needed to reproduce the evidence.

Tap to enlarge

Define the period this evidence supports and its retention treatment.

• Superseded By (Artifact ID)optional

  supersededByArtifactId

  Enter superseded by (artifact id).

• Superseded Atoptional

  supersededAt

  Enter superseded at.

• Valid from (required)

  validFromDate

  First date on which this evidence supports the selected control.

• Valid until (required)

  validUntilDate

  Last date through which the evidence remains applicable; it must follow the start date.

Tap to enlarge

Review the server-derived storage facts and optional discovery tags.

• Retention yearsoptional

  retentionYears

  Optional policy retention period. Leaving it blank does not prevent the review decision.

• Tagsoptional

  tags

  Add searchable business tags; do not place secrets or sensitive personal data in tags.

Tap to enlarge

Decide whether named human review is required and record that attestation when applicable.

• Reviewed atoptional

  reviewedAt

  Date and time the named reviewer completed the review.

• Lock Reason (if locked)optional

  lockReason

  Enter lock reason (if locked).

• Locked Atoptional

  lockedAt

  Enter locked at.

• Requires review (required)

  requiresReview

  Select this when a named human reviewer must attest to the evidence before it is relied upon.

• Revieweroptional

  reviewerName

  Name the accountable person who reviewed the evidence.

• Review notesoptional

  reviewNotes

  Summarize what was checked, any exceptions found, and the reviewer’s conclusion.