Skip to main content

Security Settings

Overview​

CADENSA provides enterprise-grade security features to protect your data. Configure two-factor authentication, manage sessions, set up SSO (ENTERPRISE) (Coming Soon), and review audit logs.

Security features:

  • Two-Factor Authentication (2FA)
  • πŸ”‘ Single Sign-On (SSO) - ENTERPRISE (Coming Soon)
  • Audit Logs - ENTERPRISE
  • πŸ›‘οΈ IP Allowlisting - ENTERPRISE
  • Session Management
  • ⚑ Security Alerts

Two-Factor Authentication (2FA)​

Enable 2FA​

Add extra security to your account.

(Covered in detail in Profile Settings)

Quick setup:

  1. Settings β†’ Security β†’ 2FA
  2. Choose method (Authenticator app recommended)
  3. Scan QR code with app
  4. Verify 6-digit code
  5. Save backup codes
  6. 2FA enabled

2FA methods:

  • Authenticator App (Recommended) - Google Authenticator, Authy, 1Password
  • SMS - Text message to phone number
  • Email - Code sent to email (least secure)

Enforce 2FA (ENTERPRISE)​

Require 2FA for all workspace members.

How to enforce:

  1. Navigate to Workspace Settings β†’ Security
  2. Click "Enforce 2FA"
  3. Set grace period
  4. Notify team members
  5. Enable enforcement

2FA enforcement settings:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Two-Factor Authentication Policy β”‚ β”‚ (ENTERPRISE Workspace Setting) β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ β”‚ β”‚ β˜‘ Require 2FA for all members β”‚ β”‚ β”‚ β”‚ Enforcement Level: β”‚ β”‚ ● Mandatory (block access) β”‚ β”‚ β—‹ Recommended (warning only) β”‚ β”‚ β”‚ β”‚ Grace Period: β”‚ β”‚ [7 days β–Ό] β”‚ β”‚ β”‚ β”‚ Users without 2FA: 3 β”‚ β”‚ β€’ John Doe (Owner) β”‚ β”‚ β€’ Sarah Johnson (Manager) β”‚ β”‚ β€’ Mike Chen (Member) [Remind] β”‚ β”‚ β€’ Lisa Park (Member) [Remind] β”‚ β”‚ β€’ Tom Wilson (Viewer) [Remind] β”‚ β”‚ β”‚ β”‚ Notification: β”‚ β”‚ β˜‘ Email users without 2FA β”‚ β”‚ β˜‘ Show banner on login β”‚ β”‚ β”‚ β”‚ Allowed Methods: β”‚ β”‚ β˜‘ Authenticator app β”‚ β”‚ β˜‘ SMS β”‚ β”‚ ☐ Email (not recommended) β”‚ β”‚ β”‚ β”‚ [Send Reminder] [Enable Enforcement] β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Grace period enforcement:

Day 1: Enable enforcement
- Email sent to users without 2FA
- Banner shown on login
- "You have 7 days to enable 2FA"

Days 2-6: Reminders
- Daily reminder banner
- Email reminder at Day 4

Day 7: Enforcement begins
- Users without 2FA blocked
- Must enable 2FA to access account
- Can still receive password reset emails

Single Sign-On (SSO)​

Coming Soon β€” ENTERPRISE

SSO (SAML 2.0) and LDAP / Active Directory integration are planned for a future release. This section describes the planned functionality. SSO is not yet available in CADENSA β€” see the Roadmap for the expected timeline.

SAML 2.0 Integration (ENTERPRISE)​

Enterprise SSO for centralized authentication.

Supported providers:

  • Microsoft Azure AD / Entra ID
  • Okta
  • Google Workspace
  • OneLogin
  • Auth0
  • Ping Identity
  • ADFS
  • Custom SAML 2.0 providers

Setup process:

Step 1: Request SSO

1. Contact CADENSA support: <a data-action="support" href="#">support@cadensa.io</a>
2. Provide:
- Identity Provider (IdP) name
- SAML metadata URL or XML file
- Technical contact info
3. Support creates SSO configuration
4. You receive CADENSA SAML details

Step 2: Configure IdP

Add CADENSA to your Identity Provider:

Service Provider Details:
- Entity ID: https://app.cadensa.io/saml/metadata
- ACS URL: https://app.cadensa.io/saml/acs
- SLS URL: https://app.cadensa.io/saml/sls

Attribute Mapping:
- Email: email, emailAddress, mail
- First Name: firstName, givenName
- Last Name: lastName, surname, sn
- Display Name: displayName (optional)

Step 3: Test & Enable

  1. CADENSA support configures connection
  2. Test login provided
  3. Verify user attributes
  4. Enable for workspace
  5. Users login via SSO

SSO configuration:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Single Sign-On Configuration β”‚ β”‚ (ENTERPRISE) β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ β”‚ β”‚ SSO Status: Enabled β”‚ β”‚ β”‚ β”‚ Identity Provider: β”‚ β”‚ Microsoft Azure AD β”‚ β”‚ β”‚ β”‚ Connection Details: β”‚ β”‚ β€’ Entity ID: https://sts.windows.net/../β”‚ β”‚ β€’ SSO URL: https://login.microsoftonlineβ”‚ β”‚ .com/.../saml2 β”‚ β”‚ β€’ Certificate: Valid until Dec 2027 β”‚ β”‚ β”‚ β”‚ Attribute Mapping: β”‚ β”‚ Email: emailaddress β”‚ β”‚ First Name: givenname β”‚ β”‚ Last Name: surname β”‚ β”‚ Display Name: displayname β”‚ β”‚ β”‚ β”‚ User Provisioning: β”‚ β”‚ ● Just-In-Time (JIT) β”‚ β”‚ (Create user on first login) β”‚ β”‚ β—‹ Manual only β”‚ β”‚ β”‚ β”‚ Default Role for New Users: β”‚ β”‚ [Member β–Ό] β”‚ β”‚ β”‚ β”‚ Fallback Authentication: β”‚ β”‚ β˜‘ Allow password login for admins β”‚ β”‚ (Emergency access) β”‚ β”‚ β”‚ β”‚ [Test SSO] [Disable SSO] [Edit] β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜


LDAP / Active Directory (ENTERPRISE)​

Direct integration with corporate directory.

Setup:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ LDAP / Active Directory Integration β”‚
β”‚ (ENTERPRISE) β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚
β”‚ Server Settings: β”‚
β”‚ Host: [ldap.company.com__________] β”‚
β”‚ Port: [389] ☐ Use SSL (636) β”‚
β”‚ β”‚
β”‚ Bind Credentials: β”‚
β”‚ Bind DN: [cn=admin,dc=company,dc=com_] β”‚
β”‚ Password: [β€’β€’β€’β€’β€’β€’β€’β€’β€’] β”‚
β”‚ β”‚
β”‚ User Search: β”‚
β”‚ Base DN: [ou=users,dc=company,dc=com_] β”‚
β”‚ Filter: [(objectClass=person)_______] β”‚
β”‚ β”‚
β”‚ Attribute Mapping: β”‚
β”‚ Email: [mail____________] β”‚
β”‚ First Name: [givenName______] β”‚
β”‚ Last Name: [sn____________] β”‚
β”‚ Username: [sAMAccountName_] β”‚
β”‚ β”‚
β”‚ Group Sync (optional): β”‚
β”‚ β˜‘ Sync LDAP groups to CADENSA β”‚
β”‚ Admin Group: [CN=CADENSA_Admins____] β”‚
β”‚ Manager Group: [CN=CADENSA_Managers_] β”‚
β”‚ β”‚
β”‚ [Test Connection] [Save Configuration] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Audit Logs​

Security & Activity Logs (ENTERPRISE)​

Track all account activity for compliance.

What's logged:

Authentication Events:

  • User login (success/failure)
  • User logout
  • Password changes
  • 2FA enabled/disabled
  • SSO logins
  • Failed login attempts

Account Changes:

  • User created/deleted
  • Email changed
  • Role changed
  • Permission changes
  • Workspace access granted/revoked

Data Access:

  • Project created/edited/deleted
  • Time entries created/edited/deleted
  • Report generated
  • Data exported
  • Settings changed

Billing:

  • Subscription upgraded/downgraded
  • Payment method added/removed
  • Invoice generated

Audit log viewer:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Audit Logs β”‚
β”‚ [Export CSV] [Filter β–Ό] [Search____] β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚
β”‚ Timestamp User Action β”‚
β”‚ ────────────────── ───────── ────────── β”‚
β”‚ β”‚
β”‚ 2026-01-25 10:45 John Doe LOGIN β”‚
β”‚ IP: 185.123.45.67 β”‚
β”‚ Device: Chrome on macOS β”‚
β”‚ Location: Budapest, HU β”‚
β”‚ [View Details] β”‚
β”‚ β”‚
β”‚ 2026-01-25 10:30 Sarah J. EDITED β”‚
β”‚ Project: Website Redesign β”‚
β”‚ Changed: Budget 80h β†’ 100h β”‚
β”‚ [View Details] β”‚
β”‚ β”‚
β”‚ 2026-01-25 10:15 Mike C. EXPORTED β”‚
β”‚ Report: Monthly Time Report β”‚
β”‚ Format: CSV β”‚
β”‚ Rows: 1,234 entries β”‚
β”‚ [View Details] β”‚
β”‚ β”‚
β”‚ 2026-01-25 09:58 System FAILED β”‚
β”‚ Login attempt failed β”‚
β”‚ User: john.doe@example.com β”‚
β”‚ Reason: Invalid password β”‚
β”‚ IP: 192.168.1.100 β”‚
β”‚ [View Details] β”‚
β”‚ β”‚
β”‚ 2026-01-25 09:45 Lisa P. CREATED β”‚
β”‚ Time Entry: 2h 30m β”‚
β”‚ Project: Mobile App β”‚
β”‚ Task: Bug fixes β”‚
β”‚ [View Details] β”‚
β”‚ β”‚
β”‚ [Load More] [Jump to Date...] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Filter audit logs:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Filter Audit Logs β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚
β”‚ Date Range: β”‚
β”‚ From: [2026-01-01_] To: [2026-01-31_] β”‚
β”‚ β”‚
β”‚ Event Type: β”‚
β”‚ ☐ All Events β”‚
β”‚ β˜‘ Authentication (login/logout) β”‚
β”‚ β˜‘ User management β”‚
β”‚ ☐ Project changes β”‚
β”‚ ☐ Time entries β”‚
β”‚ β˜‘ Data exports β”‚
β”‚ β˜‘ Settings changes β”‚
β”‚ β˜‘ Billing events β”‚
β”‚ β˜‘ Security alerts β”‚
β”‚ β”‚
β”‚ User: β”‚
β”‚ [All Users β–Ό] or [Search user...] β”‚
β”‚ β”‚
β”‚ IP Address: β”‚
β”‚ [_______________] (optional) β”‚
β”‚ β”‚
β”‚ Result: β”‚
β”‚ β—‹ All β”‚
β”‚ β—‹ Success only β”‚
β”‚ ● Failed only β”‚
β”‚ β”‚
β”‚ [Clear Filters] [Apply Filters] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Export audit logs:

Export Format:
● CSV (Excel-compatible)
β—‹ JSON (machine-readable)
β—‹ PDF (human-readable)

Date Range: Last 90 days
Events: 12,345 matching events

Columns to include:
β˜‘ Timestamp
β˜‘ User
β˜‘ Event Type
β˜‘ IP Address
β˜‘ Device/Browser
β˜‘ Location
β˜‘ Details
β˜‘ Result (Success/Failed)

[Cancel] [Export Audit Log]

IP Allowlisting (ENTERPRISE)​

Restrict Access by IP​

Only allow access from specific IP addresses.

Use cases:

  • Office-only access
  • VPN-required access
  • Geographic restrictions
  • Compliance requirements

IP allowlist configuration:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ IP Allowlisting β”‚ β”‚ (ENTERPRISE) β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ β”‚ β”‚ β˜‘ Enable IP allowlisting β”‚ β”‚ β”‚ β”‚ Warning: This will block access β”‚ β”‚ from IPs not on the list. β”‚ β”‚ β”‚ β”‚ Allowed IP Addresses: β”‚ β”‚ β”‚ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ 185.123.45.0/24 β”‚ β”‚ β”‚ β”‚ Description: Budapest Office β”‚ β”‚ β”‚ β”‚ [Edit] [Remove] β”‚ β”‚ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β”‚ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ 78.234.56.100 β”‚ β”‚ β”‚ β”‚ Description: Remote VPN β”‚ β”‚ β”‚ β”‚ [Edit] [Remove] β”‚ β”‚ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β”‚ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ 192.168.1.0/24 β”‚ β”‚ β”‚ β”‚ Description: Local Network β”‚ β”‚ β”‚ β”‚ [Edit] [Remove] β”‚ β”‚ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β”‚ β”‚ [+ Add IP Address/Range] β”‚ β”‚ β”‚ β”‚ Bypass Options: β”‚ β”‚ β˜‘ Allow API access (for integrations) β”‚ β”‚ ☐ Allow mobile apps β”‚ β”‚ β˜‘ Allow admins (emergency access) β”‚ β”‚ β”‚ β”‚ Current IP: 185.123.45.67 β”‚ β”‚ Status: Allowed β”‚ β”‚ β”‚ β”‚ [Save Settings] β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Add IP address:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Add IP Address or Range β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚
β”‚ Type: β”‚
β”‚ ● Single IP (192.168.1.100) β”‚
β”‚ β—‹ IP Range (CIDR notation) β”‚
β”‚ β”‚
β”‚ IP Address: β”‚
β”‚ [185.123.45.67______________] β”‚
β”‚ β”‚
β”‚ Or IP Range (CIDR): β”‚
β”‚ [185.123.45.0/24____________] β”‚
β”‚ β”‚
β”‚ Description: β”‚
β”‚ [Office Network_____________] β”‚
β”‚ β”‚
β”‚ [Cancel] [Add to Allowlist] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Session Management​

Active Sessions​

(Covered in Profile Settings)

Quick actions:

  • View all active sessions
  • See device, location, IP
  • Logout individual sessions
  • Logout all other sessions

Remember Me & New Tab Behavior​

Understanding how login sessions work across browser tabs.

When you log in to CADENSA, you choose how your session is stored:

Login optionSession storageNew tab behavior
βœ… Remember me checkedlocalStorage (persists across tabs)Opens directly to dashboard
☐ Remember me uncheckedsessionStorage (tab-only)Redirects to login page
Why does a new tab redirect to login?

This is intentional security behavior. When you log in without "Remember me", your session is tied to that specific browser tab. Opening a new tab starts a fresh, unauthenticated session β€” your credentials are never shared between tabs.

This protects you on shared computers: closing the tab ends your session completely.

Want to stay logged in across tabs?

Enable the "Remember me" checkbox on the login page. Your session will persist across all tabs and browser restarts until you explicitly log out or the token expires (24 hours).

What to do if you're always redirected to login on new tabs:

  1. Log out completely
  2. Log back in with "Remember me" checked
  3. New tabs will now open directly to your dashboard

Session Security Settings​

Configure session behavior.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Session Security β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ β”‚
β”‚ Session Timeout: β”‚
β”‚ [7 days β–Ό] β”‚
β”‚ β”‚
β”‚ Idle Timeout: β”‚
β”‚ [30 minutes β–Ό] β”‚
β”‚ (Logout after 30 min of inactivity) β”‚
β”‚ β”‚
β”‚ Concurrent Sessions: β”‚
β”‚ ● Unlimited β”‚
β”‚ β—‹ Single device only β”‚
β”‚ β—‹ Maximum: [3] devices β”‚
β”‚ β”‚
β”‚ Remember Device: β”‚
β”‚ β˜‘ Remember this device for 30 days β”‚
β”‚ (Skip 2FA on trusted devices) β”‚
β”‚ β”‚
β”‚ Security Notifications: β”‚
β”‚ β˜‘ Email on new device login β”‚
β”‚ β˜‘ Email on suspicious activity β”‚
β”‚ β˜‘ Email on password change β”‚
β”‚ β”‚
β”‚ [Save Settings] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Security Alerts​

Suspicious Activity Detection​

Automatic security monitoring.

What's monitored:

  • Multiple failed login attempts
  • Login from unusual location
  • Login from new device
  • Large data exports
  • Unusual API activity
  • Permission changes

Security alert example:

From: CADENSA Security <a data-action="support" href="#">support@cadensa.io</a>
To: john.doe@example.com
Subject: Security Alert: New Device Login

Dear John,

We detected a login to your CADENSA account from
a new device:

Device: Chrome on Windows
Location: London, United Kingdom
IP Address: 78.234.56.78
Time: Jan 25, 2026 at 10:45 GMT

Was this you?

[Yes, this was me] [No, secure my account]

If this wasn't you:
1. Change your password immediately
2. Enable 2FA if not already enabled
3. Review active sessions
4. Contact support if needed

Best regards,
CADENSA Security Team

Security dashboard:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Security Overview β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ β”‚ β”‚ Account Security Score: 85/100 β”‚ β”‚ β”‚ β”‚ Recommendations Completed: β”‚ β”‚ β€’ Strong password (12+ chars) β”‚ β”‚ β€’ 2FA enabled β”‚ β”‚ β€’ Recent security review β”‚ β”‚ β”‚ β”‚ Recommendations: β”‚ β”‚ β€’ Review active sessions (5 devices) β”‚ β”‚ β€’ Update password (last changed 90d) β”‚ β”‚ β”‚ β”‚ Recent Security Events: β”‚ β”‚ β€’ Login from new device (2 hours ago) β”‚ β”‚ β€’ Password changed (15 days ago) β”‚ β”‚ β€’ 2FA enabled (30 days ago) β”‚ β”‚ β”‚ β”‚ [View All Security Events] β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜


Compliance & Certifications​

SOC 2 Type II (ENTERPRISE)​

CADENSA compliance certifications.

Available certifications:

SOC 2 Type II

  • Annual audit
  • Security, availability, confidentiality
  • Report available on request

GDPR Compliant

  • Data processing agreements
  • Right to deletion
  • Data portability
  • Privacy by design

ISO 27001 (in progress)

  • Information security management
  • Expected: Q2 2026

HIPAA Compliant (ENTERPRISE add-on)

  • Healthcare data protection
  • Business Associate Agreement
  • Contact sales for details

Request compliance documents:

1. Email: <a data-action="support" href="#">support@cadensa.io</a>
2. Specify:
- Company name
- Certification needed
- Purpose (vendor assessment, audit, etc.)
3. Receive:
- SOC 2 report
- DPA (Data Processing Agreement)
- Security questionnaire responses
- Penetration test summaries

Data Encryption​

Encryption Details​

How CADENSA protects your data.

Encryption at rest:

AES-256 encryption Database encrypted Backups encrypted File storage encrypted (S3)

Encryption in transit:

TLS 1.3 (minimum TLS 1.2) Perfect Forward Secrecy HSTS enabled Certificate pinning (mobile apps)

Key management:

AWS KMS (Key Management Service) Automatic key rotation Separate keys per customer (ENTERPRISE)


Best Practices​

Do's​

  • Enable 2FA - Extra security layer
  • Use strong passwords - 12+ characters, unique
  • Review active sessions - Logout unknown devices
  • Monitor audit logs - Check for suspicious activity (ENTERPRISE)
  • Restrict IP access - If possible (ENTERPRISE)
  • Use SSO (Coming Soon) - Centralized authentication (ENTERPRISE)
  • Regular security reviews - Quarterly minimum
  • Educate team - Security awareness training

Don'ts​

  • Don't share passwords - Each user has own account
  • Don't ignore security alerts - Investigate all warnings
  • Don't disable 2FA - Unless absolutely necessary
  • Don't use public WiFi - Without VPN
  • Don't share API keys - Revoke and regenerate if leaked
  • Don't skip compliance - Legal requirements

Troubleshooting​

Can't login with SSO (Coming Soon)​

Problem: SSO login not working.

Solutions:

  1. Check with IT admin (IdP configuration)
  2. Verify user exists in IdP
  3. Check email attribute mapping
  4. Use emergency password login (if enabled)
  5. Contact CADENSA support

2FA code not working​

Problem: 6-digit code rejected.

Solutions:

  1. Ensure time sync on device (settings β†’ date/time)
  2. Wait for new code (refresh every 30 seconds)
  3. Use backup code instead
  4. Contact support to disable 2FA temporarily

IP blocked​

Problem: Cannot access from current IP.

Solutions:

  1. Check current IP: whatismyipaddress.com
  2. Contact workspace admin to add IP
  3. Use VPN if configured
  4. Use mobile data as temporary workaround
  5. Admin emergency access

Next Steps​


Need Help?​