Security and Encryption for Confluence Feature Differences

Server/Data Center

Cloud

A migration path is available

Needed

• understand the feature differences between the application for Confluence Server(DC) and Confluence Cloud

• allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

Versioning/License

Version Support

• minimum migratable version - v3.6.0

• migrate to Security and Encryption for Confluence using steps at the Migration Path

License

• available through Atlassian Marketplace

• available through Atlassian Marketplace only

Confluence Differences

Creating a new Secured macro

• macros are created by using the Secure macro on a Confluence page

Open

• macros are created by using the Secret macro on a Confluence page

Open

Decrypting the Secured macro

• approved access users need to enter their Confluence password to decrypt

• approved users can click the Decrypt button to access the secured content.

Integration with other macros

• Confluence server supports nested macros which mean Secure and Encryption macros can easily be nested and integrated with other Confluence macros

• Confluence Cloud currently does not support nested macro (See CONFCLOUD-68323). This means integration with other apps by way of nesting will be limited

Other functions

An access log of each macro

• after decrypting the macro, approved access users can also view the access log

Centralized view of all secrets on a space

• as a space administrator, you can see

  • what secrets are stored in the space

  • the last time the secrets were updated

  • which pages the secrets belong to

Centralized audit log of all macros on a space

• as a space administrator, you can use the audit logs to

  • run audit reports

  • review access to secrets

  • find out any unintended access

  • detect suspicious activities

  • provide supporting evidence of your organization's security compliance

Macro Differences Overview

Server Macros 

Cloud Macros 

This table lists the differences between Server/Data Center app and the Cloud version.

Secure

• encrypts text for secure sharing of sensitive information on Confluence Server pages

• supports rich text formatting
  
  

Secret 

• encrypts text for secure sharing of sensitive information on Confluence Cloud pages

• does not support rich text formatting
  
  

Secure macro ownership CAN BE transferred

• the user who creates the Secure macro (creator) will always be the owner of the secret

• this ownership can never be changed to anyone, but, Confluence administrators have the privilege to modify the access settings of the Secure macro.

Secret macro ownership CANNOT be transferred

• the creator of the Secret will be the owner of the secret by default, but they can add more owners. Subsequently, this means that the creator of the Secret can also be removed from the owner's field

• a Secret will always be tied to at least one owner

• Confluence admins in Cloud do not have the privilege to access these secrets unless they're the owner