<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monetization Web Docs | Tridens Technology – Security</title><link>/monetization-web-docs/categories/security/</link><description>Recent content in Security on Monetization Web Docs | Tridens Technology</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/monetization-web-docs/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Access Logs</title><link>/monetization-web-docs/security/access-logs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/monetization-web-docs/security/access-logs/</guid><description>
&lt;p>To access this section in &lt;strong>Monetization&lt;/strong>, from the &lt;i class="fa fa-bars" aria-hidden="true">&lt;/i> &lt;strong>Menu&lt;/strong>, select &lt;i class="fa fa-user" aria-hidden="true">&lt;/i> &lt;strong>User management&lt;/strong>, and click &lt;strong>Access logs&lt;/strong>. A paginated list of users&amp;rsquo; activities from a specific period is shown in a tabular format.&lt;/p>
&lt;p>&lt;strong>Access time&lt;/strong> denotes the date-time the information was accessed; &lt;strong>User&lt;/strong> indicates the individual that accessed the information. The &lt;strong>Details&lt;/strong> represent the API endpoint that was accessed.&lt;/p>
&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note:&lt;/h4>
At the moment, only the &lt;strong>Customers&lt;/strong> endpoints are being tracked.
&lt;/div>
&lt;div class="alert alert-info" role="alert">
&lt;h4 class="alert-heading">Information:&lt;/h4>
You can filter access logs by date-time, data type (user/customer), user ID, or/and customer ID.
&lt;/div></description></item><item><title>Docs: Authentication Settings</title><link>/monetization-web-docs/security/authentication-settings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/monetization-web-docs/security/authentication-settings/</guid><description>
&lt;p>Authentication is a critical part of securing your &lt;strong>Monetization&lt;/strong> environment.&lt;br>
The platform allows administrators to define how users log in, how long sessions remain active, and what security measures (such as Multi-Factor Authentication) are required to protect accounts.&lt;/p>
&lt;p>To configure authentication settings:&lt;/p>
&lt;ol>
&lt;li>Open the &lt;i class="fa fa-bars" aria-hidden="true">&lt;/i> &lt;strong>Menu&lt;/strong> (bottom left, click on your username).&lt;/li>
&lt;li>Select &lt;i class="fa fa-user" aria-hidden="true">&lt;/i> &lt;strong>Business Portal&lt;/strong>.&lt;/li>
&lt;li>Click &lt;strong>Security&lt;/strong>.&lt;/li>
&lt;/ol>
&lt;p>The &lt;strong>Authentication Settings&lt;/strong> page is displayed.&lt;/p>
&lt;p>&lt;img src="../security-authentication-authentication-settings-page.png" alt="Authentication Settings Page">&lt;/p>
&lt;hr>
&lt;h3 id="available-settings">Available Settings&lt;/h3>
&lt;h4 id="session-timeout">Session Timeout&lt;/h4>
&lt;p>The &lt;strong>session timeout&lt;/strong> determines how long a user can remain inactive before being automatically signed out.&lt;br>
This helps protect against unauthorized access if a user forgets to log out.&lt;br>
Enter the duration in seconds (e.g., &lt;code>300&lt;/code> for 5 minutes).&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Tip:&lt;/strong> For production environments, we recommend setting a shorter session timeout (e.g., 10–15 minutes) to minimize security risks.&lt;/p>
&lt;/blockquote>
&lt;hr>
&lt;h4 id="single-sign-on-sso-providers">Single Sign-On (SSO) Providers&lt;/h4>
&lt;p>Single Sign-On (SSO) enables users to log in with their existing accounts from trusted providers, reducing the need for separate credentials.&lt;br>
Monetization supports several SSO integrations out of the box:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Google&lt;/strong> – Allow users to authenticate using their Google Workspace or Gmail account.&lt;/li>
&lt;li>&lt;strong>Twitter&lt;/strong> – Enable login with Twitter credentials.&lt;/li>
&lt;li>&lt;strong>Facebook&lt;/strong> – Allow authentication via Facebook accounts.&lt;/li>
&lt;li>&lt;strong>Microsoft Entra ID&lt;/strong> – Integrate with Microsoft’s enterprise identity service (formerly Azure AD).&lt;/li>
&lt;li>&lt;strong>Custom OIDC Provider&lt;/strong> – Configure any identity provider that supports the OpenID Connect (OIDC) standard.&lt;/li>
&lt;/ul>
&lt;p>You can enable one or more providers depending on your organization’s needs.&lt;br>
For example, enterprises typically use &lt;strong>Microsoft Entra ID&lt;/strong> or &lt;strong>Google Workspace&lt;/strong>, while customer-facing applications may offer &lt;strong>social logins&lt;/strong> like Facebook or Twitter.&lt;/p>
&lt;p>👉 See our step-by-step guide: &lt;a href="https://tridenstechnology.com/how-to-set-up-sso/">How to Set Up Keycloak as an Identity Provider for Entra ID SSO&lt;/a>&lt;/p>
&lt;p>&lt;img src="../security-authentication-identity-providers-page.png" alt="Create Identity Provider">&lt;/p>
&lt;hr>
&lt;h4 id="multi-factor-authentication-mfa">Multi-Factor Authentication (MFA)&lt;/h4>
&lt;p>Multi-Factor Authentication (MFA) requires users to provide an additional verification method (such as an authenticator app or SMS code) during login.&lt;br>
Enabling MFA significantly improves account security by ensuring that a stolen password alone cannot be used to access the system.&lt;/p>
&lt;p>To enable MFA, toggle the &lt;strong>Multi-Factor Authentication&lt;/strong> switch. Once enabled, all users will be required to complete MFA when signing in.&lt;/p>
&lt;hr>
&lt;h4 id="password-policy">Password Policy&lt;/h4>
&lt;p>A strong password policy is essential to prevent brute-force attacks and ensure account safety.&lt;br>
Administrators can configure the following rules:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Minimum password length&lt;/strong> (recommended: 12 or more characters).&lt;/li>
&lt;li>&lt;strong>Maximum password length&lt;/strong>.&lt;/li>
&lt;li>&lt;strong>Password expiration&lt;/strong> (maximum password age in days).&lt;/li>
&lt;li>&lt;strong>Complexity requirements&lt;/strong>:
&lt;ul>
&lt;li>At least one uppercase letter.&lt;/li>
&lt;li>At least one lowercase letter.&lt;/li>
&lt;li>At least one digit.&lt;/li>
&lt;li>At least one special character.&lt;/li>
&lt;li>Restrict use of email or username in the password.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;p>These policies ensure that users create secure and unique passwords that are harder to guess or reuse.&lt;/p>
&lt;hr>
&lt;h3 id="saving-changes">Saving Changes&lt;/h3>
&lt;p>Once you have updated the settings, click &lt;strong>Submit&lt;/strong> to apply and save the configuration.&lt;br>
Changes take effect immediately for all new logins and sessions.&lt;/p>
&lt;hr>
&lt;h3 id="best-practices">Best Practices&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Always enable MFA&lt;/strong> for production environments.&lt;/li>
&lt;li>&lt;strong>Use SSO&lt;/strong> whenever possible to centralize identity management and reduce password fatigue.&lt;/li>
&lt;li>&lt;strong>Set strong password policies&lt;/strong> (minimum length of 12–16 characters with complexity rules).&lt;/li>
&lt;li>&lt;strong>Adjust session timeout&lt;/strong> based on compliance or security needs (shorter timeouts for high-security accounts).&lt;/li>
&lt;/ul></description></item></channel></rss>