Safety studies are carried out on increasingly complex systems, pushing traditional methods like Fault Tree Analysis (FTA) to their limits. The Model-Based Safety Analysis (MBSA) is a method which brings a solution to those difficulties, also allowing a better representation of a complex system’s dysfunctional behavior. As of now, MBSA users embed a subsystem’s behavior to a higher level system, enabling a more realistic model. However, sharing MBSA models in the extended enterprise context is not currently a widespread technique due to unsolved risks. This paper addresses four of these risks. First, by sharing their model, a supplier risks to expose their architecture to a third party. A masking process shall be applied to a shared model, to protect the intellectual property. Second, merging sub-models involves risks from a size point of view: if the model is too large it can be difficult to compute. Suppliers need to simplify large models without losing essential information. Third, sharing a model without a proper documentation involves a risk of losing traceability. This can be addressed through effective communication throughout the V-cycle project lifecycle. Finally, the usual MBSA tools are missing some aspects to mitigate the risks of model sharing and integration. Hence the need to update some of their functionalities. By exploring solutions to these risks, this research aims to facilitate the exchange of MBSA models, ultimately enhancing collaboration and efficiency in the development of complex systems.