01Access & Authentication
02Privileged & Zero Trust
03Threat Detection
Solutions
Authentication ends at the login. Identity security doesn't.
01Secure Access
02Privileged Access
03Zero Trust & Remote
04Non-Human Identity
The opportunity
Your customers buy identity from one vendor and privileged access from another. Sell them one platform — on-premise or SaaS — with deal protection.
Apply to partner01Partner with Mirket
Resources
Documentation, integration guides, the feature matrix, a glossary and release notes — the material behind the Mirket platform, mostly public.
Identity Security Platform
Mirket is an identity security platform for the people who sign in, the administrators who work behind the sign-in, and the service accounts that authenticate without a person — seven modules on one platform, running on your own infrastructure or as a service.
The threat
A correct username and a correct password are indistinguishable from a legitimate user to every control that watches the network. That is why the attacks that matter most run on identity rather than on vulnerabilities — a credential read out of LDAP traffic, a push approved out of fatigue, a privileged session opened with a stolen password. None of them breaks anything. Each of them signs in.
Mirket Identity Security Platform
Techniques from the identity attack chain, by MITRE ATT&CK® tactic. Every one of them ends at the platform.
Why Mirket
Authentication answers one question: whether a sign-in is allowed. Identity security keeps asking after the answer is yes — what the account can reach, what it does once inside, and whether the credential behind it has been exposed. Mirket is built on three decisions that follow from that.
Workforce + Privileged + Non‑Human Identity
The employee at a browser, the administrator inside a privileged session and the service account that authenticates without a person present are secured from the same console, over the same directory sources, into the same audit trail.
On-Premise + SaaS
The platform runs on your own infrastructure, as a service, or both — decided module by module. Privileged sessions, their recordings and the credentials behind them can stay entirely inside your environment while detection intelligence arrives as a service.
Authentication + Access + Detection
Authentication decides whether a sign-in is allowed. Access decides what an identity may reach and do inside a session. Detection watches what happens after both have said yes. Mirket carries all three, which is why the platform does not stop at the login.
The platform
Each module is a product in its own right. All seven are administered from the same console, over the same users, into the same audit trail — which is what makes Mirket a platform rather than seven products.
A second factor on every path a login takes: the browser, the VPN, RDP and SSH, the operating system logon, privilege elevation and legacy applications.
One sign-in for the applications your people use, federated over SAML 2.0 and OpenID Connect.
Password reset, account unlock and device enrollment, completed by the user behind MFA, on delegated directory rights.
Sessions authorized per target and opened with an injected credential; recorded as video and searchable text, with command policy enforced inside the session.
Remote privileged access to named systems with nothing published at your edge and no tunnel onto the network.
The application holds a virtual credential with no counterpart in the directory. The real password stays behind the proxy and rotates without the application being touched.
Detection across the attack chain — credential harvesting, privilege escalation and account takeover — with threat and certainty scoring and automated response.
Mirket Platform
Deployment
Where an identity lives is a decision an organization makes for its own reasons — regulation, data residency, architecture, risk. Mirket is built to follow that decision rather than to reverse it.
Multi-Factor Authentication, Single Sign-On, Secure Self-Service, Privileged Access Management, Zero Trust Network Access and the NHI LDAP Proxy run entirely inside your environment.
Multi-Factor Authentication, Single Sign-On, Secure Self-Service and Identity Threat Detection & Response run from Mirket’s cloud, with directory credential verification kept inside your network through the Mirket Gateway.
Privileged sessions, their recordings and the credentials behind them remain in your environment. Detection intelligence — new attack patterns, threat feeds, behavioral models — is kept current from Mirket’s cloud.
Every capability is listed with its deployment model and support status. The documentation is public. Every release is dated. Feature matrix Documentation How the platform deploys
In production
Among them
Mirket Security has become a key part of how we manage privileged access across our organization. We use PAM and ZTNA company-wide to secure RDP, SSH and web-based access through a consistent control layer. Beyond day-to-day access security, Mirket has been particularly valuable during financial audits. The Access Matrix and reporting capabilities give us clear visibility into who has access to what and provide the evidence we need for audit and compliance processes.
Rolling out MFA across a healthcare environment of 40,000 users and multiple hospitals required a solution that could strengthen security without disrupting daily operations. Mirket Security made that transition remarkably smooth. From doctors and nurses to administrative teams, we were able to introduce stronger authentication across our organization with minimal friction.
What we value most about Mirket Security is having our identity security capabilities within a single, integrated platform. Rather than managing separate solutions for authentication, privileged access, secure remote access and identity threat detection, we can manage these security layers through one consistent approach. Having these capabilities work together has simplified operations while giving our IT team stronger control.
Industries
Legacy ERP and MES on LDAP, a flat network, and integrators who need a way in.
A technical demonstration on your infrastructure — the logon screen, a privileged session, a service account behind the proxy.
