Centralized Security Policy Management and Enforced Document Lockdown for Royal TSX on macOS

Support for centrally managed and enforced security policies in Royal TSX for macOS through MDM solutions such as Microsoft Intune, Jamf Pro, or other macOS device management platforms.

Security configurations should be deployable through MDM configuration profiles or managed preferences, allowing administrators to enforce mandatory application settings that cannot be modified or overridden by end users.

Global Document Lockdown Enforcement

The existing document lockdown functionality should support global policy enforcement across all existing and newly created Royal TSX documents without requiring individual document configuration.

Examples of enforceable restrictions include:

  • Prevent displaying or revealing stored passwords.

  • Prevent editing or modifying stored credentials.

  • Prevent users from disabling or modifying document lockdown settings.

  • Restrict changes to authentication and credential-related configurations.

  • Automatically apply mandatory security restrictions to newly created or imported documents.

Credential Protection Without Restricting Document Editing

An important requirement is the ability to protect stored credentials while still allowing users to edit documents and connections.

Royal TSX already supports a similar configuration through document lockdown, where password visibility can be disabled while document editing remains enabled.

This functionality should be enforceable globally through MDM policies, ensuring that users can create connections, organize folders, and modify non-sensitive connection properties without being able to reveal or modify protected credentials.

Granular Configuration and Policy Enforcement

Centralized policies should allow granular control over which application and document settings can be modified by end users.

This includes document security settings, credential management, authentication configurations, and other security-related application preferences.

MDM-enforced settings should take precedence over local user preferences and document configurations, preventing users from bypassing restrictions by creating new documents or changing existing settings.

Integration with Royal Connect as a centralized policy management platform could also be an option, provided that policies can be consistently enforced on managed macOS devices.

Enterprise Use Case

In enterprise environments, Royal TSX is used on MDM-managed MacBooks to access internal infrastructure and administrative systems.

Users require flexibility to manage their own connections and documents, while sensitive credentials and security configurations must remain protected and centrally controlled.

The goal would be to ensure consistent, tamper-resistant security policy enforcement across all managed macOS devices, particularly for document lockdown and credential protection, while still allowing users to manage their own documents and connections without unnecessary restrictions.

Hi Magnus,

Thanks for the detailed feedback!

Royal Connect’s ACL model could help address some of the granular access controls you describe, such as protecting credentials while allowing users to edit other parts of a document. We’d need to look more closely at which requirements it could cover. To clarify, this refers to our upcoming Royal Connect product, rather than existing Royal TSX functionality.

Broader application policies, including restrictions for newly created or imported documents, could potentially be managed through MDM on macOS, with explicit support in the client to enforce them.

This is a potential feature area for Royal Connect, but we’re still exploring the approach and aren’t sure whether it would be included from the beginning. We can’t commit to a specific implementation or timeline at this stage.