Using SharePoint for TISAX and ISO 27001 Evidence Management

Setting up metadata, versions, access and control links for evidence files speeds up audit preparation. Library structure, permissions and calendar flow.
Technical summary
Technology
SharePoint Online, ISO 27001, TISAX
Topic
Evidence management
Level
Intermediate
In this article8 sections

In audit week, most of the time goes not on discussing controls but on looking for evidence: whose email has the last access review, which folder holds the restore test, which is the approved version of the procedure? Both TISAX assessments and ISO 27001 audits cause the same problem. In organizations using Microsoft 365, SharePoint Online is enough to build a control-based, version-controlled evidence system without additional licenses. The structure below suggests a simple setup a small ISMS team can manage. Teams that want to build the evidence system technically can get support from our SharePoint document management and revision setup service.

Metadata instead of a folder tree

Putting evidence into folders such as “2026 / IT / Access” leads to duplication when one piece of evidence serves several controls. The same access review corresponds to one control in ISO Annex A and another in VDA ISA; it gets copied into two folders, one copy is updated and the other stays old. The auditor finds the old one. Instead, metadata is added to each file in a single evidence library:

Column Type Example
Check Multiple choice (managed list) ISO Annex A · access rights; ISA · identity and access management
Framework Multiple choice ISO 27001, TISAX, IATF 16949
Period Text or choice 2026-Q3
Owner People IT manager
Status Choice Pending / Uploaded / Reviewed
Confidentiality Choice Internal / Confidential

With views, lists such as “TISAX – missing evidence this quarter” or “Control-based evidence index” can be created in one click.

Two details at setup save time later. First, don’t leave the “Period” column as free text; if “2026-Q3”, “Q3 2026” and “2026-3Q” sit side by side in the same library, filters stop working. Use a choice list. Second, make the “Control” and “Period” fields required. A file uploaded without metadata is the library equivalent of folder chaos.

The control list: where evidence expectations come from

A separate SharePoint list holds the controls (SoA rows or VDA ISA controls): control number, description, owner, evidence frequency and expected evidence type. The “Control” field in the evidence library is linked to this list. That way, you can report which period’s evidence is missing for which control.

Technically, a lookup column is defined in the evidence library with the control number in the control list as its source. If the lookup column is set to allow multiple values, one file can be linked to several controls. In very large lists, the list view threshold can cause problems; indexing the filtered columns reduces this risk.

The “expected evidence type” field in the control list shouldn’t be left blank either. A definition such as “Access review: user list taken from the system + process owner approval” tells the person uploading evidence what’s sufficient. Without a definition, everything from screenshots to email threads gets uploaded.

Document management: there must be one approved version

  • Policies and procedures are kept in a separate library with major/minor versioning turned on.
  • An approval flow (Power Automate or built-in approval) is used for publishing; readers see only the approved major version.
  • Each document has owner, review date and classification columns.
  • Old versions are kept in the version history; the auditor can see the change trail.

A mistake you may come across is also distributing a PDF of the approved document by email. The version in the library gets updated, while the old PDF lives on on people’s desktops. In announcements, share a link to the document in the library, not the file. That’s the only way to protect the “single source of truth”.

Make minor versions (0.1, 0.2) visible only to editors. If an employee with read permission can see a draft version, an unapproved rule is perceived as being in effect.

Access and confidentiality

Evidence can contain sensitive information (network diagrams, permission lists, vulnerability reports). Site permissions should be role-based, external sharing should be turned off, and confidential evidence should be kept in a separate library or folder with narrower permissions. If your license supports them, sensitivity and retention labels provide extra protection. If the auditor needs access, time-limited read-only sharing or screen sharing is preferred.

Grant permissions by group, not by individual: “Evidence – Readers”, “Evidence – Contributors”, “Evidence – Owners”. Breaking inheritance on individual files and setting unique permissions makes it impossible to know who sees what six months later. The more broken inheritances there are, the harder management becomes. That’s why keeping confidential evidence in a separate library is a cleaner approach.

The evidence site itself is also an audit topic. Reviewing site owners and members every three months keeps you from having an access control finding in the evidence store itself.

Evidence calendar and reminders

A calendar is defined for periodic evidence (monthly log review, quarterly access review, restore tests). With Power Automate, reminders can be sent at the end of the period to the owners of records still marked “Pending”. This ensures evidence is collected as it’s produced, not just before the audit.

A practical flow is set up like this: at the start of the period, an empty “Pending” record is created in the evidence library for each periodic control in the control list; the owner uploads the file and sets the status to “Uploaded”; the ISMS manager reviews it and moves it to “Reviewed”. At the end of the period, the rows still “Pending” are the missing evidence report. No separate Excel tracking is needed.

Characteristics of good evidence

  1. Dated: It’s clear which period it belongs to.
  2. Clear source: System report, signed form, meeting minutes.
  3. Clear scope: Which system, location or user group it covers.
  4. Includes results and actions: Deviations found in the review and their fixes.
  5. No more information than needed: Passwords and unnecessary personal data are masked.

The file name is part of the evidence too. A rule such as “2026-Q3_AD-access-review_approved.pdf” instead of “scan_0042.pdf” tells you what the file is even if the metadata is lost. Make sure the system clock and server name are visible in screenshots; an undated screenshot is a claim, not evidence, in the auditor’s eyes.

Setup checklist

  • The evidence site is closed to external sharing, and permissions are group-based.
  • The control list is mapped one-to-one to the SoA or VDA ISA.
  • “Control” and “Period” are required in the evidence library, and “Period” is a choice list.
  • Major/minor versioning and the approval flow are on in the policy library.
  • The start-of-period record and end-of-period reminder flow are working for periodic controls.
  • A time-limited, read-only sharing method has been defined for auditor access.

Frequently asked questions

Is an extra license needed?

The basic library, metadata, versioning and approval flow are included in standard Microsoft 365 business plans. Advanced retention and sensitivity labels depend on the license.

Can files in a Teams channel be used as evidence?

Teams files are also stored in SharePoint; however, a separate evidence site provides more orderly management for control-based metadata and permissions.

How long should we keep evidence?

For at least one certification or label cycle and according to legal/contractual retention periods; the period should be defined in the retention policy.

To set up a SharePoint evidence library and map the control list to the SoA or VDA ISA, take a look at our Audit Evidence and Document Management with SharePoint service; for final preparation before the assessment, our TISAX pre-assessment preparation service.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles