Securing your account with two‑factor authentication (2FA)

Two‑factor authentication (2FA) adds an extra layer of protection to your Kaseya SIEM account by requiring two forms of verification when you sign in:

  • Something you know: your email address and password

  • Something you have: a time‑based, one‑time code generated by an authenticator app

Even if your password is compromised, 2FA helps prevent unauthorized access to your account. Kaseya strongly recommends enabling 2FA for all Kaseya SIEM users.

How account security setup can vary

Account security requirements can vary depending on how you start using Kaseya SIEM. Some organizations arrive with users and authentication already configured through Kaseya MDR, SaaS Alerts, or Unified Login with KaseyaOne. Others may be setting up access for the first time.

This article explains how authentication and two‑factor authentication work in Kaseya SIEM so you know where settings are managed and when action may be required during initial access or account setup.

2FA behavior in Kaseya SIEM

In Kaseya SIEM, 2FA is configured per user account from within the product interface.

Key points:

  • Users manage their own 2FA settings.

  • Depending on your authentication model, multi‑factor enforcement may be centralized through KaseyaOne rather than managed individually within Kaseya SIEM.

  • 2FA uses one‑time passwords (OTP) generated by an authenticator app.

  • 2FA settings are available under Settings > Account.

The setup steps are the same for all users. Where 2FA is enforced depends on how your organization authenticates users.

Authentication model

Kaseya SIEM supports two sign‑in models. Multi‑factor authentication enforcement depends on which model your organization uses.

Direct sign‑in to Kaseya SIEM

  • Users sign in using Kaseya SIEM credentials.

  • 2FA is enforced by Kaseya SIEM.

  • Users enable 2FA from Settings > Account.

Unified Login with KaseyaOne

If your organization uses Unified Login with KaseyaOne, authentication and multi‑factor authentication (MFA) are enforced through KaseyaOne, not directly within Kaseya SIEM.

When Unified Login is enabled:

  • Users sign in through KaseyaOne.

  • Authentication (including MFA) occurs during the KaseyaOne sign‑in flow.

  • The 2FA setting in Kaseya SIEM may still be visible, but it is not the primary enforcement point. Changes to the 2FA setting in Kaseya SIEM do not affect authentication behavior when Unified Login with KaseyaOne is enabled.

For details, see Unified Login with KaseyaOne.

Enabling two‑factor authentication

If your organization uses direct sign‑in to Kaseya SIEM, follow these steps:

  1. From the side navigation menu, go to Settings > Account.

  2. Locate the Two‑Factor Authentication section.

  3. Click Enable in the Two‑Factor Authentication section

  4. You may be prompted to log out and log in again.

Setting up your authenticator app

Kaseya SIEM supports standard OTP authenticator apps, including:

  • Authy (iOS or Android)

  • Google Authenticator (iOS or Android)

To complete setup:

  1. Open your authenticator app.

  2. Scan the QR code displayed in Kaseya SIEM.

  3. Enter the generated one‑time code when prompted.

  4. Click Finish.

A confirmation message appears in the upper‑right corner to indicate that setup was successful.

Disabling two‑factor authentication

While not recommended, you can disable 2FA if required:

  1. Go to Settings > Account.

  2. Locate the Two‑Factor Authentication section.

  3. Select Disable in the Two-Factor Authentication section

Disabling 2FA significantly reduces account security. Consider re‑enabling it as soon as possible.

Key takeaways

  • 2FA is enabled per user account in Kaseya SIEM

  • Users must enable 2FA themselves when using direct sign‑in

  • Enforcement depends on the authentication model in use:

    • Direct sign‑in: Kaseya SIEM enforces 2FA

    • Unified Login: KaseyaOne enforces MFA

Related articles

  • Unified Login with KaseyaOne: Understand how authentication and multi‑factor authentication are enforced when your organization uses Unified Login, and how this affects sign‑in behavior in Kaseya SIEM

  • Getting started with Kaseya SIEM: Confirm initial access, complete early security readiness steps, and verify that the platform is ready for use before moving into investigation workflows

  • Administration and configuration: Learn how roles, permissions, and organizational access boundaries affect what users can see and do after signing in