ISO 27001 and TISAX Evidence in a Helpdesk System

What evidence does a helpdesk system produce for ISO 27001 and TISAX? Role-based access, audit trails, change and incident records, retention, and common evidence gaps.
Technical summary
Technology
ISO/IEC 27001:2022 Annex A, VDA ISA
Topic
Helpdesk audit evidence
Level
Intermediate
In this article5 sections

When an auditor asks for the record of a security incident, when a departing employee’s account was closed, or who approved the last change on a server, and the answer is scattered across emails, the control can’t be proven even if it was applied. IT support processes are examined directly in ISO 27001 and TISAX audits. A well-designed helpdesk produces this evidence not as a separate “audit preparation” task but as a natural output of daily work. Below we explain which controls a helpdesk can support and what to watch for in the design.

Let’s set the boundary up front: A helpdesk system on its own doesn’t provide ISO 27001 conformity or a TISAX label. It makes it easier to apply and evidence controls; conformity is addressed together with scope, risk assessment, policies and independent assessment.

Which control areas are supported?

Control area (ISO/IEC 27001:2022 Annex A theme) The helpdesk’s contribution Evidence to show in the audit
Information security incident management Recording security incidents as a separate type, classification, response and closure Incident record, timeline, closure summary, lessons-learned note
Access rights and identity lifecycle Approved workflow for joiner, role change and leaver requests Request, approver, time of implementation
Change management A change record type; fields for risk, testing, rollback plan and approval Approved change records
Asset management Linking tickets to device/application records Asset–ticket relationship
Logging and monitoring Immutable ticket history and timestamps Ticket activity history
Supplier relationships Tracking tickets handed over to suppliers, and their durations Supplier waiting time report

In ISO/IEC 27001:2022 Annex A, these areas fall under organizational and technological controls. Incident management relates to controls 5.24–5.28 (planning, assessment, response, learning from incidents, collection of evidence), access rights to 5.15 and 5.18, change management to 8.32, asset inventory to 5.9 and logging to 8.15. Mapping controls to record types using these numbers lets you speak the same language as the auditor.

The VDA ISA catalog used in TISAX assessments also expects similar evidence on incident management, identity and access management and change management; in the maturity assessment, it matters that the process is defined, applied and measured. In practice this means: saying “there’s a process” isn’t enough. You must show that the process works the same way in every record and that its results are reviewed periodically.

8 points to watch in the design

  1. Role-based authorization: User, support staff, team lead, manager and auditor roles should be managed with Entra ID security groups; no individual permissions should be granted.
  2. Least privilege: Support staff should see only their own teams’ queues; security incidents should be open only to the incident response team.
  3. Audit trail: Status, priority, assignment and resolution changes should be kept as separate activity records; version history shouldn’t be disabled.
  4. Timestamps: Created, first response, resolved, closed and reopened times should be stored in separate fields.
  5. Personal data: Unnecessary personal data shouldn’t be collected in ticket descriptions; sensitive attachments should be kept in a separately permissioned library, and export rights should be restricted.
  6. Retention and disposal: A retention period should be defined for closed records and applied with Microsoft Purview retention labels or a scheduled archive flow; disposal should be approved and recorded.
  7. Approvals: For permission and change requests, the approver’s identity and decision should be written to the ticket; an approval email alone isn’t evidence.
  8. Periodic access reviews: Support team and administrator groups should be reviewed quarterly, and the result recorded.

Most of these items are decisions made on setup day and are expensive to fix later. In a list with version history disabled, past changes can’t be recovered. A site that has grown with individual permissions can only be moved to a group-based model by untangling every permission one by one. An access review is a matter of minutes if it can be done through group membership alone; if there are individual permissions, every library and every item has to be examined separately. That’s also the first place the auditor looks. Who can see what, who approved it and when was it last checked?

The evidence gaps we see most often in the field

The first gap is in the leaver process. The notification from HR enters the helpdesk as a ticket, but when the account was actually disabled isn’t written to the record. The auditor picks a few leavers as a sample and compares their leaving date with the account closure date. If the record only says “completed”, this comparison can’t be made. The account closure time, the person who did it and the list of systems closed should be separate fields.

The second gap is emergency changes. An intervention at night is applied first and the record is opened later, or never. An emergency change type is defined, a deadline is set for retrospective approval, and records that exceed this deadline appear in the report.

The third gap is not separating security incidents from ordinary faults. If a user’s “I received a suspicious email” report closes in the same queue, as the same type, as a printer fault, no incident management evidence is created. Support staff need to be able to turn a ticket into a security incident with one click, at which point the record is closed off to everyone but the authorized team.

What the three gaps have in common is the same: the work was done, but the record doesn’t carry the detail that proves it. The solution isn’t to add a new process but to put the right mandatory fields on the existing record types. If support staff can’t move on without filling in these fields when closing a ticket, the evidence creates itself. The number of mandatory fields is also kept small; a form that asks for ten fields on every record produces randomly filled fields.

Is the Microsoft 365 audit log enough?

Microsoft Purview auditing records user activities in SharePoint and other services; but the retention period depends on the license plan (180 days by default in standard auditing, longer with Audit Premium). If the audit cycle is a year or longer, the application’s own activity history and periodically exported reports should be the main source of evidence.

In addition, the audit log answers the question “who changed which item, and when”; it doesn’t answer “why was this change made, and who approved it”. Approval and justification must be inside the work record. The Purview log is complementary evidence for verifying that the work record wasn’t changed afterwards.

How is the evidence pack prepared?

Before the audit, the following reports are prepared for the period: a list of security incidents with closure notes, the approval history of access requests selected for sampling, change records and approvals, an SLA compliance report, and the minutes of the support team access review. Storing the reports with versioning in a controlled document library strengthens evidence integrity. For how control–evidence mapping is managed within the ISMS, see Eretek Compliance’s evidence management service.

Don’t try to prepare the pack a week before the audit. If reports are generated automatically each month or quarter and land in the same library, audit week is spent only on sample selection and questions. The query that produces each report should also be documented; when the auditor asks “is this list complete?”, the answer is the filter criteria themselves.

As a checklist, the following are verified before the audit:

  • Mandatory fields can’t be left empty for any record type.
  • Closed records can’t be edited by support staff; corrections are made with a new activity record.
  • The auditor role is read-only and time-limited; its access is recorded.
  • Disposal of records whose retention period has expired is approved and minuted.
  • Accounts that should have been removed in the last access review have actually been removed.

Frequently asked questions

How long should we keep helpdesk records?

The standards don’t specify a period; it’s determined by the organization’s retention policy, contracts and legislation. What matters is that the period is defined and applied, and that disposal is recorded.

What if the auditor wants direct access to the helpdesk system?

A time-limited, read-only auditor role can be defined. Alternatively, ticket history reports are exported for sampling; in either case, access must be recorded.

Is it possible to get ISO 27001 certification with a helpdesk?

No. A helpdesk produces evidence for controls such as incident, change and access management. Certification is achieved through scope, risk assessment, policies, internal audit and an independent certification audit. The next step for connecting helpdesk records to the organization-wide information security management system is ISO 27001 consulting and ISMS implementation.

For setup steps, see the Microsoft 365 helpdesk setup guide; for implementation, see our Microsoft 365 integrated helpdesk and SLA system service.

Support

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

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles