|
1 | 1 | # Multi Tenancy / Multi Environment Support |
2 | 2 |
|
3 | | -The basic principle of multi-tenancy support in the secureCodeBox is to get the scanners running inside protected networks. This way the scanners are able to access the service directly without the interference of any firewall. The network connectivity between the scanner and the engine works, aslong as the scanner is able to send out http requests to the engine. The engine activly sends out requests to the scanner, it only responds to their incomming http requests. |
| 3 | +The basic principle of multi-tenancy support in the secureCodeBox is to get the *scanners running inside protected networks*. |
| 4 | +This way the scanners are able to access the service directly without the interference of any firewall. The network connectivity between the scanner and the engine works, aslong as the scanner is able to send out http requests to the engine. |
| 5 | + |
| 6 | +> The engine never activly sends out requests to the scanner, the communication is always initiated asynchronize and by pulling from the scannner side. The Engine only responds to incomming http requests from the scanner. |
4 | 7 |
|
5 | 8 | So in a multi-tenant / multi-environment secureCodeBox setup there would be two different types of scanner working on jobs. |
6 | 9 |
|
7 | | -1. Specialized scanner, located in isolated networks, handling scans for these networks. |
| 10 | +1. Specialized scanner, located in isolated networks, handling scans especially for these networks. |
8 | 11 | 2. Default scanner handling Jobs without specific network access. |
9 | 12 |
|
10 | | -To seperate which scanner should be able to work on which scan the secureCodeBox relies on the camunda user managment. Every scanner has to authenticate itself agaisnt the engine to communicate with it. The authentification and authorization system of camunda is structured into three main concepts: |
| 13 | + |
| 14 | + |
| 15 | +To seperate which scanner should be able to work on which scan the secureCodeBox relies on the camunda user managment. Every scanner has to authenticate itself against the engine to communicate with it. The authentification and authorization system of camunda is structured into three main concepts: |
11 | 16 |
|
12 | 17 | 1. `Users`: The basic building block |
13 | 18 | 2. `Authorizations`: A authorization represent a specific right. The are structure of a type of object, e.g. a "user", and a list of action allowed to be performed on the object, e.g. "create", "update". |
@@ -65,6 +70,6 @@ PUT https://engine.scb.my-organisation.com/box/securityTests |
65 | 70 | ] |
66 | 71 | ``` |
67 | 72 |
|
68 | | -The important piece of this definition is the tenant attribute of the securityTest. This indicates the engine the engine which tenant to start the securityTest with. If the tenant doesnt get specified the process will get started without a tenant and will be worked on by one of the default scanner. |
| 73 | +The important piece of this definition is the *tenant* attribute of the securityTest. This definition indicates the engine which tenant to start the securityTest with. If the tenant doesn't get specified the process will get started without a tenant and will be worked on by one of the default scanner. |
69 | 74 |
|
70 | 75 | > Note: To start a securityTest as a tenant the starting user has to be a member of the tenant. |
0 commit comments