EterShieldDocs
etershield.com
PTLog in
Guide/People and quality

Personnel Security (HR Security)

The Personnel Security module implements the requirements of ISO 27001 (Section A.6: Human Resource Security) and the GDPR as applied to the employee lifecycle.

Go to Menu → People.

28.1 JML Lifecycle

Joiners, Movers and Leavers: access management driven by events in the employee lifecycle.

Event Description
Joiner New employee: provisioning of initial access
Mover Change of role or department: review and adjustment of access
Leaver Departure from the organisation: revocation of all access

Each event records: employee, event date, owner, status (Pending / In Progress / Completed) and the list of affected systems.

Flow:

  1. Create a JML event with a type and an associated employee
  2. Add the systems to provision or revoke
  3. Mark each system as completed
  4. The event closes when all items are Completed

Go to JML Lifecycle. The detail of each process opens from the list.

Automatic steps

With the Microsoft 365: accounts and licences (write) integration connected, processes include steps that EterShield runs by itself, instead of steps you only tick off by hand. Without the integration, the equivalent manual steps remain. The default steps are:

Type Automatic steps
Joiner Notify the manager; hand over equipment from stock; create the account the day before; add to groups (with approval); assign the licence
Mover Notify the manager
Leaver Notify the manager; request return of equipment; disable the account in EterShield (with approval); block sign-in (with approval); end sessions; release licences (with approval); remove the device from Intune (with approval, only if the optional permission has been granted)

Each scheduled step runs on the process date (or the day before, in the case of account creation), and the system checks every 5 minutes for steps whose time has come. On each step you can Preview (shows what it will do without writing anything), Run now, Try again (if it failed) and, on equipment hand-over steps, Choose equipment from stock. The status of each step is: Scheduled, Awaiting approval, Running, Done, Failed or Nothing to do. If the error is temporary, the system retries up to 3 times; if data is missing (for example, the account does not exist), the step fails straight away and says why. A step that stays stuck running for more than 15 minutes becomes Failed and is never retried automatically, because the write may already have been done: check in Microsoft 365 and click Run now. There is a limit of 30 writes per hour to Microsoft 365 per organisation; when it is reached, steps are rescheduled 15 minutes later without failing.

Who can do what: running, previewing and choosing equipment requires the permission to run JML (SUPER_ADMIN, ADMIN and MANAGER). Users whose access is restricted to one entity cannot run or approve steps, because JML processes belong to the whole organisation.

Four eyes on destructive steps. Steps that block accounts, remove licences, change groups or remove devices are set to Awaiting approval and only run after someone else clicks Approve, who must be SUPER_ADMIN or ADMIN. The person who created the process cannot approve it ("Needs approval from another person"). The approval is recorded in the audit log, and whoever is due to give it receives a notification.

Protected accounts. On the write integration card (Settings, Integrations), the Protected accounts list (up to 50, one per line; ADMIN and SUPER_ADMIN only) lists the accounts that EterShield never blocks, and never ends their sessions, removes their licences or removes their devices (for example, global administrators and emergency accounts).

Connecting the write integration. On the Microsoft 365: accounts and licences (write) card (Settings, Integrations; ADMIN and SUPER_ADMIN only), enter the Directory (tenant) ID, the Application (client) ID and the Client secret of an app registration created solely for EterShield in Entra ID, the country for new accounts and the licence to assign to joiners. The secret is stored encrypted and is never shown again. EterShield never stores the initial password: first-day access is a Temporary Access Pass, delivered in a manual step.

Application permissions Status
User.ReadWrite.All, GroupMember.ReadWrite.All, LicenseAssignment.ReadWrite.All, User.RevokeSessions.All Required, with administrator consent. If any is missing, the card refuses to save and lists the ones that are missing
DeviceManagementManagedDevices.Read.All Optional: read Intune devices (section 52)
DeviceManagementManagedDevices.PrivilegedOperations.All Optional: remove equipment on departure and lock the screen of a lost device
Application.Read.All and DelegatedPermissionGrant.Read.All Optional: list the OAuth applications with access to Microsoft 365 (section 52)

Never request Directory.ReadWrite.All or RoleManagement.ReadWrite.Directory: EterShield does not use them. When you add an optional permission in Entra ID, click Sync now so that it is recognised.

Opening processes from Entra ID. The card has the option Open JML automatically from Entra ID (ADMIN and SUPER_ADMIN only; off by default). When on, every 15 minutes EterShield compares the directory: a new, active account opens a Joiner process, and a disabled or deleted account opens a Leaver process. The first run only records the accounts that already exist and opens nothing. Guests are not counted, and a duplicate process of the same type and email is not opened within 60 days. As a safeguard, if a single run detects more than 20 changes, it opens no processes, notifies the administrators and waits: to resume, switch the option off and on again.

PDF report and evidence. In the process detail, the report button downloads the process PDF for the auditor (requires the Personnel Security module; limit of 5 per minute). When the process finishes, EterShield also stores evidence with the summary and its SHA-256 fingerprint, once per process, linked to the access management controls (for example, ISO 27001 A.5.15, A.5.16, A.5.18, A.6.5 and NIS2 21.2.i; for Portuguese entities covered by the RJC, also RJC control Article 27(1)(h)). Ticking, unticking or skipping a step by hand is recorded in the audit log. Step titles are created in the language of the entity or of the interface.

28.2 Access Reviews

Access Reviews are periodic reviews of the access granted to employees, ensuring the principle of least privilege.

Process:

  1. Create a review with a period and scope (all users, by department, or by system)
  2. For each listed user, the reviewer decides: Approve (keep access) or Revoke (revoke it)
  3. The decision is recorded with date, owner and justification
  4. Completed reviews serve as evidence for ISO 27001 A.9.2.5

Go to Access Reviews.

28.3 Background Checks

Record of background checks carried out on employees or candidates.

Each record includes:

  • Type of check (criminal, references, qualifications, financial)
  • Status (Pending / Completed / Failed)
  • Date carried out and expiry date
  • Verifying entity
  • Internal owner

GDPR note: Background check data is treated as special category data (Art. 9 GDPR). Access is restricted to users with permission to view special-category HR data.

Go to Background Checks.

28.4 Disciplinary Process

Recording and management of disciplinary processes, with enhanced protection of personal data.

Data protection (GDPR Art. 9): The fields incidentDescription, actionTaken and notes are encrypted with AES-256-GCM before being persisted to the database. Plaintext is never stored. Decryption happens only in the presentation layer, for users with permission to view disciplinary processes.

Process statuses: Under Investigation → Hearing Scheduled → Decision Made → Closed

Each process records: employee, type of infringement, start date, status, decision and appeal deadline.

Go to Disciplinary Process.

28.5 Training Compliance

Monitoring of mandatory training per employee, with automatic expiry alerts.

Field Description
Training Name and type (ISO 27001, GDPR, Safety, Operational)
Status Pending / Completed / Overdue / Waived
Deadline Due date for completion
Validity Certification expiry date
Evidence Certificate or attendance record (upload)

The compliance dashboard shows the completion percentage by team and by training type. Overdue training generates automatic tasks for the owner.

Go to People (HR Security) (Training tab).

28.6 Data Subject Requests (DSR)

Management of Data Subject Requests in compliance with GDPR Articles 15-20.

Supported request types:

Type GDPR article Description
ACCESS Art. 15 Data subject requests a copy of their data
RECTIFICATION Art. 16 Correction of incorrect data
ERASURE Art. 17 Right to be forgotten
PORTABILITY Art. 20 Export of data in a structured format
OBJECTION Art. 21 Objection to processing

Legal deadline: 30 days from the date of receipt (Art. 12 GDPR). The system automatically alerts you when the deadline is approaching (7 days before).

Flow:

  1. Create the request with the type, the data subject's identity and the channel of receipt
  2. Assign it to an owner to handle
  3. Record the actions taken and documents generated
  4. Close the request with the response sent to the data subject

Go to Data Subject Requests (DSR). The detail of each request opens from the list.

Response templates. In the request detail, choose the Response template and the Template language (Portuguese or English) and click Use template. Templates exist for access, rectification, erasure, restriction, portability and objection (not for automated decisions). Fields in curly braces {{...}} must be filled in by you before sending. If you have already written response text, the Replace current text option prevents you from losing it by accident.

Exporting data subject data (portability, Art. 20). On the request, the export button (JSON or CSV) delivers the map of RoPA activities linked to the request: purpose, categories, legal basis, retention, processor and international transfer. The data subject's own data has to be extracted from the systems and added by the DPO. Requires incident permission and access to the entity; the export is recorded in the audit log.

Public privacy and cookie notice. On the data subject requests page, the Public privacy and cookie notice card (requires the permission to change settings) lets you Turn on or Turn off publication of the notice at /privacidade/<organisation-identifier> (the English version at ?lang=en), without signing in. Enter the privacy contact email and click Save. The text is built from the active RoPA activities (purpose, legal basis, categories, retention period and transfers); it never includes security measures, processor names or internal notes. The notice links to the public data subject request form, if that is turned on, and otherwise to the contact email. The cookie note mentions only strictly necessary cookies, with no analytics. The text is a template: legal validation is the organisation's responsibility. When turned off, the link stops working. Changes are recorded in the audit log.

EterShield, an Eter Growth platform