What it is
An Additional Artifact is proof that supports compliance or operational reality but is not directly tied to a specific process or configuration definition.
Additional artifacts still matter. They provide context, supporting evidence, or corroboration, even when they do not map cleanly to a single policy, process, procedure, plan, or configuration.
Before review, these items are artifacts. After review and acceptance, they become evidence.
Why it exists
Not all useful proof fits neatly into a process or configuration category. Organizations generate many records that support compliance, oversight, and accountability without being created as part of a formal workflow or configuration check.
Additional artifacts ensure this supporting proof is not ignored or lost simply because it does not belong to a narrowly defined category.
How additional artifacts become evidence
An additional artifact becomes evidence when:
- A person reviews it
- Confirms it is relevant and reliable
- Accepts it as supporting proof
Before review, it is an additional artifact.
After review, it is evidence.
What an additional artifact usually looks like
Additional artifacts can come from many sources and may be created intentionally or incidentally.
Common characteristics:
- Not generated by a specific procedure or configuration check
- May provide context or supporting information
- Often created through normal business or technical activity
- Can be structured or unstructured
Common examples
- General system logs
- Emails or internal communications
- Calendar entries
- Contracts and agreements
- Waivers or exceptions
- Audit correspondence
- Informal reports
- Notes or records retained for reference
How to use additional artifacts
Upload additional artifacts when they provide useful proof or context.
Link them to relevant policies, processes, or requirements when possible.
Review additional artifacts to determine whether they should be accepted as evidence.
Common confusion
Additional Artifact vs Process Artifact
A process artifact proves a specific activity was performed.
An additional artifact provides supporting proof or context.
Additional Artifact vs Configuration Artifact
A configuration artifact proves a technical setting exists.
An additional artifact provides general or indirect proof.
Additional Artifact vs Evidence
An additional artifact is unreviewed proof.
Evidence is proof that has been reviewed and accepted.