Open source cyber-serenity platform that help the security teams designing and managing companies' ISMS, and which allow them to create resilient digital systems with efficient responses against to cyber-threats.
Apache License 2.0
15
stars
2
forks
source link
As technology, I should support Tenant support for users of same organization #58
REQ_SEC_3 : TenantId support is implemented to allow notification of several users attached to a same company and/or solution infrastructure dedicated to a company
The exchanges to multiple connected users of a same company (e.g security team authorized/connected on a dedicated solution instance receiving a transversal notification event on eventbus/tenantId/all/ or via eventbus/all/) are possible with total confidentiality (without possible visibility for other companies and/or infrastructures when solution is deployed on a Cloud/SaaS strategy).
ech: Vert.x Web; sockJS event bus bridge
upgrade fact repository and store persistence interface contract (immutable project) to support tenant id segregation according to the page 401 DDD book
https://www.notion.so/cybnity/454-452f0645dd524fd1b57d07a68a368a3d
REQ_SEC_3 : TenantId support is implemented to allow notification of several users attached to a same company and/or solution infrastructure dedicated to a company The exchanges to multiple connected users of a same company (e.g security team authorized/connected on a dedicated solution instance receiving a transversal notification event on eventbus/tenantId/all/ or via eventbus/all/) are possible with total confidentiality (without possible visibility for other companies and/or infrastructures when solution is deployed on a Cloud/SaaS strategy).
ech: Vert.x Web; sockJS event bus bridge
upgrade fact repository and store persistence interface contract (immutable project) to support tenant id segregation according to the page 401 DDD book