MyCena supports the full range of authentication protocols used in enterprise and operational environments: HTTP/HTTPS web applications, RDP (Remote Desktop), SSH, VPN gateways, legacy terminal systems, SaaS applications, and client-server applications. Both Windows and macOS clients are supported.
For systems outside the standard protocol set — legacy applications with custom authentication, on-premise systems with proprietary login mechanisms — the MyCena team conducts a pre-deployment compatibility assessment. The two-week deployment timeline assumes standard enterprise systems. Legacy-heavy environments may require additional time for edge-case systems.
For a specific compatibility assessment against your environment, contact us for a pre-deployment technical review — this is included in the proof of value process at no cost.
MyCena holds granted patents in the United States and Europe covering the core credential control mechanism: central generation, encrypted distribution, invisible injection at the point of authentication, and zero user knowledge of credential content.
The patent matters for two practical reasons. First, it confirms technical specificity — this is an examined, granted mechanism, not a policy claim or a marketing assertion. The credential physically cannot reach the user because the architecture prevents it, and that mechanism has been reviewed and validated. Second, it means no other vendor can replicate this architecture without licensing the patent. The consistency of the technical standard across MyCena deployments is architecturally enforced, not organisationally dependent.
The same architecture applies to AI agents and automated processes. Rather than a developer creating an API key or service credential and storing it in a config file, MyCena generates the credential centrally and injects it when the agent authenticates. The agent accesses the system. The credential is never in the config file, never accessible to the developer who built the agent, and is revoked when the agent is decommissioned.
Non-human identities now outnumber human users 82:1 in enterprise environments. 97% carry excessive privileges. 71% are never rotated. The governance gap for AI agents is structurally identical to the human credential gap — credentials created by individuals, stored outside organisational control, and left active after the agent is retired. MyCena closes both gaps on a single platform.
Because the organisation generated every credential through MyCena, the organisation holds a complete record of every credential issued, to every user, for every system. When someone leaves, an authorised admin issues a single revocation command. MyCena revokes every credential for that user across every system simultaneously — within seconds.
This is not a checklist. It is not a process that depends on IT knowing which systems the person accessed. The access map is maintained automatically as credentials are issued. Nothing is missed because nothing was ever outside MyCena's visibility.
The revocation event is logged automatically with a timestamp and the identity of the authorising user. That log is immediately available for regulatory submissions, client audits, and insurance evidence. The entire process — from departure confirmed to full revocation with timestamped proof — takes under ten seconds.
The employee authenticates once to the MyCena platform — typically with biometric or hardware token, the same way they unlock their device. From that point, every system they access through MyCena appears as a clickable connection. They click. MyCena injects the credential. They are in.
The credential is distributed to the device in encrypted form. At the moment of connection, MyCena decrypts it locally and injects it into the authentication protocol for that system. The browser or application never displays it. It is never written to the clipboard. It is never stored in the user's profile. The injection happens below the application layer — invisible to the user, invisible to any screen recording or shoulder-surfing attempt.
For different protocol types — RDP, SSH, HTTPS applications, legacy systems — MyCena uses the appropriate injection method. The employee experience is identical regardless of the underlying protocol: one click, connected.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
Ce site utilise Google Analytics pour collecter des informations anonymes telles que le nombre de visiteurs du site et les pages les plus populaires.
Garder ce cookie activé nous aide à améliorer notre site Web.