IT and Devices Module
The IT and Devices module (29 EUR on the price list) provides a single record per machine, licences and applications, and a portal for requests to IT. It is off by default: it only becomes active by contract, by super-administrator activation, or if the organisation already has devices registered. Trial periods and discontinued plans do not include it. Without the module, the pages no longer exist and actions respond "module not active".
It takes up three menu entries: Devices, Licences and IT Requests.
Single device record
Under Devices there is one record per machine, linked to the person who uses it, with the sources underneath. You can filter by No owner, No agent, Not seen in 30 days and Encryption not confirmed. The device status is: In stock, Assigned, To be returned, Returned, Lost or Retired; ownership is "Company-owned" or "Personal (BYOD)".
How sources are merged. Reconciliation runs every hour and merges the sources for the same machine in this order: device serial number, motherboard serial number, MAC address and machine name. Serial numbers merge on their own. The MAC only merges if no serial number contradicts it and, when the serial number is missing on one side, if the machine name also matches (docks and adapters move between machines). An identical name on its own never merges: it goes to the review queue. The reasons that send a case to the queue are: several candidates, different serial numbers, MAC without a serial number, duplicate from the same source and only the name in common. A Wazuh source with no signal for more than 7 days is considered stale and does not block another of the same type (for example, after reinstalling the agent).
Merging two records by hand. If the same machine is in two records, open the one you want to keep and use Merge with another record: choose the other one (those with the same name appear first) and confirm with Confirm: merge and delete the other. The chosen record is deleted; the sources, assignment history and Wazuh agent move to the one that remains; the owner, asset and entity only move over if the one that remains has them empty. The system refuses to merge records with different owners (return the device first) or different entities. The merge is recorded in the audit log. Who can do this: SUPER_ADMIN, ADMIN and MANAGER.
Sources
| Source | What it provides | How to connect |
|---|---|---|
| Wazuh | SIEM agents: system name, motherboard serial number, network interfaces | Settings, Integrations |
| GLPI | Computers from the inventory: device serial number, MAC, motherboard. There can be several GLPI instances in the same organisation | Settings, Integrations |
| Intune | Compliance, encryption, operating system and primary user (evidence of owner) | Via the Microsoft 365: accounts and licences (write) integration, with the optional device read permission |
| Fleet | Managed devices (MDM): serial number, operating system, disk encryption and compliance | Fleet card in Settings, Integrations: base URL and API token of an API-only user with the Observer role. ADMIN and SUPER_ADMIN only |
When sources disagree, the order of priority is: Intune, Jamf, Fleet, Wazuh, GLPI and, lastly, the manual record. EterShield only reads hardware, network, operating system, encryption and compliance: never installed applications, location, local accounts or usage. Fleet brings up to 500 devices per sync and the address is always converted to https.
Two types of control test use this record: encrypted devices and devices with recent contact. A device with unknown encryption counts as not encrypted, and with no active devices the result is "fail".
Licences and shadow IT
Under Licences you see the Microsoft 365 subscriptions with seats purchased and assigned, the monthly cost, waste, idle seats (disabled account or person who has already left) and renewals in the next 60 days. Microsoft does not provide prices: use Edit to enter the cost per seat per month, the cycle and the renewal date. Sync now updates the list (there is also a daily sync). EterShield warns you 30 and 7 days before each renewal and shows them in the calendar. Viewing and syncing requires access to the devices module (read) and editing requires write permission on it; access restricted to one entity does not see this page.
The Applications with access to Microsoft 365 section lists the third-party applications that someone has given OAuth consent to (shadow IT). New ones appear awaiting approval: use Approve or Withdraw approval. The risk comes from the permissions requested: high (write, read mail, files or the directory), medium (read) or low (sign-in and profile only), and "whole organisation" indicates administrator consent for everyone. This list requires the optional application read permissions. When a leaver process releases a licence, the value released appears in the summary.
IT Requests
Under IT Requests, anyone can ask for what they need (access to an application, new laptop, lost device, other) with New request, choosing the type and describing what they need. The lists are My requests, IT queue and All. Requesters only see and comment on their own; cancelling is for the requester or IT. The people who manage the queue and the catalogue are SUPER_ADMIN, ADMIN and MANAGER; the other roles can only make requests. With access restricted to one entity you can only make requests.
Catalogue. Under Catalogue, IT edits the request types: name, description, approval (no approval, or approval by another IT person), deadline in hours, written procedure, automatic action and whether it appears in the portal. The base types are Application access (approval, assigns the Microsoft 365 licence, 24 h), New laptop (approval, 120 h), I lost a device (no approval, 4 h) and Other (72 h). Procedures are searchable by the assistant.
Approval by another person. The person who made the request never approves it ("You made this request: someone else must approve it"). Once approved, the application access request assigns the chosen licence and closes itself; if there are no free seats, it stays open for IT to handle. The type that assigns licences cannot be left without approval.
I lost a device. This request only accepts a device that is assigned to you (IT can specify any) and there is a maximum of 3 per person per day. When it is created, EterShield opens a security incident (physical security, medium severity), ends the sessions of your Microsoft 365 account and locks the device screen in Intune (if the optional permission has been granted). The result of each step is recorded; anything that fails is flagged for IT to do by hand. The request stays open: changing passwords, assessing the CNPD notification (72 hours) and marking the device as lost are for IT. Protected accounts do not have their sessions ended.
Each request has a deadline (counted from approval, or from creation if it does not need approval); EterShield warns you 4 hours before and when it passes. Whoever requests, approves or handles it is notified.
IT privacy package
This module processes workers' data. The organisation is the controller and EterShield is the processor. Under Devices, the Prepare now button (or the notice at the top) opens the equipment privacy page, where Create as draft creates, in one go and without duplicates:
- 4 RoPA activities (devices, access and JML, licences, IT requests), under review
- 1 LIA (legitimate interest in the security of systems)
- 1 DPIA of remote monitoring means (Labour Code, Articles 20 and 21)
- 4 retention periods: device assignment history 1 year after return; JML reports 5 years after the end; released licence seats 1 year; closed IT requests 2 years
Everything starts as pending review: adapt it to the organisation and validate it with the lawyer or the DPO before approving (DPIA approval uses the permission to approve DPIAs, section 54). It requires write permission on devices and permission to create policies. Retention only deletes on its own in organisations that have set the rule to automatic mode. The package includes the notice to workers, with a Copy button: send it before turning the module on (GDPR Arts. 13 and 14; Labour Code, Art. 21) and adjust the contact for exercising rights.
Measures already in place: inventory of hardware and network only, with no software or usage history; minimum permissions, a limit on writes per hour and four eyes; with BYOD only company data is removed; no location, screen capture or activity logging; last use of licences is not collected.