Showing all 166 capabilities
| Capability | Module | Deployment | Status |
|---|---|---|---|
| Single management console for every moduleEvery module is administered from one interface; there is no separate console per product | Platform | On-PremiseSaaS | Supported |
| Logging across all modulesLogin, audit, RADIUS, proxy, OWA, OS logon, ADFS, ActiveSync and custom API logs | Platform | On-PremiseSaaS | Supported |
| Syslog export to SIEMPlatform logs are forwarded to a SIEM or log collector over syslog | Platform | On-PremiseSaaS | Supported |
| Detailed audit trailObject, end-user IP, response status and browser are recorded for every action | Platform | On-PremiseSaaS | Supported |
| Mail template customisationNotification and enrolment emails are rewritten to match the organisation's own wording and branding | Platform | On-PremiseSaaS | Supported |
| Custom SMS providerThe organisation's own SMS gateway is used instead of the built-in delivery path | Platform | On-PremiseSaaS | Supported |
| User import from external sourcesActive Directory, Entra ID, OpenLDAP, Google Workspace and third-party identity providers | Platform | On-PremiseSaaS | Supported |
| Custom attribute supportMail, phone and pattern mapping per source, with conditions on user status | Platform | On-PremiseSaaS | Supported |
| Local user directoryUsers are created and maintained inside the platform with no external directory required | Platform | On-PremiseSaaS | Supported |
| Role-based administrationFull control and read-only administrator profiles, assignable per administrator | Platform | On-PremiseSaaS | Supported |
| Multi-tenant operation for MSSPsMany tenants managed from one centralised portal, each isolated so that data and policy stay segmented between them | Platform | SaaS | Supported |
| Tenant lifecycle from the partner consoleAn MSSP partner creates, edits and removes tenants itself, and Go to Portal opens a tenant's own portal in a new tab | Platform | SaaS | Supported |
| Licence assignment from shared poolsAn MSSP partner draws a tenant's licences from a shared pool, billed monthly on what is actually used | Platform | SaaS | Supported |
| Tenant-controlled remote supportA tenant switches remote support off, and while it is off no one above that tenant can administer it — including Mirket | Platform | SaaS | Supported |
| Administrator scope — Master or Account AdminA Master Admin sees the other tenants on the account as well; an Account Admin sees only their own | Platform | SaaS | Supported |
| Administrator profile — Full Control or Read OnlyA read-only administrator can view the interface without being able to change anything | Platform | SaaS | Supported |
| High availabilityA second node keeps the service available if the primary fails | Platform | On-Premise | Supported |
| Active-passive node configurationFailover happens automatically, and can also be initiated by an operator | Platform | On-Premise | Supported |
| Data synchronisation between nodesConfiguration changes replicate to the standby node immediately | Platform | On-Premise | Supported |
| Mirket Push — approve / deny notificationA sign-in request is pushed to the registered phone and approved or denied with one tap | MFA | On-PremiseSaaS | Supported |
| Mirket OTP — one-time code in the mobile appA single-use code generated by the platform and delivered to the registered mobile app; requires connectivity at the moment of sign-in | MFA | On-PremiseSaaS | Supported |
| Mirket Token — 30-second rotating tokenA code generated on the phone itself and changing every 30 seconds, verified without the app contacting the platform — which is what makes offline authentication possible | MFA | On-PremiseSaaS | Supported |
| TOTP — third-party authenticator appsUsers may enrol Google Authenticator, Microsoft Authenticator or any RFC 6238 application | MFA | On-PremiseSaaS | Supported |
| SMS one-time passwordA single-use code is sent by text message for users without the mobile app | MFA | On-PremiseSaaS | Supported |
| Offline authentication at the logon screenMirket Token or TOTP is verified on the endpoint itself, so logon works with no connectivity; one online sign-in on that machine is all that is required beforehand | MFA | On-PremiseSaaS | Supported |
| Recovery codes, regenerated dailyFallback codes are reissued every day, so a lost or copied list stops working quickly | MFA | On-PremiseSaaS | Supported |
| Passwordless authenticationUsers authenticate without entering a password, using supported passwordless methods: FIDO2 and WebAuthn in the browser, or a Mirket method at the Windows and Linux logon | MFA | On-PremiseSaaS | Supported |
| Passwordless authentication over RADIUSThe user approves a push on the registered phone, or enters a one-time code from the app in place of a password; the directory password is not requested | MFA | On-PremiseSaaS | Supported |
| Passwordless credential protection on WindowsThe Windows credential is never stored in plaintext: AES-256-GCM under a per-machine key, the key itself sealed by Windows DPAPI at LOCAL_MACHINE scope, so a copied registry, disk or backup cannot be decrypted elsewhere | MFA | On-PremiseSaaS | Supported |
| Biometric unlock in the mobile appFace or fingerprint must unlock the app before an approval can be given | MFA | On-PremiseSaaS | Supported |
| Mobile app backup QRA backup QR code moves every enrolled account to a replacement phone without re-enrolment | MFA | On-PremiseSaaS | Supported |
| TOTP enrolment for directory-sourced usersUsers synchronised from Active Directory or LDAP enrol their own authenticator | MFA | On-PremiseSaaS | Supported |
| Built-in RADIUS serverEmbedded in the platform; no third-party RADIUS infrastructure to license or operate | MFA | On-PremiseSaaS | Supported |
| RADIUS vendor-specific attribute (VSA) supportGroup and role information is returned to the firewall or NAS to drive its own policy | MFA | On-PremiseSaaS | Supported |
| RADIUS enforcement — VPN, firewall, network devicesAny device that speaks RADIUS is protected with no agent and no change to the device | MFA | On-PremiseSaaS | Supported |
| RADIUS authentication protocols — PAP and PAP over EAP-TTLSThe gateway decides which is used; FortiGate IPsec with IKEv2 requires EAP-TTLS, while SSL VPN typically uses PAP | MFA | On-PremiseSaaS | Supported |
| Reverse MFA — second factor before the passwordThe order is inverted: the second factor is completed first and the password taken second; listed in both platform specifications under authentication methods | MFA | On-PremiseSaaS | Supported |
| LDAP and LDAPS bind enforcementApplications that authenticate over LDAP gain a second factor without being modified | MFA | On-PremiseSaaS | Supported |
| Windows logon — local, remote, unlock and CredUIScope is selectable: none, local only, remote only, or both | MFA | On-PremiseSaaS | Supported |
| Linux and Unix logon — SSH and consoleAgents for Ubuntu, RedHat, RedHat-CentrifyDC, Debian and SUSE | MFA | On-PremiseSaaS | Supported |
| macOS logonAgent for macOS login and unlock, alongside the Windows and Linux agents | MFA | On-PremiseSaaS | Supported |
| Privilege elevation (UAC) challengeAn elevation prompt requires a second factor before administrative rights are granted | MFA | On-PremiseSaaS | Supported |
| OS logon agent — serviceless operationNo resident service runs on the endpoint, reducing footprint and attack surface | MFA | On-PremiseSaaS | Supported |
| OS logon agent — uninstall protectionA removal code is required to uninstall the agent, so a local administrator cannot simply strip it | MFA | On-PremiseSaaS | Supported |
| Silent installationThe agent deploys unattended through GPO, SCCM or any software distribution tool | MFA | On-PremiseSaaS | Supported |
| Exchange OWA and ECP — without ADFSOutlook Web Access and the Exchange admin centre are protected directly, with no ADFS in the path | MFA | On-PremiseSaaS | Supported |
| Exchange ActiveSync device approvalA newly synchronising mobile device must be approved before it can reach the mailbox | MFA | On-PremiseSaaS | Supported |
| ADFS — MFA adapterMirket registers as a second-factor adapter inside an existing ADFS deployment | MFA | On-PremiseSaaS | Supported |
| Custom API — any application over RESTA single authentication endpoint lets in-house applications call MFA directly; Postman collection published | MFA | On-PremiseSaaS | Supported |
| Microsoft Entra ID External Authentication Method (OIDC)Makes Mirket the second factor inside the Entra ID sign-in flow, with no on-premise footprint | MFA | SaaS | Supported |
| Rule engine — user and group targetingPolicies are matched top-down, so the first rule that matches decides the outcome | MFA | On-PremiseSaaS | Supported |
| Schedule conditionsA policy applies permanently, on set days and hours, or only within a date range | MFA | On-PremiseSaaS | Supported |
| Source IP conditions in authentication rulesA rule can require or waive the second factor depending on where the request originates | MFA | On-PremiseSaaS | Supported |
| Device trust conditions in authentication rulesA rule can distinguish a known, enrolled device from an unrecognised one and respond differently | MFA | On-PremiseSaaS | Supported |
| Bypass controlsGlobal, unknown-user, IP-list and named-user bypasses for migration and break-glass cases | MFA | On-PremiseSaaS | Supported |
| MFA fatigue and bombing attack protectionRepeated push notifications are rate-limited so a user cannot be worn down into approving one | MFA | On-PremiseSaaS | Supported |
| Per-target method selectionSSH, RDP and console logon each carry their own enabled methods | MFA | On-PremiseSaaS | Supported |
| SAML 2.0 identity providerFederated authentication for any application that speaks SAML 2.0, in both IdP-initiated and SP-initiated flows | SSO | On-PremiseSaaS | Supported |
| OAuth 2.0 authorisationThe authorisation framework OpenID Connect builds on, for applications and APIs that need delegated authorisation rather than a sign-in assertion | SSO | On-PremiseSaaS | Supported |
| OpenID Connect (OIDC)Federated authentication for applications expecting an OpenID Connect identity token | SSO | On-PremiseSaaS | Supported |
| IdP-initiated sign-onThe user starts from the Mirket portal and is signed straight into the application | SSO | On-PremiseSaaS | Supported |
| SP-initiated sign-onThe user starts at the application and is redirected to Mirket to authenticate | SSO | On-PremiseSaaS | Supported |
| QR-code sign-in at the Mirket portalApplies where the sign-in happens in the browser on the SAML path; not an operating-system logon method | SSO | On-PremiseSaaS | Supported |
| Single logoutSigning out propagates to federated applications instead of leaving sessions open | SSO | On-PremiseSaaS | Supported |
| Signed SAML responseThe assertion is signed so the service provider can verify Mirket issued it | SSO | On-PremiseSaaS | Supported |
| IdP metadata export and certificate downloadMetadata XML and the signing certificate are exported for import at the service provider | SSO | On-PremiseSaaS | Supported |
| Attribute mapping to the service providerDirectory attributes are mapped to the claim names each application expects | SSO | On-PremiseSaaS | Supported |
| Role and group assignment passed to the service providerGroup membership travels in the assertion, so application authorisation follows the directory | SSO | On-PremiseSaaS | Supported |
| Directory custom attributes available for SAML mappingNon-standard directory attributes can be selected and carried into the assertion | SSO | On-PremiseSaaS | Supported |
| Per-application access policy and RBACEach application carries its own policy and its own assigned users and groups | SSO | On-PremiseSaaS | Supported |
| Application logo and branding per applicationEach entry in the user portal carries its own name and logo | SSO | On-PremiseSaaS | Supported |
| Self-service password resetA user resets a forgotten directory password after passing MFA, without calling the help desk | Self-Service | On-PremiseSaaS | Supported |
| Self-service account unlockA locked-out account is unlocked by the user once identity is verified | Self-Service | On-PremiseSaaS | Supported |
| Forgotten-password flow with personal security questionsPersonal questions can be required as an additional step in the recovery path | Self-Service | On-PremiseSaaS | Supported |
| Self-service MFA method enrolmentUsers register, replace and remove their own authentication methods and devices | Self-Service | On-PremiseSaaS | Supported |
| Forbidden password listPredictable strings such as the company name or the current year are rejected outright | Self-Service | On-PremiseSaaS | Supported |
| Password expiry remindersUsers are warned a configurable number of days ahead, then reminded daily | Self-Service | On-PremiseSaaS | Supported |
| Password policy enforcementEnforces the configured password requirements, including length and character-type rules, alongside the forbidden-password controls below | Self-Service | On-PremiseSaaS | Supported |
| My Devices — user self-approval of ActiveSync devicesA user approves their own new mobile device instead of raising a ticket | Self-Service | On-PremiseSaaS | Supported |
| Operates on delegated directory rightsDomain Admin is not required; only the permissions needed for password reset and account unlock are delegated to the OUs you choose | Self-Service | On-PremiseSaaS | Supported |
| Configurable methods and default method for the user portalThe administrator chooses which methods appear and which one is offered first | Self-Service | On-PremiseSaaS | Supported |
| User expiration managementAn account is given an expiry date and disabled automatically when it passes | Self-Service | On-PremiseSaaS | Supported |
| Asset management — servers and web applicationsTarget systems are registered as assets, reached over RDP, SSH or the browser | PAM | On-Premise | Supported |
| Asset groups with inherited account mappingA mapping applied to a group reaches every asset in that group | PAM | On-Premise | Supported |
| Instant Agent — an endpoint registered as an assetAn agent installed on a workstation or a server registers that machine as an asset, so a console that is not reached over RDP or SSH is still worked on under PAM authorisation and recorded like any other session | PAM | On-Premise | Supported |
| Attended sessions on an Instant Agent endpointAn operator at the machine and a remote specialist work in the same session together, which suits operational technology sites where the console cannot simply be handed over | PAM | On-Premise | Supported |
| Credential vault for privileged accountsPrivileged passwords are held encrypted in the platform rather than by administrators | PAM | On-Premise | Supported |
| Automatic password rotation on a scheduleInterval in days and time of day, set per account | PAM | On-Premise | Supported |
| Credential injection into interactive sessionsThe session opens already authenticated and the user never sees the privileged password | PAM | On-Premise | Supported |
| Just-in-Time (JIT) privileged accessAccess is granted for the window it is needed and withdrawn afterwards, so standing privilege disappears | PAM | On-Premise | Supported |
| Access Matrix — who reaches what, and howOne view of the effective access model across every user and every asset | PAM | On-Premise | Supported |
| Show-password — authorisation, MFA and auditWhere a password must be revealed, who may reveal it is set per user, group or external source; the reveal is additionally confirmed by MFA on the registered device, and every reveal is logged as an auditable event | PAM | On-Premise | Supported |
| Mirket Native ClientAgent presenting every asset the user is entitled to reach, on Windows and macOS. Included with PAM — no ZTNA licence required; a ZTNA licence applies only when the relay is used | PAM | On-Premise | Supported |
| Browser-based isolated access (HTML5)The session runs in the browser with nothing installed and no credential reaching the endpoint | PAM | On-Premise | Supported |
| Remote browser isolation (RBI) for web applicationsWeb applications open in an isolated remote browser, so nothing executes on the user's machine | PAM | On-Premise | Supported |
| Native RDP accessStarted from a single-use launcher Mirket generates and opened in Microsoft Remote Desktop, or run inside the Mirket agent, while policy and recording stay enforced | PAM | On-Premise | Supported |
| Native SSH accessStarted from a launcher Mirket generates, in the SSH client already installed on the administrator's machine — PuTTY on Windows, Terminal on macOS — or with the SSH tooling built into the Mirket agent | PAM | On-Premise | Supported |
| Single-use session launcherA generated connection file has to be run within a minute and works exactly once, so it cannot be kept, forwarded or reused later | PAM | On-Premise | Supported |
| SFTP with authorisation and auditFile transfer is authorised and audited like any other privileged session | PAM | On-Premise | Supported |
| Privileged session video recordingEverything that happens in a session is recorded as replayable video | PAM | On-Premise | Supported |
| Session command transcriptCommands issued in the session are captured as searchable text alongside the video | PAM | On-Premise | Supported |
| Smart playbackIdle stretches are removed and playback speed is adjustable, so a long session is reviewed quickly | PAM | On-Premise | Supported |
| Command search, filtering and CSV exportA reviewer searches recorded commands, filters them and exports the result for an audit file | PAM | On-Premise | Supported |
| Command policy — blacklist or whitelist modeCommands are matched against patterns, either blocking what is listed or allowing only what is listed | PAM | On-Premise | Supported |
| Command policy action — audit, block, or kill sessionA matched command is flagged in the transcript, silently removed, or used to end the session outright | PAM | On-Premise | Supported |
| Command policy enforced in native RDP sessionsCommand control continues to apply in a native Microsoft Remote Desktop session, not only in the browser | PAM | On-Premise | Supported |
| Clipboard control — to user and to asset, separatelyCopying into the session and copying out of it are permitted or denied independently | PAM | On-Premise | Supported |
| File upload and download control, separatelyUpload and download are separate permissions, so one is allowed without the other | PAM | On-Premise | Supported |
| Clipboard and file-transfer policy in native RDPThese restrictions hold in native RDP sessions, not only in browser sessions | PAM | On-Premise | Supported |
| Session shadowing with selectable authority levelA supervisor joins a live session to observe or intervene, at a chosen level of authority | PAM | On-Premise | Supported |
| Live session terminationAn administrator ends a session in progress immediately | PAM | On-Premise | Supported |
| Inline re-authentication for the login accountRe-authentication can be required at the moment the privileged account is actually used | PAM | On-Premise | Supported |
| Manual loginWhere policy allows, an authorised user supplies their own credentials instead of drawing one from the vault | PAM | On-Premise | Supported |
| Discovery — import domain servers as assetsReports ping, WinRM reachability, operating system and OU per host before import | PAM | On-Premise | Supported |
| Discovery — import local accountsLocal accounts found on discovered hosts are imported into the vault rather than entered by hand | PAM | On-Premise | Supported |
| Discovery scheduling including cron expressionsDiscovery runs from every few minutes to a custom cron schedule, so new hosts do not go unmanaged | PAM | On-Premise | Supported |
| Detailed reporting — user based and asset basedReports run from either direction: what one user reached, or who reached one asset | PAM | On-Premise | Supported |
| Scheduled reports with email recipientsA report is generated on a schedule and emailed to named recipients with nobody logging in | PAM | On-Premise | Supported |
| Detailed session and access auditEvery session and access decision is recorded with actor, target, time and outcome | PAM | On-Premise | Supported |
| Secrets Vault — application secrets and API keysEncrypted storage, lifecycle management and secure API access for application secrets | PAM | On-Premise | Supported |
| Glass Break — recovery of accounts, assets and mappingsA recovery file rebuilds the PAM configuration if it is lost or corrupted; the recovery password is held offline | PAM | On-Premise | Supported |
| SSH key managementCentral custody and rotation of SSH key pairs used for privileged access | PAM | On-Premise | Supported |
| Credential ProviderAn API the customer builds a small agent against: the agent collects the current credential, the replacement and the context it needs from the platform, then applies the change on the target system — so rotation reaches systems that need their own handling | PAM | On-Premise | Supported |
| Zero inbound ports at the customer edgeThe connector dials outbound; nothing listens for inbound connections, so there is nothing to scan | ZTNA | On-Premise | Supported |
| Noise_IK end-to-end encryptionThe relay forwards ciphertext and cannot decrypt session traffic | ZTNA | On-Premise | Supported |
| Loopback listener — no virtual interfaceNo utun/tun/tap device is created and no entry is added to the routing table | ZTNA | On-Premise | Supported |
| Layer 7 per-application authorisationOnly explicitly authorised targets are reachable; the internal network is not exposed | ZTNA | On-Premise | Supported |
| PAM authorisation evaluated on every sessionEach connection is authorised again, rather than trusting a tunnel established once | ZTNA | On-Premise | Supported |
| Video recording and command transcript on ZTNA accessRemote access is recorded and transcribed exactly as an internal privileged session is | ZTNA | On-Premise | Supported |
| Stateless relay and connector architectureThe relay forwards end-to-end encrypted traffic between the user's agent and a connector inside the customer environment; it holds no session keys and cannot decrypt session content | ZTNA | On-Premise | Supported |
| Desktop agent for WindowsCarries native RDP, native SSH and browser-isolated access in one agent, with the RDP and SSH tooling built in | ZTNA | On-Premise | Supported |
| Desktop agent for macOS — Apple notarisedNotarised, so enterprise deployment raises no Gatekeeper warning | ZTNA | On-Premise | Supported |
| Native RDP over ZTNAA remote user works in a full RDP session inside the agent, with no VPN and no published RDP port | ZTNA | On-Premise | Supported |
| Native SSH and SFTP over ZTNAA remote user works in the agent's built-in SSH tooling and transfers files over the same path | ZTNA | On-Premise | Supported |
| Session contained within the agentThe session runs inside the agent rather than in a separate desktop window, and screen capture of that area is blacked out | ZTNA | On-Premise | Supported |
| Web access (RBI) over ZTNAInternal web applications are reached through the isolated remote browser without being published | ZTNA | On-Premise | Supported |
| Agent sign-in via SSO (OIDC)The agent authenticates the user through the organisation's own single sign-on | ZTNA | On-Premise | Supported |
| Automatic agent updates with central version managementAgent versions are managed centrally and updated without touching the endpoint | ZTNA | On-Premise | Supported |
| Enterprise branding of the agentThe agent carries the organisation's own name and visual identity | ZTNA | On-Premise | Supported |
| Per-user agent usage informationAdministrators see which users are using the agent, and how much | ZTNA | On-Premise | Supported |
| Dedicated agent page for non-administrator usersEnd users download and manage the agent from their own page, separate from the admin console | ZTNA | On-Premise | Supported |
| Clipboard permission management in agent sessionsClipboard rules apply to sessions opened through the agent | ZTNA | On-Premise | Supported |
| User revocation with automatic profile wipeRevoking a user removes their profile from the endpoint automatically, with no visit to the machine | ZTNA | On-Premise | Supported |
| HA node information surfaced to agent sessionsEach agent session records which high-availability node served it, which shortens troubleshooting | ZTNA | On-Premise | Supported |
| MFA enforcement for human LDAP authenticationA person authenticating through an application over LDAP or LDAPS can be challenged with MFA, with no change to the application's code | NHI Proxy | On-Premise | Supported |
| MFA enforcement on LDAPS bindThe same enforcement applies to binds already carried over TLS | NHI Proxy | On-Premise | Supported |
| Source IP restriction per service accountThe credential is accepted only from the source addresses authorised for that application | NHI Proxy | On-Premise | Supported |
| DN scopingA service account is confined to one branch of the directory; out-of-scope searches are rejected, which prevents directory-wide enumeration | NHI Proxy | On-Premise | Supported |
| LDAP to LDAPS protocol upliftThe proxy accepts legacy LDAP from the application and establishes a TLS-protected connection to the domain controller, protecting the directory-facing leg without any application change | NHI Proxy | On-Premise | Supported |
| Service accounts exempt from interactive MFANon-human service accounts bypass the interactive challenge and are protected instead by virtual credentials, source restriction and rotation — so directory queries generate no push notifications | NHI Proxy | On-Premise | Supported |
| Central bind logging with first and second factor resultsEvery bind is logged in one place, showing the directory result and the second-factor result separately | NHI Proxy | On-Premise | Supported |
| Policy decision taken centrally at the PortalThe proxy agent enforces the decision; it does not make it, so policy stays in one place | NHI Proxy | On-Premise | Supported |
| Blocked bind raises a high-confidence security eventA service account is normally used from one address, so a rejected bind is a strong signal rather than noise | NHI Proxy | On-Premise | Supported |
| Active-active proxy redundancyMultiple proxy instances serve traffic simultaneously, so a failure does not stop authentication | NHI Proxy | On-Premise | Supported |
| Virtual credentialsThe credential the application holds has no counterpart in Active Directory, so a captured password cannot be used for Kerberos, SMB or password spraying | NHI Proxy | On-Premise | Supported |
| Service account password rotationBecause the real secret is held in one place, it can be rotated without touching any application configuration | NHI Proxy | On-Premise | Supported |
| Per-application credential attributionEach application binds with its own credential, so a leaked secret identifies which system it came from | NHI Proxy | On-Premise | Supported |
| Individual credential revocationOne application's credential is revoked on its own, without disturbing any of the others | NHI Proxy | On-Premise | Supported |
| Behaviour analyticsA baseline of normal behaviour per account exposes sign-ins and actions that do not fit the pattern | ITDR | SaaS | Supported |
| Deception — identity-based honeypots and decoy credentialsDecoy accounts and credentials are planted, so an attacker touching them reveals lateral movement | ITDR | SaaS | Supported |
| Cyber threat intelligence integrationLeaked-credential feeds, malicious infrastructure and actor intelligence are correlated with authentication activity, so a credential known to be compromised is refused at the point of use | ITDR | SaaS | Supported |
| MITRE ATT&CK technique mappingEach detection is mapped to the technique it represents, for reporting and coverage analysis | ITDR | SaaS | Supported |
| Request origin inspection — TOR, VPN, proxy, cloudThe origin of each request is identified and scored, so anonymised access stands out | ITDR | SaaS | Supported |
| Anomaly and account takeover (ATO) detectionCredential harvesting, privilege escalation and account takeover are detected across the attack chain | ITDR | SaaS | Supported |
| Risk scoring — threat score and certainty scoreTwo separate scores per detection and per account: how serious it is, and how sure the platform is | ITDR | SaaS | Supported |
| Automated responseAccount isolation, forced password reset or an adaptive MFA challenge, applied without an analyst | ITDR | SaaS | Supported |
No capabilities match that filter.
