Evidence
The Evidence Locker holds the proof that your organisation does what its policies say, and a second person must approve each item before it counts towards a control.
Evidence (the proof that a control is
actually working) can be a certificate, a report, a screenshot, a log extract or
an audit letter. Each item carries a name, a type, an optional source system, an
owner and dates, and links to the controls it supports. Every new item starts as
Awaiting review. Under
four-eyes review (a second person checks the
work), it counts towards no control until someone other than the uploader
approves it.
The locker is append-only. Each stored file is hashed with SHA-256 so
tampering can be detected. No role can delete an item,
Admin included. A wrong upload
stays in the locker as Rejected, and an outdated one becomes
Superseded.
Who uses it
- Viewer: can open the locker and export a selection, but cannot upload and cannot start an AI action, because each one spends a tenant AI credit. The list and detail pages show only evidence the Viewer owns, so this is usually empty.
-
Contributor: can upload
evidence, link it to controls, run the two AI briefings,
AI ClassifyandReview content (AI), and upload a new version of approved evidence. Sees only their own items. Cannot approve, and cannot use bulkExport. - Manager and Admin: see every item, and can approve or reject evidence that someone else uploaded. Nobody can review their own upload. Only an Admin can delete a collection rule.
What's on this screen
The locker is at /evidence, headed Evidence Locker.
Four actions sit in a row on the right: Evidence Gaps (AI),
Refresh Triage (AI), Collection Rules and the primary
action, Upload Evidence. The two AI buttons appear only for roles
that may start an AI action.
The filter bar sits below them. It has a Search evidence… box with
a Search button, plus All Types and
All Sources dropdowns and a Filter by tag… box with
its own Search button. On the second line is the
All review states dropdown. The type and source lists are built
from the values in your own locker.
The table has a select-all checkbox, then Name, Type,
Review, Source, Size, Owner,
Created and, if you scroll right, Actions. Each name
starts with a short type chip, such as doc for a document or
file for types without their own chip (as on every row of the
captured screen), and ends with the file extension, such as .pdf.
Long names are cut short with an ellipsis. Review shows one of four
badges: Awaiting review, Approved,
Rejected or Superseded. The captured screen shows rows
awaiting review, approved and rejected. The list has no expiry column: a
Valid Until date appears only on the detail page.
Finding and opening evidence
-
To add something new, select
Upload Evidenceat the top right. TheUpload Evidencedialog opens (see the next section). -
Type a name in the
Search evidence…box. The table narrows as you type. You can narrow it further with the type, source, tag andAll review statesfilters. For example, chooseAwaiting reviewto see what is waiting for a reviewer. -
Tick a row's checkbox. A bulk bar appears above the table, showing
Link to Control,Exportor both, depending on your role. -
Select an item's name. Its detail page opens at
/evidence/{id}. -
Check the
Reviewbadge before you rely on an item. OnlyApprovedevidence counts towards a control.
Scroll the table right to reach Actions. Preview opens
the file in a panel over the list, and Download fetches the
original file. Both appear only when a file is stored.
AI Classify appears for roles that can edit evidence and start AI
actions.
Link to Control opens a dialog where you first pick a framework (or
all frameworks), then the control to link the selected items to.
Export downloads the selected items' details.
Uploading evidence
The dialog has a dashed drop zone at the top, with metadata fields below it. The
drop zone lists the accepted formats: PDF, Office documents, TXT,
CSV, JSON, XML, common image types and
ZIP. The limit is 50 MB per file, and Aegis refuses any other file.
| Field | What to enter |
|---|---|
Evidence Name |
Filled in from the first file's name, and you can edit it. It applies only to a single-file upload. With several files, each item takes its own file name. |
Type * |
Required. The dialog opens on Document. The other
choices are Screenshot, Log,
Report, Configuration and
Other.
|
Source System |
Where the file came from, such as AWS,
Okta or Jira.
|
Link to Frameworks |
Hold Ctrl or Cmd to choose several. Until you choose one,
Link to Controls reads
Select a framework first.
|
Link to Controls |
The controls this evidence supports, from the frameworks you chose. |
Valid Until, Tags |
The expiry date, and tags separated by commas. |
Link to Vendor |
Optional. Use it for supplier audit reports or questionnaires. The
default is
None.
|
-
Drag files onto the drop zone, or select
browse files. Each file appears under the zone with a control to remove it. Then fill in the fields described above. -
Select
Upload. It stays greyed out untilEvidence Namehas a value, as in the capture, where no file has been added yet. Each file uploads in turn with its own progress indicator. The dialog then closes, and the new rows appear with anAwaiting reviewbadge. -
To stop without saving anything, select
×at the top right orCancel.
You can submit the form without a file, once you have typed an
Evidence Name. This records that an artefact exists in another
system without copying it into Aegis. The item then has no
Preview or Download action.
Reviewing evidence (four-eyes)
Open an item that shows Awaiting review. Under the breadcrumb and
title, the Four-eyes review panel explains that the evidence does
not count towards any control until someone other than its uploader approves it.
When a file is stored, the header also has a Download file button,
and Preview and Extracted Text panels follow the
review panel. The captured item has no stored file, so the screen goes straight
from the review panel to File Information, Dates,
Ownership, Tags and the
Collaboration panel.
-
Check the review badge. If it reads
Awaiting reviewand you did not upload the item,ApproveandRejectappear on the right of the panel. If you did upload it, the buttons do not appear. -
Read the file in the preview (when a file is stored), then select
Approve. TheApprove evidencedialog opens. -
Or select
Reject. TheReject evidencedialog opens and asks for a reason. -
To discuss the item before you decide, use the
Collaborationpanel further down. Type inAdd a commentand selectPost comment; the comment appears underComments, which readsNo comments yet.until then. Further down the panel,Reviewscan send aRequest reviewto a named reviewer with an optional due date.
-
Add a note in
Comment (optional). When you reject, this field becomesReason (required)and you must fill it in. -
Select
Approve. A confirmation appears and the badge changes toApproved. The panel now showsReviewed by,Reviewed onand your note asReview note. From now on, the evidence counts towards its linked controls. -
To leave the item undecided, select
Cancelor×.
When the item is linked to at least one control, the dialog also shows its
AI content review, read-only, so you can weigh the AI's advice
before you decide (see The AI assist, below). The captured item has no linked
controls, so the dialog shows only the comment field.
Evidence imported by the SharePoint connector shows Uploaded by
SharePoint connector. It still starts as a draft that a person must
approve, but because the connector counts as the uploader, the admin who
connected or synced it may approve it. The same applies to a file an external IT
supplier uploaded through an evidence request: the person who requested it did
not upload it, so may review it.
A few sources approve their evidence on creation: snapshots from a trusted,
read-only connector such as Entra ID, and evidence created by a vendor
questionnaire decision. These show
Approved with a note explaining why. A reviewer other than the
owner can still select Reject on them. An approval by a person is
final.
Rejected evidence stays in the locker with your reason and never counts towards a control; the uploader adds a corrected file as a new item. If a message says the evidence was already reviewed, someone decided first, so reload the page.
Working with approved evidence
-
Open an
Approveditem. The review panel showsReviewed by,Reviewed onand theReview note. -
Read
Version history, which appears once an item has more than one version. It lists every version with its number, badge, name, file name and date, and highlights the version you are viewing. The captured item shows three versions: twoSupersededand the current oneApproved. - Select an older version's name to open it. Superseded versions stay readable, but they no longer count towards any control.
-
In the
AI content reviewpanel, selectReview content (AI). The request is queued and the panel reads that it is reviewing the document against its controls; the result replacesNot reviewed yet.when it arrives. The panel appears only on items linked to at least one control. -
Select
Upload new version. The upload dialog opens again, set up to create a new version.
- Read the blue note. The new version starts as awaiting review. The current version keeps counting until someone other than you approves the new one, and only then is it marked superseded. It is never deleted.
-
Drop the replacement file. You can add only one file here. The dialog title
names the item you are replacing, and the name and type are filled in from
the current version. If the current type is not one of the six upload types,
the type falls back to
Document, as in the captured screen; change it if needed. -
Select
Upload. The new version joins the version history asAwaiting review. Until a reviewer decides on it,Upload new versionstays hidden. -
To stop without uploading, select
×orCancel.
Evidence written by a connector has no Upload new version button:
the connector delivers new evidence itself.
The rest of the detail page
Further down:
-
Extracted Text, for stored files: a status badge (Searchable text extracted,No text found,Text extraction queued,Text extraction failedorText extraction skipped) and an excerpt of the text read from the file. -
File Information: file name, size and content type. When a file is stored, it also shows the file's SHA-256, with aVerify Integritybutton that re-reads the file and reportsChecksum matchesor a failure. -
Ownership(owner, source system and, for connector imports,Uploaded by) andDates, includingValid Until. Tags, if any.- The controls, policies and risks this evidence is linked to.
- Any roadmap work that addresses this evidence.
-
The
Collaborationpanel, with comments and review requests.
An Entra ID snapshot has no stored file. Its detail page shows an
Entra ID snapshot
summary instead, with users, administrators and Conditional Access policies, and
a
Download export (JSON) button.
Link existing items with Link to Control in the list's bulk bar.
Each linked control on the detail page has an Unlink action for
people allowed to update controls; it asks for confirmation and removes only the
link, never the evidence. Controls of frameworks that are disabled or outside
your licence are hidden here, in the CSV export and in the AI features, not
deleted: re-enable the framework and the links return.
Checking that evidence keeps arriving
Collection Rules opens /evidence/collection-rules,
headed Evidence Collection Rules. A rule never creates evidence; on
your schedule it checks that a source has delivered something since the last
check. A miss records a Failed run and turns the rule's
Status to Error. The rules table shows
Name, Source, Evidence type,
Schedule, Status, Last run,
Next run, Enabled and Actions.
-
Select
Collection Rules, thenNew rule. A form appears. -
Enter a name and the
Evidence type. Choose aSource system(optionally a connector; one of the two is required), aFrequencyand aRule owner, then save. -
Use
Pause(orEnable),EditorDeleteto manage the rule. Deleting a rule stops the checks but keeps all the evidence the source delivered.
The AI assist
The four AI helpers are advisory. They describe and suggest, and a person decides; none of them changes a review status on its own.
-
Evidence Gaps (AI)lists controls in your enabled frameworks that have no linked evidence, and suggests a collection plan. -
Refresh Triage (AI)ranks your evidence by expiry and staleness, and suggests what to renew first. Saved briefings appear below the table and can become action items. -
AI Classifysuggests a category with a confidence level. The item's type changes only if you accept the suggestion. -
Review content (AI), on the detail page, reads the document's extracted text and judges it against each linked control. Each result shows a verdict (Adequate,Partially adequate,InadequateorInsufficient text), the control, the date and model, findings markedMetorGap, and suggested improvements. It is labelledAI advisory — human decides: it never changes the review status, coverage or control status. Once run, the button readsReview content again (AI).
Tips and limits
-
Aegis does not chase expiries. It sends no reminders as
Valid Untilapproaches. RunRefresh Triage (AI)or set up an alert in Workflows. - The preview works for PDFs and common images. Download other file types to read them.
-
Bulk
Exportgives you a CSV of item details, not the files themselves. -
The AI content review needs readable text. A scanned image with no extracted
text gets
Insufficient textrather than a verdict; if extraction is still running, wait and review again. A review can take a couple of minutes; if it runs longer, the panel asks you to check back later.
Where this connects
Approved evidence proves the controls in Compliance frameworks, which are watched in Control monitoring and mapped in Control mapping. Evidence also supports risks, policies and vendors. Snapshot evidence comes from the Entra ID connector, imported files from the SharePoint connector, and comments are covered in Collaboration. Before an assessment, see Audit readiness and the external audit walkthrough.