Overview

Authentication and Security in Fixiam help organizations verify user identities, protect access to applications, and reduce the risk of unauthorized access.

Fixiam uses multiple layers of security to ensure that only the right users can access the right resources at the right time.

These layers work together to evaluate user credentials, verify identity, assess sign-in risk, and enforce additional security controls when necessary.

By combining password authentication, multi-factor authentication (MFA), adaptive risk evaluation, and application-specific security policies, organizations can strengthen access security without creating unnecessary friction for users.


How Authentication Works in Fixiam

When a user attempts to sign in, Fixiam evaluates several security controls before granting access.

Depending on your organization's configuration, users may be required to complete one or more authentication steps before access is granted.

Example

  1. A user enters their username and password.
  2. Fixiam verifies the credentials.
  3. An OTP challenge is presented.
  4. Fixiam evaluates the sign-in attempt for potential risks.
  5. Access is granted to the requested application.

Authentication Layers

Authentication in Fixiam is made up of several security layers that work together to protect access.

Password Authentication

Password authentication is the first layer of identity verification.

Organizations can define password requirements such as:

  • Password complexity
  • Password expiration
  • Account lockout rules
  • Session timeout settings

These controls help reduce the risk of unauthorized access through weak or compromised passwords.

Multi-Factor Authentication (MFA)

Multi-Factor Authentication (MFA) adds an additional layer of verification beyond passwords.

Fixiam supports the following MFA factors:

  • One-Time Password (OTP)
  • Fingerprint Authentication
  • Portrait Authentication

MFA helps ensure that access is granted only after users successfully complete additional identity verification steps.

Adaptive Risk Authentication

Adaptive Risk Authentication continuously evaluates sign-in activity and user behavior.

Instead of treating every sign-in attempt the same way, Fixiam can identify suspicious activity and automatically apply additional security controls.

Examples of risk signals include:

  • Sign-in from an unfamiliar device
  • Sign-in from an unusual location
  • Impossible travel scenarios
  • Concurrent sign-ins from multiple countries
  • Sign-ins outside normal working hours

When suspicious activity is detected, Fixiam can:

  • Require additional authentication
  • Escalate the sign-in for further verification
  • Block access entirely

Application Authentication Policies

Applications may require additional security controls beyond organization-wide authentication settings.

Administrators can define application-specific authentication requirements such as:

  • Additional MFA factors
  • Adaptive risk actions
  • Application-specific security policies

This allows organizations to apply stronger security controls to sensitive applications while maintaining a simpler experience for less critical applications.


Organization Authentication vs Application Authentication

Authentication settings can be configured at two levels within Fixiam.

Organization-Level Authentication

Organization-level settings apply across the entire organization.

Examples include:

  • Password policies
  • MFA requirements
  • Adaptive Risk settings
  • Trusted Device policies

These settings establish the baseline security requirements for all users.

Application-Level Authentication

Application-level settings apply only to a specific application.

Applications can inherit organization settings or define additional authentication requirements.

Example

Configuration LevelAuthentication Requirement
OrganizationOTP
ApplicationPortrait Authentication

Result:

Password
↓
OTP
↓
Portrait Authentication
↓
Application Access

Both requirements must be satisfied before access is granted.


Understanding Authentication Inheritance

Application authentication policies work together with organization-wide authentication policies.

When an application inherits organization settings, the application automatically follows the organization's configured security controls.

Example

Organization MFAApplication MFAResult
OTPNoneOTP
OTPOTPOTP presented once
OTPPortraitOTP followed by Portrait Authentication

This helps organizations maintain consistent security while supporting application-specific requirements.


Why Adaptive Security Matters

Traditional authentication relies primarily on passwords.

Modern security threats require additional protection.

Fixiam helps organizations reduce security risks by evaluating:

  • User identity
  • Device trust
  • Login location
  • User behavior
  • Risk indicators

This allows security controls to adapt dynamically based on the risk associated with each sign-in attempt.

Example

A user typically signs in from Lagos during business hours using a trusted device.

If the same user suddenly attempts to sign in from another country within a short period, Fixiam can identify the activity as suspicious and require additional verification before granting access.



What’s Next

To configure authentication and security controls in Fixiam, refer to the following guides:

  1. Password Authentication
  2. Multi-Factor Authentication (MFA)
  3. Adaptive Risk Authentication
  4. Security Best Practices

These guides provide detailed configuration instructions and recommendations for securing access across your organization.

Did this page help you?