You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 98baaa2
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/user-guide/multi-tenancy/README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,23 @@
1
1
# Multi Tenancy / Multi Environment Support
2
2
3
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.
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, as-long as the scanner is able to send out http requests to the engine.
5
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.
6
+
> The engine never actively sends out requests to the scanner, the communication is always initiated asynchronously and by pulling from the scanner side. The Engine only responds to incoming http requests from the scanner.
7
7
8
8
So in a multi-tenant / multi-environment secureCodeBox setup there would be two different types of scanner working on jobs.
9
9
10
-
1.Specialized scanner, located in isolated networks, handling scans especially for these networks.
10
+
1.Specialised scanner, located in isolated networks, handling scans especially for these networks.
11
11
2. Default scanner handling Jobs without specific network access.
12
12
13
13

14
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:
15
+
To separate which scanner should be able to work on which scan the secureCodeBox relies on the camunda user management. Every scanner has to authenticate itself against the engine to communicate with it. The authentication and authorization system of camunda is structured into three main concepts:
16
16
17
17
1.`Users`: The basic building block
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".
19
-
3.`Groups`: A group is a collection of users asigning them a specifc role. The secureCodeBox creates three different roles by default.
20
-
1.`camunda-admin` for administartion users, with the ability to do everything.
18
+
2.`Authorization `: 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".
19
+
3.`Groups`: A group is a collection of users assigning them a specific role. The secureCodeBox creates three different roles by default.
20
+
1.`camunda-admin` for administration users, with the ability to do everything.
21
21
2.`scanner` for the technical users of the scanners, with the ability to fetch scan jobs and submit results
22
22
3.`continuousIntegration` to start security tests from ci systems like "jenkins" or "travis".
23
23
4.`Tenants`: A tenant groups together users from a business centric view. E.g. all users of a team would be part a of a tenant.
@@ -26,19 +26,19 @@ To seperate which scanner should be able to work on which scan the secureCodeBox
26
26
27
27
As an example, let imagine the following example:
28
28
29
-
A company consisting of many different delopment teams has a shared secureCodeBox instance. "Team Blue" now wants to test their internal Payment Microservice which is running in a protected network. To get started the team sets up a camunda Tenant called:
29
+
A company consisting of many different deployment teams has a shared secureCodeBox instance. "Team Blue" now wants to test their internal payment microservice which is running in a protected network. To get started the team sets up a camunda Tenant called:
The Scanner needs to be deployed in the network. The setup will depend on their network, e.g. when the network is a protected vpc in aws the scanner could be deployed via fargate in the same vpc.
40
40
41
-
More generaly they want to get the scanner container running and provide it with three pieces of information:
41
+
More generally they want to get the scanner container running and provide it with three pieces of information:
0 commit comments