Allen
Jones

NIS2 Endpoint Evidence for Security Control Reviews

Allen Jones

Nov 10, 2026

11 min read

nis2 endpoint evidence

TL; DR

Endpoint evidence collected by IT teams supports management oversight and gives reviewers a basis for assessing endpoint controls within a wider NIS2 readiness review.

  • Management bodies oversee cybersecurity risk-management measures. Auditors, competent authorities, and customers may also need supporting records, depending on the review.
  • Patch results, policy audit records, and device-state checks help establish what changed, whether controls worked as intended, and which issues remain unresolved.
  • Hexnode UEM supports evidence collection through patch reports, policy audits, scheduled report delivery, and CSV/PDF exports.

What is NIS2 endpoint evidence and how does it support a NIS2 readiness review?

Endpoint evidence includes records that help reviewers assess security measures on devices, such as asset inventories, patch results, policy histories, and verification checks. In a NIS2 readiness review, these records support assessment of the organization’s endpoint security measures.

These records connect the expected security requirement to the action taken and the verified result. Identifying the affected devices and relevant dates helps reviewers determine what each record demonstrates.

Article 21(2) of the NIS2 Directive sets out cybersecurity risk-management requirements. The following endpoint records can support the assessment of specific aspects of those requirements:

  • Maintenance and vulnerability handling: Patch findings, installation results, and remediation checks.
  • Control effectiveness: Checks showing whether endpoint security measures operate as intended.
  • Cryptography and encryption: Device encryption status checked against applicable encryption policies.
  • Access control and asset management: Device inventories, ownership details, and relevant access configurations.

The wider review must also consider management oversight, incident reporting, business continuity, and cybersecurity training. More importantly, the organization’s legal or compliance team should confirm which national and sector-specific requirements apply.

For endpoint administrators, the next challenge is bringing the relevant records together and establishing what they show.

Why is endpoint evidence difficult to assemble for a NIS2 review?

Endpoint evidence becomes difficult to assemble when records show different parts of the same activity without clearly connecting them. Asset inventories identify the devices, policies define the expected settings, and change records show actions taken. Patch results and device checks help establish whether those actions achieved the intended result.

Imagine you’re preparing for a NIS2 readiness review. Your team sent a security update to employees’ laptops last week, and the deployment ticket is closed. When a reviewer asks which laptops completed the update, you turn to the device reports. Some show successful installation, others need a restart, and several have not reported back since deployment. To answer confidently, you need to connect each laptop to its installation result, request fresh checks where results are missing, and assign follow-up for outstanding work. The reviewer can then distinguish verified installations from devices that still need attention.

The example shows why a review needs to connect three types of evidence:

  • Intended settings: The security configurations and requirements expected on each device.
  • Recorded actions: The changes, assignments, or update deployments initiated to meet those requirements.
  • Verified results: The checks showing whether those configurations or updates took effect.

How do gaps in endpoint evidence affect security reviews?

When endpoint records miss affected devices, timestamps, change details, or verification results, reviewers may struggle to establish which controls were applied and whether they worked. Without a recorded outcome, a successful action may be indistinguishable from an unsuccessful or unverified attempt.

These gaps can lead to:

  • Missed patch follow-up: Without installation and restart results, administrators may overlook updates that failed or still require action.
  • Unexplained policy changes: Missing details make it harder to identify who changed a setting, when, and which devices were affected.
  • Additional investigation: IT teams may need to compare reports, logs, and tickets to establish what happened before deciding on corrective action.

These gaps weaken management’s visibility into outstanding risks and remediation progress. A NIS2 endpoint evidence checklist connects these stages across a defined review period, supporting endpoint-control assessment within the organization’s wider readiness review.

Thumbnail-Patch-management-One-pager
Featured Resource

Hexnode UEM for Patch Management

Get an overview of Hexnode’s patch deployment, vulnerability insights, and compliance tracking capabilities.

Get the one pager

What should your endpoint evidence checklist include?

To address these evidence gaps, reviewers need a clear connection between the devices in scope, the controls applied, and the results recorded. A NIS2 endpoint evidence checklist brings those details together and helps track outstanding issues.

ENISA’s NIS2 Technical Implementation Guidance provides advice and evidence examples for specified entities covered by Commission Implementing Regulation (EU) 2024/2690. The guidance is non-binding and may also inform reviews outside its stated scope.

Drawing on relevant practices from ENISA and NIST’s guidance on control assessment and enterprise patch management, the five steps below organize endpoint evidence collection into a recommended workflow. Adapt it to applicable requirements, national guidance, and your organization’s review procedures.

Step 1: Establish the devices, controls, and review period

Start by establishing the review period, along with the endpoint groups and security controls being assessed. Include the operating systems, ownership models, and locations represented, then check which devices are under management. Comparing the management inventory with procurement records or a maintained asset register can help identify discrepancies that need investigation.

For each endpoint, record:

  • Device identity: Serial number or asset identifier, alongside its management-system ID.
  • Ownership: Responsible owner and assigned user, where applicable.
  • Device details: Operating system, management status, and relevant device group.
  • Evidence dates: When the relevant device state was checked and when the report was collected.
  • Review scope: Whether the device is included or excluded, with the reason for any exclusion.

Step 2: Check patching results against required updates

With the review scope established, identify the updates each device needs under applicable requirements and your organization’s patch management policy. Then follow the records from detection through installation and verification to establish whether patching was completed.

For each affected device, collect:

Evidence  What to record 
Required update  Patch identifier and affected operating system or application 
Detection  Scan date and reported missing update 
Deployment result  Attempt date, installation status, and available failure details 
Restart status  Whether a restart remains necessary, where reported 
Verification  Verification date, method, and observed result 
Outstanding action  Responsible owner, remediation target, or documented exception reference 

Read these records together to distinguish completed updates from scheduled deployments, failed installations, and pending restarts, where reported. If the available information does not confirm completion, obtain an updated assessment or relevant device check.

For updates that remain unresolved, check progress against approved remediation targets and assign follow-up. Retain testing and approval records required by the patching procedure, with any deferred update linked to its justification, approval, and reassessment date.

Step 3: Trace policy changes to assignments and endpoint state

Alongside patching results, review whether device settings match the approved security configuration. Bring together the relevant policy, change history, assignments, and device checks to establish what changed and whether it took effect.

Check the following parts of the record:

  • Approved settings: The configuration the device should follow.
  • Change history: What was modified, by whom, and when, with required approval records.
  • Assignment and delivery: Which devices or groups were targeted and what delivery status is available.
  • Device verification: The observed settings and the date they were checked.

Retain before-and-after configuration details where available. If a record shows that a policy was edited without identifying the changed settings, note that limitation.

If the device settings differ from the approved configuration, use these records to investigate assignment changes, delivery failures, group-membership changes, or conflicting configuration sources.

Step 4: Record unresolved issues and assign follow-up

As you review patching results and device configurations, bring unresolved findings into a shared record so each issue can be tracked through follow-up. Distinguish confirmed failures from outcomes that remain unverified and identify approved exceptions separately.

For each finding, document:

  • Affected devices and issue: What failed or remains unknown, with links to supporting records.
  • Risk and response: The identified exposure and proposed corrective action or other treatment.
  • Accountability: Responsible owner, agreed target date, and required approval.
  • Exception and interim measures: Any approved justification, compensating measures, verification results, and reassessment date, where applicable.

For corrective actions, retain a follow-up check showing whether the issue was resolved. If someone with appropriate risk-acceptance authority accepts the remaining risk, preserve the decision and justification separately from successful remediation. Risk acceptance does not, by itself, satisfy or waive an applicable legal obligation.

Keep accepted risks subject to the organization’s review process so changes in exposure or operating conditions can trigger reassessment.

Step 5: Preserve the evidence and document the review

Once findings and follow-up actions are recorded, preserve the supporting evidence so another reviewer can understand what it shows. Include its source system, applied filters, covered devices, review period, observation dates, collection timestamp, and relevant time zone.

Keep observation and collection dates distinct. An encryption report downloaded today may reflect an earlier device check, so it cannot establish the device’s state throughout a previous review period. Assessing that period requires relevant historical records.

Retain original exports alongside your working analysis in an access-controlled repository, protecting them against unauthorized modification or deletion. Restrict access to sensitive information and apply retention periods based on applicable requirements and organizational policy.

Complete the review by documenting the findings, evidence limitations, unresolved actions, decisions, and review date. Link these to the wider readiness assessment so management and other reviewers can trace each endpoint finding to its supporting records and documented response.

How can Hexnode UEM support endpoint evidence collection?

Hexnode UEM provides patch reports and policy audit records to help administrators review update results and trace policy activity. Use these records alongside your endpoint evidence checklist to assess reported outcomes and identify gaps requiring follow-up.

Review patch status and outstanding updates

Begin with patch and update reports to see which devices need attention and which are reported as fully patched:

Report  Evidence-review use 
Devices missing patches  Identify endpoints with outstanding updates. 
Devices with failed patches  Identify unsuccessful deployments for investigation and corrective action. 
Devices pending reboot  Identify devices with updates awaiting a restart. 
Fully patched devices  Review devices reported as having all applicable updates installed. 

Check available last successful scan timestamps to establish when the underlying assessment occurred. Consider each report’s supported platforms, available data, and assessed updates when deciding what its results demonstrate.

Connect policy activity with device results

Alongside patch results, use Reports > Built-in Reports > Audit to examine policy activity. Under the Policy category, Policy Events tracks creation, edits, updates, and archiving. Policy Association and Dissociation tracks assignment changes. Available fields include technician identity, created time, policy version, and target details.

These details help establish who acted, when, and which targets were involved. Compare them with approved change requests and device-state checks to assess whether the intended configuration took effect.

Preserve records for the wider review

Once you have identified the relevant reports, use scheduled report delivery and CSV/PDF exports to support recurring collection. Download required exports into your controlled evidence repository during their 24-hour availability window in the Exports subtab.

Keep report filters, covered devices, and relevant dates with each export so reviewers can interpret its scope and timing. Apply your approved retention policy, with legal and compliance teams confirming how the records support applicable requirements.

Frequently Asked Questions (FAQs)

Screenshots can support a review, but exported reports generally make device-level reconciliation easier. Keep screenshots with their capture time, source, and scope, and retain the underlying records where available.

Record offline devices as having an unverified current state, alongside their last successful contact and relevant scan timestamps. Assign an owner to restore connectivity or investigate, then collect fresh evidence before marking the control as verified.

Compare the device identifiers, update identifiers, timestamps, and completion criteria in both records. A closed ticket may document completed administrative work while the endpoint still requires installation or a restart. Resolve the discrepancy using a fresh assessment and attach the verification result to the ticket.

No. It identifies devices reported as having all applicable updates installed within the reporting source’s coverage and assessment time. NIS2 readiness also requires assessment of other applicable technical, operational, and organizational measures.

Build a clearer endpoint evidence trail with Hexnode UEM

A useful endpoint review connects the devices in scope with the actions taken, the results verified, and the issues still requiring attention. Start with a representative device group and use your checklist to identify where supporting records are complete and where further checks are needed.

Request a Hexnode UEM demo to explore how patch reports and policy audit records fit your evidence collection process. Evaluate them against your review needs, with legal and compliance teams confirming how the records support applicable requirements.

Share

Allen Jones

Curious, constantly learning, and turning complex tech concepts into meaningful narratives through thoughtful storytelling. Here I write about endpoint security that are grounded in real IT use cases.