Enterprise organizations using Turbot Pipes can now take advantage of powerful new security and governance features that provide granular control over authentication, access management, and workspace configuration across their entire tenant. These enhancements address key requirements from our enterprise customers who need to enforce consistent security policies, meet compliance requirements, and maintain governance standards while enabling their teams to leverage the full power of Turbot Pipes. ## Session timeout management Custom tenant administrators can now [configure session timeout policies](https://turbot.com/pipes/docs/accounts/tenant/authentication#session-timeout) that align with their organization's security requirements. This feature provides separate controls for browser-based Console sessions and CLI sessions, ensuring appropriate security postures across different access patterns. ### Configurable timeout policies Set distinct timeout durations for different access methods: - **Console Session Timeout**: Control how long users can remain logged in through the web browser - **CLI Session Timeout**: Manage the duration of command-line interface sessions - **Custom durations**: Choose from preset options or define custom timeout periods that meet your specific security policies The default timeout is 30 days, but organizations with stricter security requirements can reduce this to as little as a few hours, ensuring that inactive sessions are terminated promptly.

Session timeout configuration in Turbot Pipes

## Enhanced token management API [tokens](https://turbot.com/pipes/docs/accounts/developer/advanced#tokens) are critical for automation and integration, but they also represent a potential security risk if not properly managed. Our enhanced token management features give organizations the control they need while maintaining usability. ### User token improvements Users can now create up to five tokens, each with: - **Custom titles**: Make tokens easily identifiable by adding descriptive names - **Expiration dates**: Set specific expiration periods for each token - **Individual management**: Deactivate or delete tokens independently

### Maximum token expiration controls Enterprise administrators can now enforce organization-wide token lifetime policies through the [Maximum Token Expiration](https://turbot.com/pipes/docs/accounts/tenant/authentication#maximum-token-expiration) setting. This ensures that no token within your tenant can exceed your defined security threshold, whether it's 30 days, 90 days, or any custom duration. Key benefits: - Enforce consistent token rotation practices - Reduce the risk of long-lived credentials - Maintain compliance with security policies - Apply to both user tokens and Service Account tokens

## Workspace and access restrictions Enterprise tenants can now [configure granular restrictions](https://turbot.com/pipes/docs/accounts/tenant/workspace-settings#workspace-configuration) on workspace features and user capabilities, helping organizations maintain control over their data access patterns and workspace proliferation.

### Personal workspace management Control whether users can create personal workspaces, helping organizations: - Maintain centralized governance over all workspaces - Ensure all work happens in team-managed spaces - Simplify compliance and auditing - Reduce shadow IT risks New tenants have personal workspaces disabled by default, encouraging collaborative workspace patterns from the start. ### PostgreSQL endpoint access control Direct database access can be powerful for advanced users but may not align with every organization's security model. Enterprise tenants can now completely disable Steampipe PostgreSQL endpoint access across all workspaces. Consider disabling direct database access if your organization: - Requires all data access to go through approved APIs - Needs to prevent data exfiltration through database connections - Wants to simplify the security surface area - Has compliance requirements that restrict direct database access When disabled: - Users cannot connect directly to workspace PostgreSQL endpoints - All database connection information is removed from the UI - API and web-based access remain fully functional - Existing database connections are terminated ## Start securing your Pipes deployment today Ready to implement these enterprise controls? Sign in to your tenant to configure these new security features, or [sign up for a free trial](https://pipes.turbot.com/tenant/create) to get started. And [let us know](https://turbot.com/community/join) how these enterprise features support your organization's security requirements!

Enhanced Enterprise Controls for Turbot Pipes