Team and sensitive data

Hello, I have some questions regarding the use of Team with sensitive data.

  • Has anyone had any experience using Team by Obeo to collaborate on models containing sensitive data?
  • How does Team secure the model while noone is working on it?
  • Is it possible to have the model be fully encrypted while noone is working on it?
  • Is it possible to have the parts of the model not being worked on be encrypted, so that only the parts that need modifying are “in the clear” while people work on them?
  • Has there been any sort of cybersecurity assessment of Team as a tool?

Thanks a lot,

For context, I have contacted Obeo for more information, but I would love early advice by any Obeo personnel in the forum or the perspective of a user of the tool on these issues

Team for Capella has several ways to handle sensitive data:

  • Setting the CDO server to accept only SSL connections (acceptor tag) so communications between the clients and the server are secured.
  • Encrypting the database files: Database security is not handled by Team for Capella, it just stores and manages models in a database using the framework CDO. CDO can store models with different databases. However, Team for Capella is tested with an H2 database, so that is the one we support, but it works with other solutions. There are documentations about how to encrypt the .db files it manages ( I do not think we ever tested it and I do not know the impact on performances. The point here is that you can choose the settings of the database, including encryption.
  • User management: Not only, you can define which users are able to connect to the repository, you can have multiple repositories on the same server with different user lists. You can also use the “User Profile” mode to define write rules and limit the model edition scope.

I am not sure how to answer your question on the full or partial encryption of the models depending on if you are working on the models or not. First, it depend on how you manage the model. By default, we use and support a H2 database (but it could be a plain file or stored only in memory. CDO offers different possibilities). Therefore the models you handle in Team for Capella are stored as database tables in .db files. I think the encryption in this case is globaly set for the whole .db files depending on how you set it. If your questions were about encrypting the model elements displayed in Team for Capella that are not currently edited, then this feature is not available. It may not be too hard to have that feature. It may just require a custom LabelProvider, but we would need more information for a proper solution.
Finally, I think that all the Team for Capella users I interacted with used a private network. Even if some uses a SSL connection, LDAP authentication etc, the server was not accessible from outside. I do not think I heard of cybersecurity assessment by I will ask around.

Best regards,
Steve Monnier

Thanks a lot for the information Steve!


Some additions to Steve’s answer:

  • Yes, it’s quite common to have usages in secure domains (which I obviously can’t give details of)
  • T4C does not require any external access (deployment on an internal secure network)
  • For H2, it is indeed possible to imagine technical adaptations. However, contractually, maintenance only covers H2 databases

By the way, not sure we received your initial request. Feel free to contact me in PM for further information on this subject.

Kind regards,


Hi Samuel.

I’m trying to send you a PM but can’t seem to find where to do so. Would you mind sending me one please? Thanks a lot.

Copyright © Eclipse Capella, the Eclipse Capella logo, Eclipse and the Eclipse logo are Trademarks of The Eclipse Foundation.