Security Settings

Protect your RAD Repairs account and data with comprehensive security features including two-factor authentication, password policies, session management, and audit logging.

Security Settings Panel
Security Settings - Light Mode

The Security Settings panel provides centralized control over authentication and access policies

Overview of Security Features

RAD Repairs provides multiple layers of security to protect your business data and customer information. The Security Settings panel allows administrators to configure:

Security Best Practice: We recommend enabling two-factor authentication for all administrator accounts and setting a strong password policy. These measures significantly reduce the risk of unauthorized access.

Two-Factor Authentication (2FA)

Two-factor authentication adds an additional security layer by requiring users to provide a second form of verification beyond their password. RAD Repairs supports authenticator app-based 2FA using TOTP (Time-based One-Time Passwords).

Enabling 2FA for Your Account

Individual users can enable 2FA for their own accounts through their profile settings.

1

Access Security Settings

Click on your profile avatar in the top-right corner and select "Security" from the dropdown menu.

2

Enable Two-Factor Authentication

Click the "Enable 2FA" button to begin the setup process.

3

Scan QR Code

Open your authenticator app (Google Authenticator, Authy, Microsoft Authenticator, etc.) and scan the displayed QR code.

4

Verify Setup

Enter the 6-digit code from your authenticator app to confirm the setup is working correctly.

5

Save Backup Codes

Download and securely store the backup codes. These can be used to access your account if you lose access to your authenticator app.

Enforcing 2FA for All Users

Administrators can require all users to enable two-factor authentication. When this setting is enabled:

Important: Before enforcing 2FA for all users, ensure that all team members have access to an authenticator app on their mobile devices. Consider providing a transition period and training for users unfamiliar with 2FA.

Password Policies

Strong password policies help prevent unauthorized access to user accounts. Configure the following password requirements:

Minimum Length

Set the minimum number of characters required for passwords. We recommend a minimum of 12 characters for strong security.

Setting Recommended Value Description
Minimum Length 12 characters The minimum number of characters a password must contain
Maximum Length 128 characters The maximum number of characters allowed (prevents DoS attacks)

Complexity Requirements

Require passwords to include a mix of character types for increased security:

Modern Security Guidance: Recent NIST guidelines suggest that password length is more important than complexity. Consider requiring longer passwords (16+ characters) rather than complex combinations that users may struggle to remember.

Expiration Settings

Configure password expiration to require users to change their passwords periodically:

Setting Options Description
Password Expiration Never / 30 / 60 / 90 / 180 days How often users must change their passwords
Password History 0-24 passwords Number of previous passwords that cannot be reused
Expiration Warning 3-14 days Days before expiration to start warning users

Session Management

Control user session behavior to balance security with user convenience:

Session Timeout Settings

Active Session Controls

Administrators and users can view and manage active sessions:

Login Attempt Limits

Protect against brute-force attacks by limiting failed login attempts:

Setting Default Value Description
Maximum Failed Attempts 5 attempts Number of failed attempts before account lockout
Lockout Duration 15 minutes How long the account is locked after exceeding attempts
Lockout Reset Period 1 hour Time after which failed attempt count resets
CAPTCHA Threshold 3 attempts Show CAPTCHA after this many failed attempts

Locked Out? If a user is locked out of their account, an administrator can manually unlock it from the User Management panel. Users can also use the "Forgot Password" feature if email-based recovery is enabled.

IP Restrictions

For enhanced security, you can restrict access to RAD Repairs based on IP addresses. This is particularly useful for businesses with static IP addresses.

Allowlist Mode

Only allow access from specified IP addresses or ranges:

Blocklist Mode

Block specific IP addresses or ranges while allowing all others:

Caution: Be careful when configuring IP restrictions. Incorrect settings could lock yourself or your team out of the application. Always ensure you have a backup access method before enabling strict IP restrictions.

Audit Logging

RAD Repairs maintains comprehensive audit logs of all security-related events. These logs are essential for compliance, troubleshooting, and security investigations.

Events Logged

Viewing Audit Logs

Access audit logs from Admin Settings > Security > Audit Log. You can:

Frequently Asked Questions

What happens if I lose access to my authenticator app?

Use one of your backup codes to log in, then disable and re-enable 2FA to set up a new authenticator. If you don't have backup codes, contact your administrator to temporarily disable 2FA on your account.

Can I use SMS-based 2FA instead of an authenticator app?

RAD Repairs currently supports authenticator app-based 2FA only. SMS-based 2FA is not available due to security vulnerabilities associated with SMS (SIM swapping attacks, SMS interception).

How do I know if someone tried to access my account?

Check your login history in your profile settings, or view the audit log (administrators only). You'll see all login attempts, including failed ones, with timestamps and IP addresses.

Can I set different password policies for different user roles?

Currently, password policies apply to all users equally. However, you can require 2FA only for administrator accounts while making it optional for other users.

How long are audit logs retained?

By default, audit logs are retained for 90 days. This can be configured in Security Settings. For compliance purposes, you may want to extend retention or export logs regularly for long-term storage.

What should I do if I suspect a security breach?

Immediately: 1) Force logout all sessions from your account, 2) Change your password, 3) Review audit logs for suspicious activity, 4) Contact RAD Repairs support if needed. For serious incidents, consider contacting your IT security team or authorities.

Need Help with Security Configuration?

If you have questions about security settings or need assistance configuring your account protection, our support team is here to help.

Contact Support