Close your ISO 27001 SSH access control gaps. In under 30 minutes.
Ezeelogin maps directly to the privileged access, session logging, identity lifecycle and access revocation controls your auditor will check — out of the box, self-hosted, no cloud dependency.
Auditors require documented proof that every privileged access event was logged with user identity, timestamp, and activity. SSH keys alone leave no trail.
Ezeelogin logs every SSH session automatically — user, server, timestamp, full session recording. Exportable for auditors on demand.
ISO 27001 explicitly requires identities to be disabled or removed promptly when no longer needed. Manual SSH key removal across server fleets routinely fails this test.
Ezeelogin removes access to every server in a single action — seconds after a user departs, with a full audit trail of the removal.
Shared admin accounts violate 8.2(h). ISO 27001 requires each person to have a separate identity so privileged actions can be attributed to a specific individual.
Ezeelogin creates individual gateway identities per user. No shared root. Every action attributed. Segregation enforced by design.
ISO 27001:2022 control mapping
A direct map between the ISO 27001:2022 controls your auditor will check, and the Ezeelogin features that satisfy each one.
| Control | ISO 27001:2022 Requirement | How Ezeelogin satisfies it |
|---|---|---|
|
8.2
Privileged Access Rights |
Restrict and manage allocation of privileged access. Log all privileged access for audit. No shared admin IDs. Break-glass / just-in-time access for maintenance. |
|
8.15 Logging |
Produce logs of user IDs, timestamps, system access events and privileges. Protect logs against tampering. Support SIEM integration. |
|
8.16 Monitoring Activities |
Monitor networks and systems for anomalous behaviour. Establish baselines. Real-time alerting. |
|
5.15 Access Control |
Establish rules for physical and logical access. Apply least privilege and need-to-know principles. |
|
5.16 Identity Management |
Manage the full lifecycle of identities. Disable or remove identities when no longer required. |
|
5.18 Access Rights |
Provision, review, modify and remove access rights. Maintain a central record of granted access. |
|
5.3 Segregation of Duties |
Separate conflicting duties using RBAC. |
|
8.18 Privileged Utility Programs |
Restrict use of utility programs that override controls. Log all use. |
|
8.22 Segregation of Networks |
Group information services into segregated domains and control traffic between them. |
|
5.17 Authentication Information |
Control authentication information. Enforce MFA. Manage password lifecycle. |
|
Run the installer on any Linux server. Standard VPS setup completes in under 10 minutes.
Onboard servers individually or in bulk. Group by environment, sensitivity level or business unit.
Assign roles via RBAC. Enforce MFA. Set command restrictions. Every control documented.
Audit logs, session recordings and access reports are produced automatically from day one.
This single auditor question maps to at least five ISO 27001:2022 controls. Without a centralised SSH gateway, answering it requires assembling logs from dozens of servers, tracking down SSH key records, and hoping nothing was missed. With Ezeelogin, you pull one report.
Outcome: Gap report findings addressed with documented, repeatable controls.
Outcome: Auditor requirement met in one export. Certification unblocked.
ISO 27001 5.18 requires regular review of access rights. Without a central system, this means chasing server admins for lists that go stale immediately. With Ezeelogin: the access rights registry is always current. The review is a report, not a project.
Outcome: Continuous compliance evidence. No annual scramble.
ISO 27001 5.16(d) requires identities to be disabled “in a timely fashion.” Manual SSH key removal across dozens of servers is slow and error-prone — the exact pattern auditors flag. With Ezeelogin: one action removes access across every server and logs the removal with a timestamp.
Outcome: 5.16(d) satisfied. Full audit trail. Zero lingering access.
Enforce two factor authentication or MFA at the gateway using Google Authenticator, Duo, YubiKey, FIDO2, or RADIUS. Supports ISO/IEC 27001:2022 control 5.17
Remove a user's access to every server in a single action. Timestamped and logged. The documented, repeatable process 5.16(d) and 5.18(d) require.
Master-slave high availability ensures your access control infrastructure meets the Availability requirements across 5.15, 8.14 and business continuity controls.
All access routes through one jump server. Production servers never directly exposed. Supports network segregation requirements under 8.22.
Assign least-privilege access by role, group or individual server. No user touches a server they aren't explicitly authorised to access. Satisfies 5.15 and 8.2.
Every SSH session recorded and replayable. Timestamped, searchable by user, server or date. The primary evidence artefact for 8.15 logging requirements.
Central record of access rights granted to every user across every server. Always current. Supports periodic access rights reviews required under 5.18.
Whitelist or blacklist specific commands per user or group. Restricts use of privileged utility programs as required under 8.18. All execution logged.
Runs entirely on your infrastructure. Session data, logs and access records never leave your environment — critical for defining your ISO 27001 ISMS scope boundary.
Yes. Ezeelogin generates timestamped session logs containing user IDs, server identifiers, and command histories—the specific audit evidence referenced in ISO/IEC 27001:2022 controls 8.2(j) and 8.15. Session recordings provide non-repudiable evidence of the exact actions performed during privileged access. Many organizations use Ezeelogin exports directly as audit evidence.
Yes, significantly. Because Ezeelogin runs entirely on your own infrastructure, your access logs, session recordings and identity data stay within your ISMS boundary. This simplifies your scope documentation and avoids the third-party cloud risk assessment required when audit evidence is held by a SaaS provider.
The most common gap is session-level logging — most organisations have system-level logs but not full per-session SSH audit trails with session replay. The second most common gap is documented, timestamped access revocation. Both are explicit ISO 27001:2022 requirements (8.15 and 5.16/5.18) that SSH key management alone cannot satisfy.
Yes. Ezeelogin logs can be exported and ingested into SIEM platforms. ISO 27001:2022 control 8.15 references SIEM as the recommended mechanism for log analysis and alerting — Ezeelogin provides the structured SSH access logs that feed into it.
Simple, server-based pricing. Your subscription is based on the number of servers added to the gateway, allowing you to scale your infrastructure without being limited by the number of users accessing the system. See full pricing →
