Syteca 7.24 shifts the focus to operations. The release strengthens credential governance, makes privileged Linux access terminal-native and introduces Heartbeat, a status check for vault passwords. This article assesses the new capabilities soberly and distinguishes them from features already established since version 7.21. Furthermore, it identifies which organisations should prioritise the update. Target audience: CISOs, PAM administrators and IT managers in Switzerland and the wider DACH region.
Why Syteca 7.24 matters for PAM and insider threat management
Syteca combines Privileged Access Management, insider threat management and user activity monitoring on a single platform. A new release becomes relevant when it reduces operational complexity, improves audit readiness and measurably lowers the risks associated with privileged access paths. This is precisely where 7.24 comes in. The focus lies on reliable credential governance, less friction in administration and native support for the environments that teams actually operate. That scope ranges from Windows service accounts to the Linux terminal. Consequently, the release primarily strengthens PAM operations. Through session recording and comprehensive logging it also feeds directly into the evidence chain of insider threat programmes. This assessment is based on the official release announcement from Syteca.
Rebranding in brief: Syteca is the successor brand to Ekran System. For existing customers this matters because the vendor is consolidating its solution portfolio under the new name. Core functions such as PAM, session recording and user activity monitoring continue to evolve. In audits, therefore, organisations can clearly demonstrate that existing control mechanisms such as the logging of privileged activities remain intact.
Syteca 7.24 puts operational reliability and credential governance at the centre.
The essentials at a glance: the priorities of Syteca 7.24
- Service account discovery for Windows: automatic detection of service accounts, including dependency transparency and onboarding into the vault.
- PACM for the Linux terminal: privileged sessions launched directly from the command line, with unchanged governance.
- Heartbeat: status verification for vault passwords to detect password drift early.
- ACB API expansion: manage secrets, folders and users via API with a more flexible token model.
- Password manager: revised interface with clearer navigation for daily administration.
The new features in Syteca 7.24 in detail
Service account discovery and onboarding for Windows
Syteca already detects privileged accounts in Active Directory and Linux environments. Version 7.24 extends discovery to Windows service accounts, that is, local or domain accounts under which services, scheduled tasks and IIS application pools run. These accounts often have extensive rights, unclear ownership and static passwords, which makes them a typical blind spot in PAM programmes. The decisive point is dependency transparency. Before onboarding or a password change, Syteca shows which services, tasks and application pools depend on a given account. After onboarding, the platform takes over password rotation. It starts or stops dependent services automatically when needed so that operations continue without interruption. Discovery also detects and flags Group Managed Service Accounts, yet deliberately does not onboard them, since Active Directory manages their passwords natively.
PACM: privileged sessions directly in the Linux terminal
With the native PAM Connection Manager, version 7.24 brings access management to where Linux administrators, DevOps and SRE teams already work. Using the pacm command, users open the connection manager directly from an SSH or local terminal session. From there, they list and filter available secrets and start SSH or Telnet sessions to target systems without any detour through browsers or Windows jump servers. Governance remains identical: approval workflows, password checkout, time-window restrictions and session recording continue to apply. In addition, the release provides a unified Linux x64 agent with full SELinux support, which broadens platform coverage without requiring a separate deployment path.
Heartbeat: verify password status instead of assuming it
Heartbeat checks whether credentials stored in the vault still work on the target system. It addresses an underestimated operational risk: if someone changes a password outside Syteca, the vault drifts out of sync. Access then fails at the worst possible moment. The check runs on schedule or on demand and returns one of three statuses per password. Valid means the stored password works. Invalid means the account requires resynchronisation. Failed means the check could not complete, for example because the target system was unreachable. Syteca logs every check for audit purposes. If a scheduled check identifies an invalid password, the platform pauses automatic checks for that secret. An administrator then decides on rotation, reconnection or analysis. For emergency and break-glass access, this delivers a tangible gain in reliability.
Application Credentials Broker: expanded API for automation
The Application Credentials Broker is the integration point through which external systems, scripts and applications retrieve secrets at runtime. Version 7.24 expands the corresponding API significantly: in addition to secret values, folders and users can now also be managed via API. Furthermore, the authentication model becomes more flexible. All user types can issue tokens with configurable lifetimes and optional IP restrictions. For DevOps and platform teams, this translates into fewer hard-coded passwords, cleaner secret lifecycles and a more natural integration into infrastructure automation. Traceability of secret delivery remains fully intact. In this way, secret sprawl is curbed at its root.
Password manager with revised interface
Password management receives a tidier layout and improved navigation. The clearer hierarchy reduces effort in routine administration and shortens the learning curve for new users. It is no spectacular feature. However, in the daily work of teams that manage approvals and maintain secrets, such improvements add up to measurable efficiency gains.
Context: what has been established since 7.21
To place Syteca 7.24 in context, it helps to know the foundation laid by release 7.21. It includes agentless browser access via the Web Connection Manager, sensitive data masking in recordings and live views, as well as smoother session playback. The trade press has documented this, for example devops.com and Security Boulevard. Occasionally these functions appear incorrectly in overviews of newer releases; in fact, they already belong to the established core. Version 7.24 builds on them rather than replacing them. Consequently, the combination of agentless access, masking and the new operational features forms a continuous chain: controlled connection, reliable credential basis and privacy-compliant analysis.
Update recommendation and practice for Syteca 7.24
Our recommendation is nuanced. Three groups benefit most. First, Windows-heavy environments with a large legacy of service accounts: there, discovery with dependency transparency enables rotation without fear of outages for the first time. Second, Linux and DevOps teams that have long perceived privileged access as an awkward fit in their terminal workflow. Third, organisations pursuing automation initiatives that want to deliver secrets in a controlled manner to pipelines and applications. For monitoring-only setups without vault usage, however, the update can be bundled into a regular maintenance window.
Notes from project experience for a smooth transition: test the end-to-end chain in staging, from request and approval through access, session review and reporting. Inventory service dependencies before the first onboarding. Furthermore, define heartbeat schedules along with an escalation process for invalid passwords. Set token policies for the ACB regarding lifetime and IP restrictions. In addition, plan a short enablement for administrators so the team can use the revised navigation of the password manager productively from day one. Finally, document a clear rollback path.
Practical check for Swiss companies:
Compliance: Logged Heartbeat checks, traceable secret delivery and session recording support audit requirements such as ISO 27001 and accountability duties under the revised FADP.
Operations: Dependency transparency for service accounts and automatic service handling during rotation clearly reduce the risk of self-inflicted outages.
Risk management: Terminal-native access with unchanged governance closes the gap between security policies and lived DevOps practice, a frequent cause of shadow workflows.
Further information and advice
Are you planning the upgrade to Syteca 7.24, or evaluating PAM and insider threat use cases holistically? We support you with assessments, hands-on demos and a clear roadmap. The scope ranges from feasibility checks and role and approval concepts to production rollout. The audit and compliance assessment for Swiss companies is included.
🎯 Key takeaways for decision-makers
A few immediate conclusions for management and IT leaders:
- Syteca 7.24 targets operations: credential governance, reliability and reduced friction in administration are central, while the core architecture remains unchanged.
- Service accounts are central: Windows discovery with dependency transparency closes one of the most common blind spots in PAM programmes.
- Linux gains parity: PACM brings PAM into the native terminal workflow, including SELinux support and unchanged governance.
- Approach the upgrade methodically: test the end-to-end chain in staging, and define heartbeat escalation processes and ACB token policies before rollout.
Frequently asked questions about Syteca 7.24
What is new in Syteca 7.24?
Syteca 7.24 delivers five priorities. Discovery now also finds and onboards Windows service accounts, including dependency transparency. The native PAM Connection Manager brings privileged sessions into the Linux terminal and is complemented by a unified Linux x64 agent with SELinux support. Heartbeat verifies the status of vault passwords. In addition, the Application Credentials Broker API is significantly expanded and the password manager interface has been revised. The focus lies on operational reliability and credential governance.
Is the update worthwhile for existing installations?
Yes, particularly for Windows-heavy environments with many service accounts, for Linux and DevOps teams and for organisations with automation initiatives via the ACB API. For monitoring-only setups without vault usage, the update can be bundled into a regular maintenance window. Before production rollout, we recommend staging tests of the end-to-end workflows.
What is Heartbeat in Syteca?
Heartbeat is a new feature in Syteca 7.24. It checks, on schedule or on demand, whether passwords stored in the vault still work on the target system. This detects password drift caused by changes made outside Syteca. For each password, it reports the status Valid, Invalid or Failed. Syteca logs every check for audit purposes. When passwords are invalid, automatic checks pause until an administrator decides.
What was Ekran System and how does it relate to the rebranding?
Ekran System is the former name of the platform now called Syteca. The platform continues core functions such as session recording, user activity monitoring and PAM under the new branding. For existing customers, the functional line remains intact and grows step by step, most recently with the operational capabilities in release 7.24.
What is Syteca primarily used for?
Syteca covers the entire lifecycle of privileged access. The spectrum ranges from secure, also agentless connections and secret management in the vault through approval processes to forensic session analysis. The platform therefore supports Privileged Access Management, insider threat management and user activity monitoring.