rohit/probo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
823 Commits 1 Branch 0 Tags
839d842fd1dcd852344cd2bf48ba11a4c2c2000b
Commit Graph

45 Commits

Author SHA1 Message Date
Bryan Frimin
cece072619 Add note to risk 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-24 17:47:39 -07:00
Bryan Frimin
80ad4f643a Add business and data impact on list 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-23 11:23:28 -07:00
Bryan Frimin
ca1b7e8f42 Expire vendor risk assement 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-22 16:03:09 -07:00
Bryan Frimin
f038642ece Add first risk assememnt implementation 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-22 16:02:59 -07:00
Bryan Frimin
53c326d354 Remove unused types 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-20 21:23:18 -07:00
Bryan Frimin
9aeed6da4a Add settins connector view 
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-20 21:16:49 -07:00
Antoine Bouchardy
b137ec6bdf Add categories on risk 
Signed-off-by: Antoine Bouchardy <antoine@getprobo.com>
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
 2025-04-20 20:04:09 -07:00
gearnode
a90de1fdde Update risk matrix 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-15 11:16:24 -07:00
gearnode
3711bb4bbb Rename mitigation into mesure 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-12 21:09:49 -07:00
gearnode
9b868220f6 Add vendor business and security owner 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-12 14:53:16 -07:00
gearnode
8bbb4f59f1 Add risk ownership 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-12 11:18:20 -07:00
gearnode
e3c7194afc Add risk treatment 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-12 10:39:05 -07:00
gearnode
16efab774a Refactor risk management 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-12 00:18:31 -07:00
gearnode
9fa33726e7 Enhance vendor management with extended data fields 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-10 17:19:35 -07:00
gearnode
7e6fa44923 Add vendor compliance reports 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-09 09:32:48 -07:00
gearnode
4ce72c03f7 Add control-policy mappings and rename control APIs 
This introduces the ability to map controls to policies alongside the
existing control-mitigation mappings. The feature adds bidirectional
relationships with new GraphQL fields on Control and Policy types.

Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-08 21:14:11 -07:00
gearnode
fd9442f6a3 Fix fulfill missing upload 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-02 11:57:15 +02:00
gearnode
c145125b1a Add requested evidence 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-02 10:10:49 +02:00
gearnode
0ec0c7d6c3 Add mapping between risk and mitigation 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-04-01 07:39:29 +02:00
gearnode
d0fc5cd439 Add mapping between control and mitigation 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-31 22:01:09 +02:00
gearnode
7d38882e1f Add risk proba and impact 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-31 09:49:35 +02:00
gearnode
5e601a0ef0 Add risk list and create risk 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-30 16:51:24 +02:00
gearnode
4e4e2369fc Add import mitigations 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-30 15:02:46 +02:00
gearnode
1867c79aad Add mitigation views 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-28 14:19:36 +01:00
gearnode
7321862ba9 First step of mitigation migration 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-27 23:34:35 +01:00
gearnode
483a620fe7 Rename control to mitigation 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-27 13:07:27 +01:00
gearnode
b8bbeaba11 Add evidence type link 
close #44

Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-20 17:25:29 +01:00
gearnode
7efae81113 Make task time estimate optional 
close #38

Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-19 13:08:27 +01:00
gearnode
1505e5b096 Expose new cursor over GraphQL API 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-19 00:20:35 +01:00
gearnode
257ea563a9 Add service account people kind 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-16 18:44:17 +01:00
gearnode
c9b58010f7 Use REST API for confirm endpoint 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-14 13:48:29 +01:00
gearnode
7153831fb2 Remove user from organization 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-14 11:17:28 +01:00
gearnode
ebc88ec7e8 Add user invitation system 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-14 10:43:34 +01:00
gearnode
87f7654b10 Add organization member list 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-14 09:38:01 +01:00
gearnode
ab739d9bda Add update organziation 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-13 11:15:13 +01:00
gearnode
8cbe08d136 Add assigned people to a task 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-13 10:08:31 +01:00
gearnode
376edd927d Add task time estimate 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-13 09:14:08 +01:00
gearnode
d4280b1111 Add control importance 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-13 08:46:51 +01:00
gearnode
1a6e68f13c Add email confirmation 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-12 12:17:21 +01:00
gearnode
019f76ecfd Refactor authentication handler 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-11 12:28:51 +01:00
gearnode
5bdc474aef Move coredata outside probo service 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-11 09:38:36 +01:00
gearnode
51fb5c9510 Update gqlgen code 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-11 09:14:01 +01:00
gearnode
c2bf3a42ed Simplify database schema 
Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-11 09:03:13 +01:00
gearnode
58eda95d93 Rewrite the global id system to include tenant id 
The API should be aware of the tenant they are working on. Many solution
is possible like passing a header, adding the tenant id in each function
call, encode the tenant id in the GID.

I consider the header as a hack it force the client to keep in mind to
pass this header, having to returns an error in case of not defined
header and add a non standard header make the API more harder to use.

Passing the tenant id everywhere will be a good option but since Relay
impose to have node(id: ID!) Node interface it is not possible or by
hacking by wrapping node(id: ID!) Node in top query who getting the
tenant_id.

I finish by simpliy encode the tenant id directly in the object id, it
what AWS do too, it allow to always have the information, and it ensure
a right data isolation.

Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-10 13:54:55 +01:00
gearnode
123a538d82 Embded frontend inside go binary 
This will simplify the self hosting of the platform.

Signed-off-by: gearnode <bryan@frimin.fr>
 2025-03-09 15:30:28 +01:00