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.

Evidence cannot be deleted

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

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

  1. To add something new, select Upload Evidence at the top right. The Upload Evidence dialog opens (see the next section).
  2. Type a name in the Search evidence… box. The table narrows as you type. You can narrow it further with the type, source, tag and All review states filters. For example, choose Awaiting review to see what is waiting for a reviewer.
  3. Tick a row's checkbox. A bulk bar appears above the table, showing Link to Control, Export or both, depending on your role.
  4. Select an item's name. Its detail page opens at /evidence/{id}.
  5. Check the Review badge before you rely on an item. Only Approved evidence counts towards a control.
The Evidence Locker, with its AI actions, filters and Review column — /evidence.
The Evidence Locker, with its AI actions, filters and Review column — /evidence.

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.
  1. 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.
  2. Select Upload. It stays greyed out until Evidence Name has 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 an Awaiting review badge.
  3. To stop without saving anything, select × at the top right or Cancel.
The Upload Evidence dialog: drop zone, metadata fields and framework and control pickers — /evidence.
The Upload Evidence dialog: drop zone, metadata fields and framework and control pickers — /evidence.
Evidence without a file

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.

  1. Check the review badge. If it reads Awaiting review and you did not upload the item, Approve and Reject appear on the right of the panel. If you did upload it, the buttons do not appear.
  2. Read the file in the preview (when a file is stored), then select Approve. The Approve evidence dialog opens.
  3. Or select Reject. The Reject evidence dialog opens and asks for a reason.
  4. To discuss the item before you decide, use the Collaboration panel further down. Type in Add a comment and select Post comment; the comment appears under Comments, which reads No comments yet. until then. Further down the panel, Reviews can send a Request review to a named reviewer with an optional due date.
An evidence item awaiting four-eyes review, with its Collaboration panel — /evidence/:id.
An evidence item awaiting four-eyes review, with its Collaboration panel — /evidence/:id.
  1. Add a note in Comment (optional). When you reject, this field becomes Reason (required) and you must fill it in.
  2. Select Approve. A confirmation appears and the badge changes to Approved. The panel now shows Reviewed by, Reviewed on and your note as Review note. From now on, the evidence counts towards its linked controls.
  3. To leave the item undecided, select Cancel or ×.
The Approve evidence dialog — /evidence/:id.
The Approve evidence dialog — /evidence/:id.

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

  1. Open an Approved item. The review panel shows Reviewed by, Reviewed on and the Review note.
  2. 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: two Superseded and the current one Approved.
  3. Select an older version's name to open it. Superseded versions stay readable, but they no longer count towards any control.
  4. In the AI content review panel, select Review content (AI). The request is queued and the panel reads that it is reviewing the document against its controls; the result replaces Not reviewed yet. when it arrives. The panel appears only on items linked to at least one control.
  5. Select Upload new version. The upload dialog opens again, set up to create a new version.
An approved item with its version history and AI content review panel — /evidence/:id.
An approved item with its version history and AI content review panel — /evidence/:id.
  1. 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.
  2. 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.
  3. Select Upload. The new version joins the version history as Awaiting review. Until a reviewer decides on it, Upload new version stays hidden.
  4. To stop without uploading, select × or Cancel.
Uploading a new version of approved evidence — /evidence/:id.
Uploading a new version of approved evidence — /evidence/:id.

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:

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.

  1. Select Collection Rules, then New rule. A form appears.
  2. Enter a name and the Evidence type. Choose a Source system (optionally a connector; one of the two is required), a Frequency and a Rule owner, then save.
  3. Use Pause (or Enable), Edit or Delete to 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.

Tips and limits

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.